[PATCH v2] ARM: dts: aspeed: zaius add reg field to pca9541a i2c mux

[Emily Shaffer]

Xo, with those backports the LM5066I works out of the box - no code change
needed from me.

Joel, can we pull in the patchset Xo linked (
https://lkml.org/lkml/2016/8/15/569)?  I didn't have any conflicts locally
with this, should be straightforward.

Thanks,
Emily

On Thu, Mar 2, 2017 at 10:57 AM Rick Altherr <raltherr at google.com> wrote:

> Not that I've found.  Best I've been able to work out is grepping the
> build log
> (tmp/work/zaius-openbmc-linux-gnueabi/linux-obmc/4.7+git999-r0/temp/log.do_compile)
> for "warning".
>
> On Thu, Mar 2, 2017 at 10:52 AM, Emily Shaffer <emilyshaffer at google.com>
> wrote:
> > I'm going to give a try with those patches backported, no luck getting
> rid
> > of the warning.
> >
> > Incidentally, is there a way to turn on warnings as errors with bitbake?
> I
> > was unaware of those warnings until Joel pointed them out.
> >
> > On Thu, Mar 2, 2017 at 9:58 AM Xo Wang <xow at google.com> wrote:
> >>
> >> It looks like this issue is fixed in v4.9:
> >> https://lkml.org/lkml/2016/8/15/569
> >>
> >> The cover letter to that patchset also mentions adding an unused "reg"
> >> property as a workaround. I had probably copied and pasted the pca9541
> >> bindings without "reg" to the Zaius dts without reading the rest of
> >> the notes. Oops.
> >>
> >> Should we backport that patchset and/or wait for the next OpenBMC kernel
> >> rebase?
> >>
> >> Emily: can you test whether the "reg" property is still necessary if
> >> you backport those patches?
> >>
> >> cheers
> >> xo
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170303/baa58535/attachment.html>