1csx_AccessConfigurationRegKiesrtneerl(9FFu)nctions focrsxD_rAicvceersssConfigurationRegister(9F)
2
3
4
6 csx_AccessConfigurationRegister - read or write a PC Card Configuration
7 Register
8
10 #include <sys/pccard.h>
11
12
13
14 int32_t csx_AccessConfigurationRegister(client_handle_t ch,
15 access_config_reg_t *acr);
16
17
19 Solaris DDI Specific (Solaris DDI)
20
22 ch Client handle returned from csx_RegisterClient(9F).
23
24
25 acr Pointer to an access_config_reg_t structure.
26
27
29 This function allows a client to read or write a PCCard Configuration
30 Register.
31
33 The structure members of access_config_reg_t are:
34
35 uint32_t Socket; /* socket number*/
36 uint32_t Action; /* register access operation*/
37 uint32_t Offset; /* config register offset*/
38 uint32_t Value; /* value read or written*/
39
40
41
42 The fields are defined as follows:
43
44 Socket Not used in Solaris, but for portability with other Card Ser‐
45 vices implementations, it should be set to the logical socket
46 number.
47
48
49 Action May be set to CONFIG_REG_READ or CONFIG_REG_WRITE. All other
50 values in the Action field are reserved for future use. If
51 the Action field is set to CONFIG_REG_WRITE, the Value field
52 is written to the specified configuration register. Card Ser‐
53 vices does not read the configuration register after a write
54 operation. For that reason, the Value field is only updated
55 by a CONFIG_REG_READ request.
56
57
58 Offset Specifies the byte offset for the desired configuration reg‐
59 ister from the PC Card configuration register base specified
60 in csx_RequestConfiguration(9F).
61
62
63 Value Contains the value read from the PC Card Configuration Regis‐
64 ter for a read operation. For a write operation, the Value
65 field contains the value to write to the configuration regis‐
66 ter. As noted above, on return from a write request, the
67 Value field is the value written to the PC Card and not any
68 changed value that may have resulted from the write request
69 (that is, no read after write is performed).
70
71
72
73 A client must be very careful when writing to the COR (Configuration
74 Option Register) at offset 0. This has the potential to change the type
75 of interrupt request generated by the PC Card or place the card in the
76 reset state. Either request may have undefined results. The client
77 should read the register to determine the appropriate setting for the
78 interrupt mode (Bit 6) before writing to the register.
79
80
81 If a client wants to reset a PCCard, the csx_ResetFunction(9F) function
82 should be used. Unlike csx_AccessConfigurationRegister(), the
83 csx_ResetFunction(9F) function generates a series of event notifica‐
84 tions to all clients using the PC Card, so they can re-establish the
85 appropriate card state after the reset operation is complete.
86
88 CS_SUCCESS Successful operation.
89
90
91 CS_BAD_ARGS Specified arguments are invalid. Client
92 specifies an Offset that is out of range or
93 neither CONFIG_REG_READ or CONFIG_REG_WRITE
94 is set.
95
96
97 CS_UNSUPPORTED_MODE Client has not called csx_RequestConfigura‐
98 tion(9F) before calling this function.
99
100
101 CS_BAD_HANDLE Client handle is invalid.
102
103
104 CS_NO_CARD No PC card in socket.
105
106
107 CS_UNSUPPORTED_FUNCTION No PCMCIA hardware installed.
108
109
111 This function may be called from user or kernel context.
112
114 csx_ParseTuple(9F), csx_RegisterClient(9F), csx_RequestConfigura‐
115 tion(9F), csx_ResetFunction(9F)
116
117
118 PCCard 95 Standard, PCMCIA/JEIDA
119
120
121
122SunOS 5.11 19 Jul 199c6sx_AccessConfigurationRegister(9F)