[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170608084619.GH3730@atomide.com>
Date: Thu, 8 Jun 2017 01:46:20 -0700
From: Tony Lindgren <tony@...mide.com>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: Kishon Vijay Abraham I <kishon@...com>,
Rob Herring <robh+dt@...nel.org>, Sekhar Nori <nsekhar@...com>,
Russell King <linux@...linux.org.uk>,
linux-omap <linux-omap@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>
Subject: Re: [PATCH v2 0/8] omap*: Fixes/Cleanups for MMC devicetree node
* Ulf Hansson <ulf.hansson@...aro.org> [170608 00:24]:
> If it helps, I can host a branch with the updates on the omap_hsmmc
> driver, such it can be pulled in from arm soc?
Great that works for me. Let's just make sure git bisect
keeps working.
> I guess you need that as, the DT changes relies on the new vqmmc
> binding. Or you thing it doesn't matter, because for the current
> changes that regulator is always an always on regulator?
Or maybe we can just add the new regulator, then do a
follow-up series to remove the old ones?
Regards,
Tony
Powered by blists - more mailing lists