mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Nicolas.Ferre@microchip.com>
To: <alexandre.belloni@bootlin.com>,
	<Ludovic.Desroches@microchip.com>, <gregkh@linuxfoundation.org>,
	<robh+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-usb@vger.kernel.org>, <stern@rowland.harvard.edu>,
	<Tudor.Ambarus@microchip.com>
Subject: Re: [RESEND PATCH] dt-bindings: arm: atmel: add new sam9x60 SFR binding
Date: Mon, 18 Feb 2019 12:28:56 +0000	[thread overview]
Message-ID: <51c2d2af-3d2f-0fa8-c9e7-5fc6a4f1a1b4@microchip.com> (raw)
In-Reply-To: <20190206180425.27324-1-nicolas.ferre@microchip.com>

On 06/02/2019 at 19:04, Nicolas Ferre wrote:
> Add this SFR compatible definition for the sam9x60 SoC. Will be needed
> in OHCI driver: ohci-at91.c.
> 
> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> Hi Rob,
> It seems that this patch was lost in my series "[PATCH 0/8] ARM: at91/dt:
> update to existing drivers for the sam9x60 SoC". I split it and resend it only
> for USB tree.

Rob,

Ping...


> Hi Greg,
> 
> This DT bindind goes with the patch already queued in your usb-next tree "USB:
> host: ohci-at91: add sam9x60-sfr definition for ohci".
> 
> Once Rob added his tag, can you please queue it in your tree as I reviewed my
> first idea of adding it to the arm-soc tree?
> 
> Best regards,
>    Nicolas
> 
>   Documentation/devicetree/bindings/arm/atmel-sysregs.txt | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
> index badce6ef3ab3..dfc91bc02b97 100644
> --- a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
> +++ b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
> @@ -148,6 +148,7 @@ required properties:
>   - compatible: Should be "atmel,<chip>-sfr", "syscon" or
>   	"atmel,<chip>-sfrbu", "syscon"
>     <chip> can be "sama5d3", "sama5d4" or "sama5d2".
> +  It also can be "microchip,sam9x60-sfr", "syscon".
>   - reg: Should contain registers location and length
>   
>   	sfr@f0038000 {
> 


-- 
Nicolas Ferre

      reply	other threads:[~2019-02-18 12:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 18:04 Nicolas Ferre
2019-02-18 12:28 ` Nicolas.Ferre [this message]

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=51c2d2af-3d2f-0fa8-c9e7-5fc6a4f1a1b4@microchip.com \
    --to=nicolas.ferre@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=Tudor.Ambarus@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®