From: nicolas.ferre@atmel•com (Nicolas Ferre)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: at91: dts: sama5d3/sama5d4: reduce NFC command registers memory region
Date: Wed, 4 Mar 2015 16:19:18 +0100 [thread overview]
Message-ID: <54F72276.8060605@atmel.com> (raw)
In-Reply-To: <20150115110501.53b4584c@bbrezillon>
Le 15/01/2015 11:05, Boris Brezillon a ?crit :
> Hi Josh,
>
> On Thu, 15 Jan 2015 17:59:15 +0800
> Josh Wu <josh.wu@atmel•com> 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@atmel•com> 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.
Hi Josh,
What is the status of this patch set?
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2015-03-04 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 7:08 [PATCH] ARM: at91: dts: sama5d3/sama5d4: reduce NFC command registers memory region Josh Wu
2015-01-15 8:45 ` Boris Brezillon
2015-01-15 9:59 ` Josh Wu
2015-01-15 10:05 ` Boris Brezillon
2015-03-04 15:19 ` Nicolas Ferre [this message]
2015-03-05 1:52 ` Josh Wu
2015-03-05 9:13 ` Nicolas Ferre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54F72276.8060605@atmel.com \
--to=nicolas.ferre@atmel$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox