lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 18 Feb 2019 12:28:56 +0000 From: <Nicolas.Ferre@...rochip.com> To: <alexandre.belloni@...tlin.com>, <Ludovic.Desroches@...rochip.com>, <gregkh@...uxfoundation.org>, <robh+dt@...nel.org> CC: <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>, <linux-usb@...r.kernel.org>, <stern@...land.harvard.edu>, <Tudor.Ambarus@...rochip.com> Subject: Re: [RESEND PATCH] dt-bindings: arm: atmel: add new sam9x60 SFR binding 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@...rochip.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@...38000 { > -- Nicolas Ferre
Powered by blists - more mailing lists