Hi Josh, On Thu, 15 Jan 2015 17:59:15 +0800 Josh Wu <josh.wu@xxxxxxxxx> wrote: > Hi， Boris > > Thanks for the review. > > On 1/15/2015 4:45 PM, Boris Brezillon wrote: > > Hi Josh, > > > > On Thu, 15 Jan 2015 15:08:03 +0800 > > Josh Wu <josh.wu@xxxxxxxxx> wrote: > > > >> To get NFC status, we need to read the NFC command registers, which is a > >> 256M memory mapping address. To check the status, you just read such > >> address from NFC command registers. > >> For example, to check NFCBUSY (bit 27), you need to read 0x08000000 > >> (bit 27 is set to 1) of the NFC command register. > >> If you want to check NFCBUSY (bit 27) and NFCWR (bit 26) in same time, > >> you need to read 0x0c000000 (bit 27 and bit 26 are set to 1). > > Are NFCBUSY and NFCWR found in NFCDATA_STATUS and those found in HSMC_SR > > representing the same thing. > yes. it is. I just check with IP team. The NFCBUSY of NFCDATA_STATUS is > also refer to NFC_BUSY of HSMC_SR. > > > If they are, I think you can just use HSMC_SR instead of NFCDATA_STATUS > > to check the status [1] and drop the last bit in the NFC Command > > Resgiters range. > Thank you. your code works (just need some typo change). > I want to send [1] code with your signed-off and my acked to mtd list. > Is it okay for you? Sure, no problem. -- Boris Brezillon, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
