On Mon, Feb 22, 2016 at 09:47:34AM +0100, Wolfram Sang wrote: > On Mon, Feb 15, 2016 at 01:57:47PM +0100, Wolfram Sang wrote: > > This series provides the necessary preparation to use Lager for testing the > > above mentioned features. After this, the rest is done at runtime as > > described > > in the upstream documentation. > > > > This series depends on the i2c-demux-pinctrl driver which is in linux-next > > already. Because IIC0/I2C0 is unpopulated and even so, IIC0 is used as > > default > > like before, chances of a regression are extremly unlikely. The only > > regression > > I can think of is someone using: > > a) IIC0 with an external board > > b) the Lager DTS from upstream unmodified > > c) a private .config and forgot to activate the i2c-demux-pinctrl driver > > > > We could point this person to the working shmobile_defconfig, though. > > However, > > I'd think that someone using IIC0 externally will also have a private Lager > > DTS > > and in that case will be made aware by the merge conflict. > > > > Another minor question for me is: Do we need to update multiv7_defconfig, > > too. > > My feeling is no, so I left it out, but may be convinced otherwise.
My feeling is yes for consistency. Are you concerned about bloat in multiv7_defconfig? > > Magnus: I hope this is what you had in mind for the reference platform idea. > > > > Kind regards, > > > > Wolfram > > Can we have this in 4.6? Sure, I have tentatively queued this up for v4.6.
