[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2923003.R6AlEiEkj2@wuerfel>
Date: Fri, 20 May 2016 16:15:27 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Mark Brown <broonie@...nel.org>
Cc: Andy Gross <andy.gross@...aro.org>,
Felipe Balbi <balbi@...nel.org>,
David Brown <david.brown@...aro.org>,
Peter Chen <Peter.Chen@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Stern <stern@...land.harvard.edu>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
linux-soc@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [RFC 4/8] usb: phy: move TCSR driver into new file
On Friday 20 May 2016 13:44:14 Mark Brown wrote:
> On Fri, May 20, 2016 at 02:24:14PM +0200, Arnd Bergmann wrote:
> > On Thursday 19 May 2016 14:08:43 Andy Gross wrote:
>
> > > I'd rather do something like what we did for the GSBI. It needed to
> > > change some phy related bits in the TCSR as well. We defined the TCSR
> > > as a syscon, with binding documentation under mfd. If we add a syscon
> > > entry and use it if it is present, we can deal with that pretty
> > > easily. The offsets change for each soc, and this would also fix that
> > > issue because we can change offset based on tcsr compat.
>
> > Works for me, but be aware that this will break the server chips,
> > as ACPI has no support for regmap devices.
>
> Just to be clear there's nothing precluding the use of regmap on ACPI
> devices, it's syscon it doesn't have anything for.
>
Yes, that's what I meant.
Arnd
Powered by blists - more mailing lists