Documentation/pcmcia/driver-changes.rst

8    If `struct pcmcia_device *p_dev->config_flags` is set accordingly,
14 	- CONF_AUTO_CHECK_VCC : check for matching Vcc
15 	- CONF_AUTO_SET_VPP   : set Vpp
16 	- CONF_AUTO_AUDIO     : auto-enable audio line, if required
17 	- CONF_AUTO_SET_IO    : set ioport resources (->resource[0,1])
18 	- CONF_AUTO_SET_IOMEM : set first iomem resource (->resource[2])
20 * pcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)
28    `struct pcmcia_device *p_dev->resource[2,3,4,5]` for up to four ioport
30    are reserved and may be used immediately -- until pcmcia_release_window()
35    `struct pcmcia_device *p_dev->resource[0,1]` for up to two ioport
40 * No dev_info_t, no cs_types.h (as of 2.6.36)
41    dev_info_t and a few other typedefs are removed. No longer use them
45 * No dev_node_t (as of 2.6.35)
46    There is no more need to fill out a "dev_node_t" structure.
52    - calling request_irq/free_irq directly. Use the IRQ from `*p_dev->irq`.
53    - use pcmcia_request_irq(p_dev, handler_t); the PCMCIA core will
57 * no cs_error / CS_CHECK / CONFIG_PCMCIA_DEBUG (as of 2.6.33)
59    Linux-style checking of return values, and -- if necessary -- debug
71    configuration options. During a driver's probe() phase, one doesn't need
77    necessary now is calling pcmcia_disable_device. As there is no valid
87 * Move suspend, resume and reset out of event handler (as of 2.6.16)::
89        int (*suspend)          (struct pcmcia_device *dev);
93   (SUSPEND == RESET_PHYSICAL) and (RESUME == CARD_RESET) events
102 * in-kernel device<->driver matching (as of 2.6.13)
115    The irq_mask and irq_list parameters should no longer be used in
117    determine which IRQ should be used. Therefore, link->irq.IRQInfo2
120 * client->PendingEvents is gone (as of 2.6.11)
121    client->PendingEvents is no longer available.
123 * client->Attributes are gone (as of 2.6.11)
124    client->Attributes is unused, therefore it is removed from all
127 * core functions no longer available (as of 2.6.11)
129    because they are unused by all in-kernel drivers, and no external
140    It is no longer necessary to iterate on the driver's internal
141    client list and call the ->detach() function upon module removal.
145    it no longer marks these resources busy. This means that driver
148    your IO regions in-use, and request_mem_region() to mark your
149    memory regions in-use. The name argument should be a pointer to