All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 5 Mar 2015 10:13:13 +0100	[thread overview]
Message-ID: <54F81E29.7010605@atmel.com> (raw)
In-Reply-To: <54F7B6CE.8060403@atmel.com>

Le 05/03/2015 02:52, Josh Wu a ?crit :
> Hi, Nicolas
> 
> On 3/4/2015 11:19 PM, Nicolas Ferre wrote:
>> 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?
> 
> The v2 of this patch is sent. But it's not taken by Brain.
> I just ping Brain yesterday. Check the v2 patch here:
> http://patchwork.ozlabs.org/patch/431752/

Ok, thanks for the information Josh.

Bye,
-- 
Nicolas Ferre

WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
To: Josh Wu <josh.wu-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>,
	Boris Brezillon
	<boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Ian Campbell
	<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
	Alexandre Belloni
	<alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
	Jean-Christophe Plagniol-Villard
	<plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] ARM: at91: dts: sama5d3/sama5d4: reduce NFC command registers memory region
Date: Thu, 5 Mar 2015 10:13:13 +0100	[thread overview]
Message-ID: <54F81E29.7010605@atmel.com> (raw)
In-Reply-To: <54F7B6CE.8060403-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>

Le 05/03/2015 02:52, Josh Wu a écrit :
> Hi, Nicolas
> 
> On 3/4/2015 11:19 PM, Nicolas Ferre wrote:
>> 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-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org> 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-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org> 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?
> 
> The v2 of this patch is sent. But it's not taken by Brain.
> I just ping Brain yesterday. Check the v2 patch here:
> http://patchwork.ozlabs.org/patch/431752/

Ok, thanks for the information Josh.

Bye,
-- 
Nicolas Ferre
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-03-05  9:13 UTC|newest]

Thread overview: 14+ 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  7:08 ` Josh Wu
2015-01-15  8:45 ` Boris Brezillon
2015-01-15  8:45   ` Boris Brezillon
2015-01-15  9:59   ` Josh Wu
2015-01-15  9:59     ` Josh Wu
2015-01-15 10:05     ` Boris Brezillon
2015-01-15 10:05       ` Boris Brezillon
2015-03-04 15:19       ` Nicolas Ferre
2015-03-04 15:19         ` Nicolas Ferre
2015-03-05  1:52         ` Josh Wu
2015-03-05  1:52           ` Josh Wu
2015-03-05  9:13           ` Nicolas Ferre [this message]
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=54F81E29.7010605@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.