6179b5562d
PCI drivers have the new_id file in sysfs which allows new IDs to be added at runtime. The advantage is to avoid re-compilation of a driver that works for a new device, but it's ID table doesn't contain the new device. This mechanism is only meant for testing, after the driver has been tested successfully, the ID should be added in source code so that new revisions of the kernel automatically detect the device. The implementation follows the PCI implementation. The interface is documented in Documentation/pcmcia/driver.txt. Computations should be done in userspace, so the sysfs string contains the raw structure members for matching. Signed-off-by: Bernhard Walle <bwalle@suse.de> Cc: Dominik Brodowski <linux@dominikbrodowski.net> Cc: Greg KH <greg@kroah.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
30 lines
987 B
Text
30 lines
987 B
Text
PCMCIA Driver
|
|
-------------
|
|
|
|
|
|
sysfs
|
|
-----
|
|
|
|
New PCMCIA IDs may be added to a device driver pcmcia_device_id table at
|
|
runtime as shown below:
|
|
|
|
echo "match_flags manf_id card_id func_id function device_no \
|
|
prod_id_hash[0] prod_id_hash[1] prod_id_hash[2] prod_id_hash[3]" > \
|
|
/sys/bus/pcmcia/drivers/{driver}/new_id
|
|
|
|
All fields are passed in as hexadecimal values (no leading 0x).
|
|
The meaning is described in the PCMCIA specification, the match_flags is
|
|
a bitwise or-ed combination from PCMCIA_DEV_ID_MATCH_* constants
|
|
defined in include/linux/mod_devicetable.h.
|
|
|
|
Once added, the driver probe routine will be invoked for any unclaimed
|
|
PCMCIA device listed in its (newly updated) pcmcia_device_id list.
|
|
|
|
A common use-case is to add a new device according to the manufacturer ID
|
|
and the card ID (form the manf_id and card_id file in the device tree).
|
|
For this, just use:
|
|
|
|
echo "0x3 manf_id card_id 0 0 0 0 0 0 0" > \
|
|
/sys/bus/pcmcia/drivers/{driver}/new_id
|
|
|
|
after loading the driver.
|