Hi Biju-san, > From: Biju Das, Sent: Friday, October 12, 2018 5:32 PM > > Hi Shimoda-San, > > Thanks for the patch. > > > -----Original Message----- > > From: [email protected] <linux-renesas-soc- > > [email protected]> On Behalf Of Yoshihiro Shimoda > > Sent: 09 October 2018 11:45 <snip> > > diff --git a/arch/arm64/boot/dts/renesas/r8a77990.dtsi > > b/arch/arm64/boot/dts/renesas/r8a77990.dtsi > > index 7278cd5..e3726307 100644 > > --- a/arch/arm64/boot/dts/renesas/r8a77990.dtsi > > +++ b/arch/arm64/boot/dts/renesas/r8a77990.dtsi > > @@ -357,6 +357,51 @@ > > resets = <&cpg 407>; > > }; > > > > + hsusb: usb@e6590000 { > > + compatible = "renesas,usbhs-r8a77990", > > + "renesas,rcar-gen3-usbhs"; > > + reg = <0 0xe6590000 0 0x100>; > > is it not 0x200? > > Renesas_usbhs driver("drivers/usb/renesas_usbhs/common.c ") maps the address > up to 0x100 using "devm_ioremap_resource" > function > > where as the "drivers/usb/renesas_usbhs/rcar3" access addresses beyond > 0x100 (for eg:- 0x102,0x180,0x184,0x188) using > iowrite32/16 calls. > > This issue is present in other R-Car Gen3 variant as well(for eg:- R-Car > H3/M3-W,..... etc).
Thank you very much for your report! You're collect. So, I'll submit a patch to resolve it for all R-Car Gen3 SoCs. Best regards, Yoshihiro Shimoda
