Symbian3/PDK/Source/GUID-745273E3-BB3A-59BF-9C33-6C8BB3D850A9.dita
changeset 5 f345bda72bc4
parent 1 25a17d01db0c
equal deleted inserted replaced
4:4816d766a08a 5:f345bda72bc4
     9 -->
     9 -->
    10 <!DOCTYPE concept
    10 <!DOCTYPE concept
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
    12 <concept id="GUID-745273E3-BB3A-59BF-9C33-6C8BB3D850A9" xml:lang="en"><title>GPIO
    12 <concept id="GUID-745273E3-BB3A-59BF-9C33-6C8BB3D850A9" xml:lang="en"><title>GPIO
    13 Design Considerations</title><shortdesc> General design considerations involved in implementing the Symbian
    13 Design Considerations</title><shortdesc> General design considerations involved in implementing the Symbian
    14 platform <apiname>GPIO</apiname> class.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
    14 platform <codeph>GPIO</codeph> class.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
    15 <section id="GUID-CC35EB0E-6156-50F9-9AFC-7D89F2BE2D8A"><title>Pin IDs</title> <p>To
    15 <section id="GUID-CC35EB0E-6156-50F9-9AFC-7D89F2BE2D8A"><title>Pin IDs</title> <p>To
    16 manipulate a GPIO interface at the level of the pin it is necessary to have
    16 manipulate a GPIO interface at the level of the pin it is necessary to have
    17 a method of specifying individual pins which is both systematic and intuitive.
    17 a method of specifying individual pins which is both systematic and intuitive.
    18 For the purposes of porting we need a systematic way of identifying a pin
    18 For the purposes of porting we need a systematic way of identifying a pin
    19 by its module and bit number: this means specifying the module by its register
    19 by its module and bit number: this means specifying the module by its register
   247 is expected that the implementation of all the API functions will involve
   247 is expected that the implementation of all the API functions will involve
   248 the use of locks. In principle locks are not necessary where a function can
   248 the use of locks. In principle locks are not necessary where a function can
   249 be implemented exclusively by a single read, write or modify call to the hardware
   249 be implemented exclusively by a single read, write or modify call to the hardware
   250 register API. </p> </section>
   250 register API. </p> </section>
   251 </conbody><related-links>
   251 </conbody><related-links>
   252 <link href="GUID-0E15C8C4-E511-569F-8AB4-895CA00331AB.dita"><linktext>GPIO Features</linktext>
       
   253 </link>
       
   254 <link href="GUID-48AEF60B-D2B6-55B5-96FD-55C1F1868A3F.dita"><linktext>GPIO Implementation
   252 <link href="GUID-48AEF60B-D2B6-55B5-96FD-55C1F1868A3F.dita"><linktext>GPIO Implementation
   255 Guide</linktext></link>
   253 Guide</linktext></link>
   256 </related-links></concept>
   254 </related-links></concept>