Driver changes

This file details changes in 2.6 which affect PCMCIA card driver authors:

  • pcmcia_loop_config() and autoconfiguration (as of 2.6.36)

    Ifstruct pcmcia_device *p_dev->config_flags is set accordingly,pcmcia_loop_config() now sets up certain configuration valuesautomatically, though the driver may still override the settingsin the callback function. The following autoconfiguration optionsare provided at the moment:

    • CONF_AUTO_CHECK_VCC : check for matching Vcc
    • CONF_AUTO_SET_VPP : set Vpp
    • CONF_AUTO_AUDIO : auto-enable audio line, if required
    • CONF_AUTO_SET_IO : set ioport resources (->resource[0,1])
    • CONF_AUTO_SET_IOMEM : set first iomem resource (->resource[2])
  • pcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)

    pcmcia_request_configuration() got renamed to pcmcia_enable_device(),as it mirrors pcmcia_disable_device(). Configuration settings are nowstored in struct pcmcia_device, e.g. in the fields config_flags,config_index, config_base, vpp.

  • pcmcia_request_window changes (as of 2.6.36)

    Instead of win_req_t, drivers are now requested to fill outstruct pcmcia_device *p_dev->resource[2,3,4,5] for up to four ioportranges. After a call to pcmcia_request_window(), the regions found thereare reserved and may be used immediately – until pcmcia_release_window()is called.

  • pcmcia_request_io changes (as of 2.6.36)

    Instead of io_req_t, drivers are now requested to fill outstruct pcmcia_device *p_dev->resource[0,1] for up to two ioportranges. After a call to pcmcia_request_io(), the ports found thereare reserved, after calling pcmcia_request_configuration(), they maybe used.

  • No dev_info_t, no cs_types.h (as of 2.6.36)

    dev_info_t and a few other typedefs are removed. No longer use themin PCMCIA device drivers. Also, do not include pcmcia/cs_types.h, asthis file is gone.

  • No dev_node_t (as of 2.6.35)

    There is no more need to fill out a “dev_node_t” structure.

  • New IRQ request rules (as of 2.6.35)

    Instead of the old pcmcia_request_irq() interface, drivers may nowchoose between:

    • calling request_irq/free_irq directly. Use the IRQ from*p_dev->irq.
    • use pcmcia_request_irq(p_dev, handler_t); the PCMCIA core willclean up automatically on calls to pcmcia_disable_device() ordevice ejection.
  • no cs_error / CS_CHECK / CONFIG_PCMCIA_DEBUG (as of 2.6.33)

    Instead of the cs_error() callback or the CS_CHECK() macro, please useLinux-style checking of return values, and – if necessary – debugmessages using “dev_dbg()” or “pr_debug()”.

  • New CIS tuple access (as of 2.6.33)

    Instead of pcmcia_get_{first,next}_tuple(), pcmcia_get_tuple_data() andpcmcia_parse_tuple(), a driver shall use “pcmcia_get_tuple()” if it isonly interested in one (raw) tuple, or “pcmcia_loop_tuple()” if it isinterested in all tuples of one type. To decode the MAC from CISTPL_FUNCE,a new helper “pcmcia_get_mac_from_cis()” was added.

  • New configuration loop helper (as of 2.6.28)

    By calling pcmcia_loop_config(), a driver can iterate over all availableconfiguration options. During a driver’s probe() phase, one doesn’t needto use pcmcia_get_{first,next}_tuple, pcmcia_get_tuple_data andpcmcia_parse_tuple directly in most if not all cases.

  • New release helper (as of 2.6.17)

    Instead of calling pcmcia_release_{configuration,io,irq,win}, all that’snecessary now is calling pcmcia_disable_device. As there is no validreason left to call pcmcia_release_io and pcmcia_release_irq, theexports for them were removed.

  • Unify detach and REMOVAL event code, as well as attach and INSERTIONcode (as of 2.6.16):

    void (*remove)          (struct pcmcia_device *dev);int (*probe)            (struct pcmcia_device *dev);

  • Move suspend, resume and reset out of event handler (as of 2.6.16):

    int (*suspend)          (struct pcmcia_device *dev);int (*resume)           (struct pcmcia_device *dev);

    should be initialized in struct pcmcia_driver, and handle(SUSPEND == RESET_PHYSICAL) and (RESUME == CARD_RESET) events

  • event handler initialization in struct pcmcia_driver (as of 2.6.13)

    The event handler is notified of all events, and must be initializedas the event() callback in the driver’s struct pcmcia_driver.

  • pcmcia/version.h should not be used (as of 2.6.13)

    This file will be removed eventually.

  • in-kernel device<->driver matching (as of 2.6.13)

    PCMCIA devices and their correct drivers can now be matched inkernelspace. See ‘devicetable.txt’ for details.

  • Device model integration (as of 2.6.11)

    A struct pcmcia_device is registered with the device model core,and can be used (e.g. for SET_NETDEV_DEV) by usinghandle_to_dev(client_handle_t * handle).

  • Convert internal I/O port addresses to unsigned int (as of 2.6.11)

    ioaddr_t should be replaced by unsigned int in PCMCIA card drivers.

  • irq_mask and irq_list parameters (as of 2.6.11)

    The irq_mask and irq_list parameters should no longer be used inPCMCIA card drivers. Instead, it is the job of the PCMCIA core todetermine which IRQ should be used. Therefore, link->irq.IRQInfo2is ignored.

  • client->PendingEvents is gone (as of 2.6.11)

    client->PendingEvents is no longer available.

  • client->Attributes are gone (as of 2.6.11)

    client->Attributes is unused, therefore it is removed from allPCMCIA card drivers

  • core functions no longer available (as of 2.6.11)

    The following functions have been removed from the kernel sourcebecause they are unused by all in-kernel drivers, and no externaldriver was reported to rely on them:

    pcmcia_get_first_region()pcmcia_get_next_region()pcmcia_modify_window()pcmcia_set_event_mask()pcmcia_get_first_window()pcmcia_get_next_window()
  • device list iteration upon module removal (as of 2.6.10)

    It is no longer necessary to iterate on the driver’s internalclient list and call the ->detach() function upon module removal.

  • Resource management. (as of 2.6.8)

    Although the PCMCIA subsystem will allocate resources for cards,it no longer marks these resources busy. This means that driverauthors are now responsible for claiming your resources as perother drivers in Linux. You should use request_region() to markyour IO regions in-use, and request_mem_region() to mark yourmemory regions in-use. The name argument should be a pointer toyour driver name. Eg, for pcnet_cs, name should point to thestring “pcnet_cs”.

  • CardServices is goneCardServices() in 2.4 is just a big switch statement to call variousservices. In 2.6, all of those entry points are exported and calleddirectly (except for pcmcia_report_error(), just use cs_error() instead).

  • struct pcmcia_driverYou need to use struct pcmcia_driver and pcmcia_{un,}register_driverinstead of {un,}register_pccard_driver