summaryrefslogtreecommitdiff
path: root/doc/driver-model/UDM-pcmcia.txt
blob: fc31461ca7229873b78d7ce7ff87e38e3d2c882e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
The U-Boot Driver Model Project
===============================
PCMCIA analysis
===============
Viktor Krivak <viktor.krivak@gmail.com>
2012-03-17

I) Overview
-----------

  U-boot implements only 2 methods to interoperate with pcmcia. One to turn
  device on and other to turn device off. Names of these methods are usually
  pcmcia_on() and pcmcia_off() without any parameters. Some files in driver
  directory implements only internal API. These methods aren't used outside
  driver directory and they are not converted to new driver model.

II) Approach
-----------

  1) New API
  ----------

    Current API is preserved and all internal methods are hiden.

    struct ops {
      void (*pcmcia_on)(struct instance *i);
      void (*pcmcia_off)(struct instance *i);
    }

  2) Conversion
  -------------

    In header file pcmcia.h are some other variables which are used for
    additional configuration. But all have to be moved to platform data or to
    specific driver implementation.

  3) Platform data
  ----------------

    Many boards have custom implementation of internal API. Pointers to these
    methods are stored in platform_data. But the most implementations for Intel
    82365 and compatible PC Card controllers and Yenta-compatible
    PCI-to-CardBus controllers implement whole API per board. In these cases
    pcmcia_on() and pcmcia_off() behave only as wrappers and call specific
    board methods.

III) Analysis of in-tree drivers
--------------------------------

  1) i82365.c
  -----------
    Driver methods have different name i82365_init() and i82365_exit but
    all functionality is the same. Board files board/atc/ti113x.c and
    board/cpc45/pd67290.c use their own implementation of these method.
    In this case all methods in driver behave only as wrappers.

  2) marubun_pcmcia.c
  -------------------
    Meets standard API behaviour. Simple conversion.

  3) mpc8xx_pcmcia.c
  ------------------
    Meets standard API behaviour. Simple conversion.

  4) rpx_pcmcia.c
  ---------------
    Implements only internal API used in other drivers. Non of methods
    implemented here are used outside driver model.

  5) ti_pci1410a.c
  ----------------
    Has different API but methods in this file are never called. Probably
    dead code.

  6)tqm8xx_pcmcia.c
  -----------------
    Implements only internal API used in other drivers. Non of methods
    implemented here are used outside driver model.