2018-01-26 20:45:16 +03:00
// SPDX-License-Identifier: GPL-2.0
2005-04-17 02:20:36 +04:00
# include <linux/pci.h>
# include <linux/module.h>
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 11:04:11 +03:00
# include <linux/slab.h>
2005-04-17 02:20:36 +04:00
# include <linux/ioport.h>
2006-10-19 19:41:28 +04:00
# include <linux/wait.h>
2005-04-17 02:20:36 +04:00
2005-11-06 03:45:08 +03:00
# include "pci.h"
2005-04-17 02:20:36 +04:00
/*
* This interrupt - safe spinlock protects all accesses to PCI
* configuration space .
*/
2011-11-04 12:46:00 +04:00
DEFINE_RAW_SPINLOCK ( pci_lock ) ;
2005-04-17 02:20:36 +04:00
/*
2018-03-10 01:36:33 +03:00
* Wrappers for all PCI configuration access functions . They just check
* alignment , do locking and call the low - level functions pointed to
* by pci_dev - > ops .
2005-04-17 02:20:36 +04:00
*/
# define PCI_byte_BAD 0
# define PCI_word_BAD (pos & 1)
# define PCI_dword_BAD (pos & 3)
2017-03-17 00:50:06 +03:00
# ifdef CONFIG_PCI_LOCKLESS_CONFIG
# define pci_lock_config(f) do { (void)(f); } while (0)
# define pci_unlock_config(f) do { (void)(f); } while (0)
# else
# define pci_lock_config(f) raw_spin_lock_irqsave(&pci_lock, f)
# define pci_unlock_config(f) raw_spin_unlock_irqrestore(&pci_lock, f)
# endif
2015-12-28 00:21:11 +03:00
# define PCI_OP_READ(size, type, len) \
2018-09-19 02:58:37 +03:00
int noinline pci_bus_read_config_ # # size \
2005-04-17 02:20:36 +04:00
( struct pci_bus * bus , unsigned int devfn , int pos , type * value ) \
{ \
unsigned long flags ; \
u32 data = 0 ; \
2024-04-29 12:47:07 +03:00
int res ; \
\
if ( PCI_ # # size # # _BAD ) \
return PCIBIOS_BAD_REGISTER_NUMBER ; \
\
2017-03-17 00:50:06 +03:00
pci_lock_config ( flags ) ; \
2005-04-17 02:20:36 +04:00
res = bus - > ops - > read ( bus , devfn , pos , len , & data ) ; \
2021-11-18 17:03:12 +03:00
if ( res ) \
PCI_SET_ERROR_RESPONSE ( value ) ; \
else \
* value = ( type ) data ; \
2017-03-17 00:50:06 +03:00
pci_unlock_config ( flags ) ; \
2024-04-29 12:47:07 +03:00
\
2005-04-17 02:20:36 +04:00
return res ; \
}
2015-12-28 00:21:11 +03:00
# define PCI_OP_WRITE(size, type, len) \
2018-09-19 02:58:37 +03:00
int noinline pci_bus_write_config_ # # size \
2005-04-17 02:20:36 +04:00
( struct pci_bus * bus , unsigned int devfn , int pos , type value ) \
{ \
unsigned long flags ; \
2024-04-29 12:47:07 +03:00
int res ; \
\
if ( PCI_ # # size # # _BAD ) \
return PCIBIOS_BAD_REGISTER_NUMBER ; \
\
2017-03-17 00:50:06 +03:00
pci_lock_config ( flags ) ; \
2005-04-17 02:20:36 +04:00
res = bus - > ops - > write ( bus , devfn , pos , len , value ) ; \
2017-03-17 00:50:06 +03:00
pci_unlock_config ( flags ) ; \
2024-04-29 12:47:07 +03:00
\
2005-04-17 02:20:36 +04:00
return res ; \
}
PCI_OP_READ ( byte , u8 , 1 )
PCI_OP_READ ( word , u16 , 2 )
PCI_OP_READ ( dword , u32 , 4 )
PCI_OP_WRITE ( byte , u8 , 1 )
PCI_OP_WRITE ( word , u16 , 2 )
PCI_OP_WRITE ( dword , u32 , 4 )
EXPORT_SYMBOL ( pci_bus_read_config_byte ) ;
EXPORT_SYMBOL ( pci_bus_read_config_word ) ;
EXPORT_SYMBOL ( pci_bus_read_config_dword ) ;
EXPORT_SYMBOL ( pci_bus_write_config_byte ) ;
EXPORT_SYMBOL ( pci_bus_write_config_word ) ;
EXPORT_SYMBOL ( pci_bus_write_config_dword ) ;
2005-09-27 12:21:55 +04:00
2015-01-10 05:34:39 +03:00
int pci_generic_config_read ( struct pci_bus * bus , unsigned int devfn ,
int where , int size , u32 * val )
{
void __iomem * addr ;
addr = bus - > ops - > map_bus ( bus , devfn , where ) ;
2021-11-18 17:03:14 +03:00
if ( ! addr )
2015-01-10 05:34:39 +03:00
return PCIBIOS_DEVICE_NOT_FOUND ;
if ( size = = 1 )
* val = readb ( addr ) ;
else if ( size = = 2 )
* val = readw ( addr ) ;
else
* val = readl ( addr ) ;
return PCIBIOS_SUCCESSFUL ;
}
EXPORT_SYMBOL_GPL ( pci_generic_config_read ) ;
int pci_generic_config_write ( struct pci_bus * bus , unsigned int devfn ,
int where , int size , u32 val )
{
void __iomem * addr ;
addr = bus - > ops - > map_bus ( bus , devfn , where ) ;
if ( ! addr )
return PCIBIOS_DEVICE_NOT_FOUND ;
if ( size = = 1 )
writeb ( val , addr ) ;
else if ( size = = 2 )
writew ( val , addr ) ;
else
writel ( val , addr ) ;
return PCIBIOS_SUCCESSFUL ;
}
EXPORT_SYMBOL_GPL ( pci_generic_config_write ) ;
int pci_generic_config_read32 ( struct pci_bus * bus , unsigned int devfn ,
int where , int size , u32 * val )
{
void __iomem * addr ;
addr = bus - > ops - > map_bus ( bus , devfn , where & ~ 0x3 ) ;
2021-11-18 17:03:14 +03:00
if ( ! addr )
2015-01-10 05:34:39 +03:00
return PCIBIOS_DEVICE_NOT_FOUND ;
* val = readl ( addr ) ;
if ( size < = 2 )
* val = ( * val > > ( 8 * ( where & 3 ) ) ) & ( ( 1 < < ( size * 8 ) ) - 1 ) ;
return PCIBIOS_SUCCESSFUL ;
}
EXPORT_SYMBOL_GPL ( pci_generic_config_read32 ) ;
int pci_generic_config_write32 ( struct pci_bus * bus , unsigned int devfn ,
int where , int size , u32 val )
{
void __iomem * addr ;
u32 mask , tmp ;
addr = bus - > ops - > map_bus ( bus , devfn , where & ~ 0x3 ) ;
if ( ! addr )
return PCIBIOS_DEVICE_NOT_FOUND ;
if ( size = = 4 ) {
writel ( val , addr ) ;
return PCIBIOS_SUCCESSFUL ;
}
2016-11-01 00:00:01 +03:00
/*
* In general , hardware that supports only 32 - bit writes on PCI is
* not spec - compliant . For example , software may perform a 16 - bit
* write . If the hardware only supports 32 - bit accesses , we must
* do a 32 - bit read , merge in the 16 bits we intend to write ,
* followed by a 32 - bit write . If the 16 bits we * don ' t * intend to
* write happen to have any RW1C ( write - one - to - clear ) bits set , we
* just inadvertently cleared something we shouldn ' t have .
*/
2020-08-06 07:14:55 +03:00
if ( ! bus - > unsafe_warn ) {
dev_warn ( & bus - > dev , " %d-byte config write to %04x:%02x:%02x.%d offset %#x may corrupt adjacent RW1C bits \n " ,
size , pci_domain_nr ( bus ) , bus - > number ,
PCI_SLOT ( devfn ) , PCI_FUNC ( devfn ) , where ) ;
bus - > unsafe_warn = 1 ;
}
2016-11-01 00:00:01 +03:00
mask = ~ ( ( ( 1 < < ( size * 8 ) ) - 1 ) < < ( ( where & 0x3 ) * 8 ) ) ;
2015-01-10 05:34:39 +03:00
tmp = readl ( addr ) & mask ;
tmp | = val < < ( ( where & 0x3 ) * 8 ) ;
writel ( tmp , addr ) ;
return PCIBIOS_SUCCESSFUL ;
}
EXPORT_SYMBOL_GPL ( pci_generic_config_write32 ) ;
2009-04-24 06:45:17 +04:00
/**
* pci_bus_set_ops - Set raw operations of pci bus
* @ bus : pci bus struct
* @ ops : new raw operations
*
* Return previous raw operations
*/
struct pci_ops * pci_bus_set_ops ( struct pci_bus * bus , struct pci_ops * ops )
{
struct pci_ops * old_ops ;
unsigned long flags ;
2010-02-17 17:35:19 +03:00
raw_spin_lock_irqsave ( & pci_lock , flags ) ;
2009-04-24 06:45:17 +04:00
old_ops = bus - > ops ;
bus - > ops = ops ;
2010-02-17 17:35:19 +03:00
raw_spin_unlock_irqrestore ( & pci_lock , flags ) ;
2009-04-24 06:45:17 +04:00
return old_ops ;
}
EXPORT_SYMBOL ( pci_bus_set_ops ) ;
2008-12-18 20:17:16 +03:00
2006-10-19 19:41:28 +04:00
/*
* The following routines are to prevent the user from accessing PCI config
* space when it ' s unsafe to do so . Some devices require this during BIST and
* we ' re required to prevent it during D - state transitions .
*
* We have a bit per device to indicate it ' s blocked and a global wait queue
* for callers to sleep on until devices are unblocked .
*/
2011-11-04 12:45:59 +04:00
static DECLARE_WAIT_QUEUE_HEAD ( pci_cfg_wait ) ;
2005-09-27 12:21:55 +04:00
2011-11-04 12:45:59 +04:00
static noinline void pci_wait_cfg ( struct pci_dev * dev )
PCI: Fix pci_cfg_wait queue locking problem
The pci_cfg_wait queue is used to prevent user-space config accesses to
devices while they are recovering from reset.
Previously we used these operations on pci_cfg_wait:
__add_wait_queue(&pci_cfg_wait, ...)
__remove_wait_queue(&pci_cfg_wait, ...)
wake_up_all(&pci_cfg_wait)
The wake_up acquires the wait queue lock, but the add and remove do not.
Originally these were all protected by the pci_lock, but cdcb33f98244
("PCI: Avoid possible deadlock on pci_lock and p->pi_lock"), moved
wake_up_all() outside pci_lock, so it could race with add/remove
operations, which caused occasional kernel panics, e.g., during vfio-pci
hotplug/unplug testing:
Unable to handle kernel read from unreadable memory at virtual address ffff802dac469000
Resolve this by using wait_event() instead of __add_wait_queue() and
__remove_wait_queue(). The wait queue lock is held by both wait_event()
and wake_up_all(), so it provides mutual exclusion.
Fixes: cdcb33f98244 ("PCI: Avoid possible deadlock on pci_lock and p->pi_lock")
Link: https://lore.kernel.org/linux-pci/79827f2f-9b43-4411-1376-b9063b67aee3@huawei.com/T/#u
Based-on: https://lore.kernel.org/linux-pci/20191210031527.40136-1-zhengxiang9@huawei.com/
Based-on-patch-by: Xiang Zheng <zhengxiang9@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Tested-by: Xiang Zheng <zhengxiang9@huawei.com>
Cc: Heyi Guo <guoheyi@huawei.com>
Cc: Biaoxiang Ye <yebiaoxiang@huawei.com>
2020-06-26 02:14:55 +03:00
__must_hold ( & pci_lock )
2006-10-19 19:41:28 +04:00
{
do {
2010-02-17 17:35:19 +03:00
raw_spin_unlock_irq ( & pci_lock ) ;
PCI: Fix pci_cfg_wait queue locking problem
The pci_cfg_wait queue is used to prevent user-space config accesses to
devices while they are recovering from reset.
Previously we used these operations on pci_cfg_wait:
__add_wait_queue(&pci_cfg_wait, ...)
__remove_wait_queue(&pci_cfg_wait, ...)
wake_up_all(&pci_cfg_wait)
The wake_up acquires the wait queue lock, but the add and remove do not.
Originally these were all protected by the pci_lock, but cdcb33f98244
("PCI: Avoid possible deadlock on pci_lock and p->pi_lock"), moved
wake_up_all() outside pci_lock, so it could race with add/remove
operations, which caused occasional kernel panics, e.g., during vfio-pci
hotplug/unplug testing:
Unable to handle kernel read from unreadable memory at virtual address ffff802dac469000
Resolve this by using wait_event() instead of __add_wait_queue() and
__remove_wait_queue(). The wait queue lock is held by both wait_event()
and wake_up_all(), so it provides mutual exclusion.
Fixes: cdcb33f98244 ("PCI: Avoid possible deadlock on pci_lock and p->pi_lock")
Link: https://lore.kernel.org/linux-pci/79827f2f-9b43-4411-1376-b9063b67aee3@huawei.com/T/#u
Based-on: https://lore.kernel.org/linux-pci/20191210031527.40136-1-zhengxiang9@huawei.com/
Based-on-patch-by: Xiang Zheng <zhengxiang9@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Tested-by: Xiang Zheng <zhengxiang9@huawei.com>
Cc: Heyi Guo <guoheyi@huawei.com>
Cc: Biaoxiang Ye <yebiaoxiang@huawei.com>
2020-06-26 02:14:55 +03:00
wait_event ( pci_cfg_wait , ! dev - > block_cfg_access ) ;
2010-02-17 17:35:19 +03:00
raw_spin_lock_irq ( & pci_lock ) ;
2011-11-04 12:45:59 +04:00
} while ( dev - > block_cfg_access ) ;
2005-09-27 12:21:55 +04:00
}
2011-04-17 19:20:32 +04:00
/* Returns 0 on success, negative values indicate error. */
2024-04-29 12:47:07 +03:00
# define PCI_USER_READ_CONFIG(size, type) \
2005-09-27 12:21:55 +04:00
int pci_user_read_config_ # # size \
( struct pci_dev * dev , int pos , type * val ) \
{ \
u32 data = - 1 ; \
2024-04-29 12:47:07 +03:00
int ret ; \
\
2011-04-17 19:20:32 +04:00
if ( PCI_ # # size # # _BAD ) \
return - EINVAL ; \
2024-04-29 12:47:07 +03:00
\
raw_spin_lock_irq ( & pci_lock ) ; \
2011-11-04 12:45:59 +04:00
if ( unlikely ( dev - > block_cfg_access ) ) \
pci_wait_cfg ( dev ) ; \
2006-10-19 19:41:28 +04:00
ret = dev - > bus - > ops - > read ( dev - > bus , dev - > devfn , \
2024-04-29 12:47:07 +03:00
pos , sizeof ( type ) , & data ) ; \
raw_spin_unlock_irq ( & pci_lock ) ; \
2021-11-18 17:03:12 +03:00
if ( ret ) \
PCI_SET_ERROR_RESPONSE ( val ) ; \
else \
* val = ( type ) data ; \
2024-04-29 12:47:07 +03:00
\
2014-05-21 09:23:30 +04:00
return pcibios_err_to_errno ( ret ) ; \
2012-06-11 09:27:19 +04:00
} \
EXPORT_SYMBOL_GPL ( pci_user_read_config_ # # size ) ;
2005-09-27 12:21:55 +04:00
2011-04-17 19:20:32 +04:00
/* Returns 0 on success, negative values indicate error. */
2015-12-28 00:21:11 +03:00
# define PCI_USER_WRITE_CONFIG(size, type) \
2005-09-27 12:21:55 +04:00
int pci_user_write_config_ # # size \
( struct pci_dev * dev , int pos , type val ) \
{ \
2024-04-29 12:47:07 +03:00
int ret ; \
\
2011-04-17 19:20:32 +04:00
if ( PCI_ # # size # # _BAD ) \
return - EINVAL ; \
2024-04-29 12:47:07 +03:00
\
raw_spin_lock_irq ( & pci_lock ) ; \
2011-11-04 12:45:59 +04:00
if ( unlikely ( dev - > block_cfg_access ) ) \
pci_wait_cfg ( dev ) ; \
2006-10-19 19:41:28 +04:00
ret = dev - > bus - > ops - > write ( dev - > bus , dev - > devfn , \
2024-04-29 12:47:07 +03:00
pos , sizeof ( type ) , val ) ; \
raw_spin_unlock_irq ( & pci_lock ) ; \
\
2014-05-21 09:23:30 +04:00
return pcibios_err_to_errno ( ret ) ; \
2012-06-11 09:27:19 +04:00
} \
EXPORT_SYMBOL_GPL ( pci_user_write_config_ # # size ) ;
2005-09-27 12:21:55 +04:00
PCI_USER_READ_CONFIG ( byte , u8 )
PCI_USER_READ_CONFIG ( word , u16 )
PCI_USER_READ_CONFIG ( dword , u32 )
PCI_USER_WRITE_CONFIG ( byte , u8 )
PCI_USER_WRITE_CONFIG ( word , u16 )
PCI_USER_WRITE_CONFIG ( dword , u32 )
/**
2011-11-04 12:45:59 +04:00
* pci_cfg_access_lock - Lock PCI config reads / writes
2005-09-27 12:21:55 +04:00
* @ dev : pci device struct
*
2011-11-04 12:45:59 +04:00
* When access is locked , any userspace reads or writes to config
* space and concurrent lock requests will sleep until access is
2017-03-28 03:46:14 +03:00
* allowed via pci_cfg_access_unlock ( ) again .
2006-10-19 19:41:28 +04:00
*/
2011-11-04 12:45:59 +04:00
void pci_cfg_access_lock ( struct pci_dev * dev )
{
might_sleep ( ) ;
raw_spin_lock_irq ( & pci_lock ) ;
if ( dev - > block_cfg_access )
pci_wait_cfg ( dev ) ;
dev - > block_cfg_access = 1 ;
raw_spin_unlock_irq ( & pci_lock ) ;
}
EXPORT_SYMBOL_GPL ( pci_cfg_access_lock ) ;
/**
* pci_cfg_access_trylock - try to lock PCI config reads / writes
* @ dev : pci device struct
*
* Same as pci_cfg_access_lock , but will return 0 if access is
* already locked , 1 otherwise . This function can be used from
* atomic contexts .
*/
bool pci_cfg_access_trylock ( struct pci_dev * dev )
2005-09-27 12:21:55 +04:00
{
unsigned long flags ;
2011-11-04 12:45:59 +04:00
bool locked = true ;
2005-09-27 12:21:55 +04:00
2010-02-17 17:35:19 +03:00
raw_spin_lock_irqsave ( & pci_lock , flags ) ;
2011-11-04 12:45:59 +04:00
if ( dev - > block_cfg_access )
locked = false ;
else
dev - > block_cfg_access = 1 ;
2010-02-17 17:35:19 +03:00
raw_spin_unlock_irqrestore ( & pci_lock , flags ) ;
2006-10-19 19:41:28 +04:00
2011-11-04 12:45:59 +04:00
return locked ;
2005-09-27 12:21:55 +04:00
}
2011-11-04 12:45:59 +04:00
EXPORT_SYMBOL_GPL ( pci_cfg_access_trylock ) ;
2005-09-27 12:21:55 +04:00
/**
2011-11-04 12:45:59 +04:00
* pci_cfg_access_unlock - Unlock PCI config reads / writes
2005-09-27 12:21:55 +04:00
* @ dev : pci device struct
*
2011-11-04 12:45:59 +04:00
* This function allows PCI config accesses to resume .
2006-10-19 19:41:28 +04:00
*/
2011-11-04 12:45:59 +04:00
void pci_cfg_access_unlock ( struct pci_dev * dev )
2005-09-27 12:21:55 +04:00
{
unsigned long flags ;
2010-02-17 17:35:19 +03:00
raw_spin_lock_irqsave ( & pci_lock , flags ) ;
2006-10-19 19:41:28 +04:00
2018-03-10 01:36:33 +03:00
/*
* This indicates a problem in the caller , but we don ' t need
* to kill them , unlike a double - block above .
*/
2011-11-04 12:45:59 +04:00
WARN_ON ( ! dev - > block_cfg_access ) ;
2006-10-19 19:41:28 +04:00
2011-11-04 12:45:59 +04:00
dev - > block_cfg_access = 0 ;
2010-02-17 17:35:19 +03:00
raw_spin_unlock_irqrestore ( & pci_lock , flags ) ;
2017-01-14 03:05:12 +03:00
wake_up_all ( & pci_cfg_wait ) ;
2005-09-27 12:21:55 +04:00
}
2011-11-04 12:45:59 +04:00
EXPORT_SYMBOL_GPL ( pci_cfg_access_unlock ) ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
static inline int pcie_cap_version ( const struct pci_dev * dev )
{
2013-01-26 04:55:45 +04:00
return pcie_caps_reg ( dev ) & PCI_EXP_FLAGS_VERS ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
}
2014-11-11 23:09:46 +03:00
bool pcie_cap_has_lnkctl ( const struct pci_dev * dev )
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
{
int type = pci_pcie_type ( dev ) ;
2013-08-28 21:33:53 +04:00
return type = = PCI_EXP_TYPE_ENDPOINT | |
2013-08-27 19:54:40 +04:00
type = = PCI_EXP_TYPE_LEG_END | |
type = = PCI_EXP_TYPE_ROOT_PORT | |
type = = PCI_EXP_TYPE_UPSTREAM | |
type = = PCI_EXP_TYPE_DOWNSTREAM | |
type = = PCI_EXP_TYPE_PCI_BRIDGE | |
type = = PCI_EXP_TYPE_PCIE_BRIDGE ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
}
2022-09-17 15:03:09 +03:00
bool pcie_cap_has_lnkctl2 ( const struct pci_dev * dev )
{
return pcie_cap_has_lnkctl ( dev ) & & pcie_cap_version ( dev ) > 1 ;
}
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
static inline bool pcie_cap_has_sltctl ( const struct pci_dev * dev )
{
2015-06-25 00:05:54 +03:00
return pcie_downstream_port ( dev ) & &
2013-08-28 22:01:03 +04:00
pcie_caps_reg ( dev ) & PCI_EXP_FLAGS_SLOT ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
}
2019-10-18 19:52:21 +03:00
bool pcie_cap_has_rtctl ( const struct pci_dev * dev )
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
{
int type = pci_pcie_type ( dev ) ;
2013-08-28 21:33:53 +04:00
return type = = PCI_EXP_TYPE_ROOT_PORT | |
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
type = = PCI_EXP_TYPE_RC_EC ;
}
static bool pcie_capability_reg_implemented ( struct pci_dev * dev , int pos )
{
if ( ! pci_is_pcie ( dev ) )
return false ;
switch ( pos ) {
2013-02-14 22:35:42 +04:00
case PCI_EXP_FLAGS :
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
return true ;
case PCI_EXP_DEVCAP :
case PCI_EXP_DEVCTL :
case PCI_EXP_DEVSTA :
2013-08-28 22:03:42 +04:00
return true ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
case PCI_EXP_LNKCAP :
case PCI_EXP_LNKCTL :
case PCI_EXP_LNKSTA :
return pcie_cap_has_lnkctl ( dev ) ;
case PCI_EXP_SLTCAP :
case PCI_EXP_SLTCTL :
case PCI_EXP_SLTSTA :
return pcie_cap_has_sltctl ( dev ) ;
case PCI_EXP_RTCTL :
case PCI_EXP_RTCAP :
case PCI_EXP_RTSTA :
return pcie_cap_has_rtctl ( dev ) ;
case PCI_EXP_DEVCAP2 :
case PCI_EXP_DEVCTL2 :
2022-09-17 15:03:09 +03:00
return pcie_cap_version ( dev ) > 1 ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
case PCI_EXP_LNKCAP2 :
case PCI_EXP_LNKCTL2 :
case PCI_EXP_LNKSTA2 :
2022-09-17 15:03:09 +03:00
return pcie_cap_has_lnkctl2 ( dev ) ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
default :
return false ;
}
}
/*
* Note that these accessor functions are only for the " PCI Express
* Capability " (see PCIe spec r3.0, sec 7.8). They do not apply to the
* other " PCI Express Extended Capabilities " ( AER , VC , ACS , MFVC , etc . )
*/
int pcie_capability_read_word ( struct pci_dev * dev , int pos , u16 * val )
{
int ret ;
* val = 0 ;
if ( pos & 1 )
2020-06-15 10:32:25 +03:00
return PCIBIOS_BAD_REGISTER_NUMBER ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
if ( pcie_capability_reg_implemented ( dev , pos ) ) {
ret = pci_read_config_word ( dev , pci_pcie_cap ( dev ) + pos , val ) ;
/*
2021-11-18 17:03:32 +03:00
* Reset * val to 0 if pci_read_config_word ( ) fails ; it may
* have been written as 0xFFFF ( PCI_ERROR_RESPONSE ) if the
* config read failed on PCI .
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
*/
if ( ret )
* val = 0 ;
return ret ;
}
/*
* For Functions that do not implement the Slot Capabilities ,
* Slot Status , and Slot Control registers , these spaces must
* be hardwired to 0 b , with the exception of the Presence Detect
* State bit in the Slot Status register of Downstream Ports ,
* which must be hardwired to 1 b . ( PCIe Base Spec 3.0 , sec 7.8 )
*/
2015-06-25 00:05:54 +03:00
if ( pci_is_pcie ( dev ) & & pcie_downstream_port ( dev ) & &
pos = = PCI_EXP_SLTSTA )
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
* val = PCI_EXP_SLTSTA_PDS ;
return 0 ;
}
EXPORT_SYMBOL ( pcie_capability_read_word ) ;
int pcie_capability_read_dword ( struct pci_dev * dev , int pos , u32 * val )
{
int ret ;
* val = 0 ;
if ( pos & 3 )
2020-06-15 10:32:25 +03:00
return PCIBIOS_BAD_REGISTER_NUMBER ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
if ( pcie_capability_reg_implemented ( dev , pos ) ) {
ret = pci_read_config_dword ( dev , pci_pcie_cap ( dev ) + pos , val ) ;
/*
2021-11-18 17:03:32 +03:00
* Reset * val to 0 if pci_read_config_dword ( ) fails ; it may
* have been written as 0xFFFFFFFF ( PCI_ERROR_RESPONSE ) if
* the config read failed on PCI .
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
*/
if ( ret )
* val = 0 ;
return ret ;
}
2015-06-25 00:05:54 +03:00
if ( pci_is_pcie ( dev ) & & pcie_downstream_port ( dev ) & &
pos = = PCI_EXP_SLTSTA )
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
* val = PCI_EXP_SLTSTA_PDS ;
return 0 ;
}
EXPORT_SYMBOL ( pcie_capability_read_dword ) ;
int pcie_capability_write_word ( struct pci_dev * dev , int pos , u16 val )
{
if ( pos & 1 )
2020-06-15 10:32:25 +03:00
return PCIBIOS_BAD_REGISTER_NUMBER ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
if ( ! pcie_capability_reg_implemented ( dev , pos ) )
return 0 ;
return pci_write_config_word ( dev , pci_pcie_cap ( dev ) + pos , val ) ;
}
EXPORT_SYMBOL ( pcie_capability_write_word ) ;
int pcie_capability_write_dword ( struct pci_dev * dev , int pos , u32 val )
{
if ( pos & 3 )
2020-06-15 10:32:25 +03:00
return PCIBIOS_BAD_REGISTER_NUMBER ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
if ( ! pcie_capability_reg_implemented ( dev , pos ) )
return 0 ;
return pci_write_config_dword ( dev , pci_pcie_cap ( dev ) + pos , val ) ;
}
EXPORT_SYMBOL ( pcie_capability_write_dword ) ;
2023-07-17 15:04:53 +03:00
int pcie_capability_clear_and_set_word_unlocked ( struct pci_dev * dev , int pos ,
u16 clear , u16 set )
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
{
int ret ;
u16 val ;
ret = pcie_capability_read_word ( dev , pos , & val ) ;
2023-08-24 21:40:29 +03:00
if ( ret )
return ret ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
2023-08-24 21:40:29 +03:00
val & = ~ clear ;
val | = set ;
return pcie_capability_write_word ( dev , pos , val ) ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
}
2023-07-17 15:04:53 +03:00
EXPORT_SYMBOL ( pcie_capability_clear_and_set_word_unlocked ) ;
int pcie_capability_clear_and_set_word_locked ( struct pci_dev * dev , int pos ,
u16 clear , u16 set )
{
unsigned long flags ;
int ret ;
spin_lock_irqsave ( & dev - > pcie_cap_lock , flags ) ;
ret = pcie_capability_clear_and_set_word_unlocked ( dev , pos , clear , set ) ;
spin_unlock_irqrestore ( & dev - > pcie_cap_lock , flags ) ;
return ret ;
}
EXPORT_SYMBOL ( pcie_capability_clear_and_set_word_locked ) ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
int pcie_capability_clear_and_set_dword ( struct pci_dev * dev , int pos ,
u32 clear , u32 set )
{
int ret ;
u32 val ;
ret = pcie_capability_read_dword ( dev , pos , & val ) ;
2023-08-24 21:40:29 +03:00
if ( ret )
return ret ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
2023-08-24 21:40:29 +03:00
val & = ~ clear ;
val | = set ;
return pcie_capability_write_dword ( dev , pos , val ) ;
PCI: Add accessors for PCI Express Capability
The PCI Express Capability (PCIe spec r3.0, sec 7.8) comes in two
versions, v1 and v2. In v1 Capability structures (PCIe spec r1.0 and
r1.1), some fields are optional, so the structure size depends on the
device type.
This patch adds functions to access this capability so drivers don't
have to be aware of the differences between v1 and v2. Note that these
new functions apply only to the "PCI Express Capability," not to any of
the other "PCI Express Extended Capabilities" (AER, VC, ACS, MFVC, etc.)
Function pcie_capability_read_word/dword() reads the PCIe Capabilities
register and returns the value in the reference parameter "val". If
the PCIe Capabilities register is not implemented on the PCIe device,
"val" is set to 0.
Function pcie_capability_write_word/dword() writes the value to the
specified PCIe Capability register.
Function pcie_capability_clear_and_set_word/dword() sets and/or clears bits
of a PCIe Capability register.
[bhelgaas: changelog, drop "pci_" prefixes, don't export
pcie_capability_reg_implemented()]
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
2012-07-24 13:20:05 +04:00
}
EXPORT_SYMBOL ( pcie_capability_clear_and_set_dword ) ;
2017-02-07 22:32:33 +03:00
int pci_read_config_byte ( const struct pci_dev * dev , int where , u8 * val )
{
2017-03-30 06:49:06 +03:00
if ( pci_dev_is_disconnected ( dev ) ) {
2021-11-18 17:03:13 +03:00
PCI_SET_ERROR_RESPONSE ( val ) ;
2017-05-23 22:36:58 +03:00
return PCIBIOS_DEVICE_NOT_FOUND ;
2017-03-30 06:49:06 +03:00
}
2017-02-07 22:32:33 +03:00
return pci_bus_read_config_byte ( dev - > bus , dev - > devfn , where , val ) ;
}
EXPORT_SYMBOL ( pci_read_config_byte ) ;
int pci_read_config_word ( const struct pci_dev * dev , int where , u16 * val )
{
2017-03-30 06:49:06 +03:00
if ( pci_dev_is_disconnected ( dev ) ) {
2021-11-18 17:03:13 +03:00
PCI_SET_ERROR_RESPONSE ( val ) ;
2017-05-23 22:36:58 +03:00
return PCIBIOS_DEVICE_NOT_FOUND ;
2017-03-30 06:49:06 +03:00
}
2017-02-07 22:32:33 +03:00
return pci_bus_read_config_word ( dev - > bus , dev - > devfn , where , val ) ;
}
EXPORT_SYMBOL ( pci_read_config_word ) ;
int pci_read_config_dword ( const struct pci_dev * dev , int where ,
u32 * val )
{
2017-03-30 06:49:06 +03:00
if ( pci_dev_is_disconnected ( dev ) ) {
2021-11-18 17:03:13 +03:00
PCI_SET_ERROR_RESPONSE ( val ) ;
2017-05-23 22:36:58 +03:00
return PCIBIOS_DEVICE_NOT_FOUND ;
2017-03-30 06:49:06 +03:00
}
2017-02-07 22:32:33 +03:00
return pci_bus_read_config_dword ( dev - > bus , dev - > devfn , where , val ) ;
}
EXPORT_SYMBOL ( pci_read_config_dword ) ;
int pci_write_config_byte ( const struct pci_dev * dev , int where , u8 val )
{
2017-03-30 06:49:06 +03:00
if ( pci_dev_is_disconnected ( dev ) )
2017-05-23 22:36:58 +03:00
return PCIBIOS_DEVICE_NOT_FOUND ;
2017-02-07 22:32:33 +03:00
return pci_bus_write_config_byte ( dev - > bus , dev - > devfn , where , val ) ;
}
EXPORT_SYMBOL ( pci_write_config_byte ) ;
int pci_write_config_word ( const struct pci_dev * dev , int where , u16 val )
{
2017-03-30 06:49:06 +03:00
if ( pci_dev_is_disconnected ( dev ) )
2017-05-23 22:36:58 +03:00
return PCIBIOS_DEVICE_NOT_FOUND ;
2017-02-07 22:32:33 +03:00
return pci_bus_write_config_word ( dev - > bus , dev - > devfn , where , val ) ;
}
EXPORT_SYMBOL ( pci_write_config_word ) ;
int pci_write_config_dword ( const struct pci_dev * dev , int where ,
u32 val )
{
2017-03-30 06:49:06 +03:00
if ( pci_dev_is_disconnected ( dev ) )
2017-05-23 22:36:58 +03:00
return PCIBIOS_DEVICE_NOT_FOUND ;
2017-02-07 22:32:33 +03:00
return pci_bus_write_config_dword ( dev - > bus , dev - > devfn , where , val ) ;
}
EXPORT_SYMBOL ( pci_write_config_dword ) ;
2023-12-08 05:56:50 +03:00
void pci_clear_and_set_config_dword ( const struct pci_dev * dev , int pos ,
u32 clear , u32 set )
{
u32 val ;
pci_read_config_dword ( dev , pos , & val ) ;
val & = ~ clear ;
val | = set ;
pci_write_config_dword ( dev , pos , val ) ;
}
EXPORT_SYMBOL ( pci_clear_and_set_config_dword ) ;