* [RESEND PATCH] dt-bindings: arm: atmel: add new sam9x60 SFR binding
@ 2019-02-06 18:04 Nicolas Ferre
2019-02-18 12:28 ` Nicolas.Ferre
0 siblings, 1 reply; 2+ messages in thread
From: Nicolas Ferre @ 2019-02-06 18:04 UTC (permalink / raw)
To: Alexandre Belloni, Ludovic Desroches, linux-arm-kernel,
Greg Kroah-Hartman, Rob Herring
Cc: linux-kernel, devicetree, linux-usb, Alan Stern, Nicolas Ferre
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.
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 {
--
2.17.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [RESEND PATCH] dt-bindings: arm: atmel: add new sam9x60 SFR binding
2019-02-06 18:04 [RESEND PATCH] dt-bindings: arm: atmel: add new sam9x60 SFR binding Nicolas Ferre
@ 2019-02-18 12:28 ` Nicolas.Ferre
0 siblings, 0 replies; 2+ messages in thread
From: Nicolas.Ferre @ 2019-02-18 12:28 UTC (permalink / raw)
To: alexandre.belloni, Ludovic.Desroches, gregkh, robh+dt
Cc: linux-arm-kernel, linux-kernel, devicetree, linux-usb, stern,
Tudor.Ambarus
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-02-18 12:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-06 18:04 [RESEND PATCH] dt-bindings: arm: atmel: add new sam9x60 SFR binding Nicolas Ferre
2019-02-18 12:28 ` Nicolas.Ferre
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).