13 Tutorial</title><shortdesc>Explains how to use the MMC Controller interfaces to use MMC hardware.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
13 Tutorial</title><shortdesc>Explains how to use the MMC Controller interfaces to use MMC hardware.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
14 <section id="GUID-388CEB1C-BA81-593F-81D3-C0BD72A405E0"><title>Client interfaces</title> <p>The |
14 <section id="GUID-388CEB1C-BA81-593F-81D3-C0BD72A405E0"><title>Client interfaces</title> <p>The |
15 following diagram shows the relationship between the Controller and its clients, |
15 following diagram shows the relationship between the Controller and its clients, |
16 and also shows aspects of the relationship between the constituent parts. |
16 and also shows aspects of the relationship between the constituent parts. |
17 In this case, the client is the MultiMediaCard driver, although in general |
17 In this case, the client is the MultiMediaCard driver, although in general |
18 this could be some other device driver. </p><fig id="GUID-108025DD-1333-4A3C-A507-7D61A42BCEA4"> |
18 this could be some other device driver. </p><fig id="GUID-FF02FE34-4E77-42DE-89BC-4D789E6A310D"> |
19 <image href="GUID-6597A895-37D5-51D1-86B3-E74F6E845899_d0e387797_href.png" placement="inline"/> |
19 <image href="GUID-6597A895-37D5-51D1-86B3-E74F6E845899_d0e409537_href.png" placement="inline"/> |
20 </fig> <p>The session is used to pass commands either to the entire stack, |
20 </fig> <p>The session is used to pass commands either to the entire stack, |
21 i.e. a broadcast command, or to individual cards in the stack. </p> <p>The |
21 i.e. a broadcast command, or to individual cards in the stack. </p> <p>The |
22 session provides access to the stack of cards, via a pointer to a stack object, |
22 session provides access to the stack of cards, via a pointer to a stack object, |
23 the <codeph>iStackP</codeph> private member. The session is used to pass commands |
23 the <codeph>iStackP</codeph> private member. The session is used to pass commands |
24 either to the entire stack, i.e. a broadcast command, or to individual cards |
24 either to the entire stack, i.e. a broadcast command, or to individual cards |
68 that session, the mechanism for locking the stack involves submitting a session |
68 that session, the mechanism for locking the stack involves submitting a session |
69 even though no bus activity results. If this session completes successfully |
69 even though no bus activity results. If this session completes successfully |
70 then the stack is locked. The client can then go ahead and invoke its series |
70 then the stack is locked. The client can then go ahead and invoke its series |
71 of commands - configuring that same session object as necessary each time |
71 of commands - configuring that same session object as necessary each time |
72 and submitting it. </p> </section> |
72 and submitting it. </p> </section> |
73 <section id="GUID-34C0B6CD-C9BF-4D75-BBAE-78D36B2879FF"><title>See also</title> <p> <xref href="GUID-9573F7B9-76E9-5DCB-A498-C0DE59606911.dita">Concepts</xref> </p> </section> |
73 <section id="GUID-4B239C05-3CCF-4FB5-BD11-DA7DFF52DA95"><title>See also</title> <p> <xref href="GUID-9573F7B9-76E9-5DCB-A498-C0DE59606911.dita">Concepts</xref> </p> </section> |
74 </conbody></concept> |
74 </conbody></concept> |