linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: Joel Stanley <joel@jms.id.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	devicetree <devicetree@vger.kernel.org>,
	Devicetree Compiler <devicetree-compiler@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Manikandan Elumalai <manikandan.hcl.ers.epl@gmail.com>,
	Andrew Jeffery <andrew@aj.id.au>, Vijay Khemka <vkhemka@fb.com>
Subject: Re: linux-next: build warning after merge of the aspeed tree
Date: Mon, 11 May 2020 10:19:15 -0500	[thread overview]
Message-ID: <CAL_JsqJWXH4JMZgRQa9r_aPLW6Muz6BRtf_NmeqJv21Aefji1A@mail.gmail.com> (raw)
In-Reply-To: <CACPK8XcUydETZvJEkWPvLnLXatAg3D-MfA1yeDzE0epc-hisJQ@mail.gmail.com>

On Fri, May 8, 2020 at 1:40 AM Joel Stanley <joel@jms.id.au> wrote:
>
> On Wed, 6 May 2020 at 23:13, Joel Stanley <joel@jms.id.au> wrote:
> >
> > Hi Rob,
> >
> > On Wed, 6 May 2020 at 23:10, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > Hi all,
> > >
> > > After merging the aspeed tree, today's linux-next build (arm
> > > multi_v7_defconfig) produced this warning:
> >
> > Thanks Stephen.
> >
> > > arch/arm/boot/dts/aspeed-bmc-facebook-yosemitev2.dts:126.11-130.4: Warning (i2c_bus_reg): /ahb/apb/bus@1e78a000/i2c-bus@80/ipmb1@10: I2C bus unit address format error, expected "40000010"
> > > arch/arm/boot/dts/aspeed-bmc-facebook-yosemitev2.dts:128.3-30: Warning (i2c_bus_reg): /ahb/apb/bus@1e78a000/i2c-bus@80/ipmb1@10:reg: I2C address must be less than 10-bits, got "0x40000010"
> > > arch/arm/boot/dts/aspeed-bmc-facebook-yosemitev2.dts:137.11-141.4: Warning (i2c_bus_reg): /ahb/apb/bus@1e78a000/i2c-bus@100/ipmb3@10: I2C bus unit address format error, expected "40000010"
> > > arch/arm/boot/dts/aspeed-bmc-facebook-yosemitev2.dts:139.3-30: Warning (i2c_bus_reg): /ahb/apb/bus@1e78a000/i2c-bus@100/ipmb3@10:reg: I2C address must be less than 10-bits, got "0x40000010"
> > > arch/arm/boot/dts/aspeed-bmc-facebook-yosemitev2.dts:148.11-152.4: Warning (i2c_bus_reg): /ahb/apb/bus@1e78a000/i2c-bus@180/ipmb5@10: I2C bus unit address format error, expected "40000010"
> > > arch/arm/boot/dts/aspeed-bmc-facebook-yosemitev2.dts:150.3-30: Warning (i2c_bus_reg): /ahb/apb/bus@1e78a000/i2c-bus@180/ipmb5@10:reg: I2C address must be less than 10-bits, got "0x40000010"
> > > arch/arm/boot/dts/aspeed-bmc-facebook-yosemitev2.dts:159.11-163.4: Warning (i2c_bus_reg): /ahb/apb/bus@1e78a000/i2c-bus@300/ipmb7@10: I2C bus unit address format error, expected "40000010"
> > > arch/arm/boot/dts/aspeed-bmc-facebook-yosemitev2.dts:161.3-30: Warning (i2c_bus_reg): /ahb/apb/bus@1e78a000/i2c-bus@300/ipmb7@10:reg: I2C address must be less than 10-bits, got "0x40000010"
> >
> > These are IPMB nodes with the SLAVE_ADDRESS bit set:
> >
> > +&i2c5 {
> > +       //Host3 IPMB bus
> > +       status = "okay";
> > +       multi-master;
> > +       ipmb5@10 {
> > +               compatible = "ipmb-dev";
> > +               reg = <(0x10 | I2C_OWN_SLAVE_ADDRESS)>;
> > +               i2c-protocol;
> > +       };
> >
> > This is a correct entry, so dtc should not warn about it.
>
> I sent a patch for dtc here:
> https://lore.kernel.org/lkml/20200508063904.60162-1-joel@jms.id.au/

Patches for dtc need to be against upstream dtc. There's already a
similar patch posted for it which I commented on and never saw a
respin.

Rob

  reply	other threads:[~2020-05-11 15:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 23:10 linux-next: build warning after merge of the aspeed tree Stephen Rothwell
2020-05-06 23:13 ` Joel Stanley
2020-05-08  6:40   ` Joel Stanley
2020-05-11 15:19     ` Rob Herring [this message]
2020-05-20  7:56       ` Joel Stanley
2020-05-22  0:16         ` Stephen Rothwell
2020-05-22  8:15           ` Arnd Bergmann
2020-05-28  6:09             ` Joel Stanley
2020-05-28  7:21               ` Joel Stanley
2023-07-10 23:51 Stephen Rothwell
2023-07-20  0:40 ` Stephen Rothwell
2023-08-02  0:06   ` Stephen Rothwell
2023-08-09  7:57     ` Joel Stanley
2023-08-09  8:23       ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAL_JsqJWXH4JMZgRQa9r_aPLW6Muz6BRtf_NmeqJv21Aefji1A@mail.gmail.com \
    --to=robh+dt@kernel.org \
    --cc=andrew@aj.id.au \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=manikandan.hcl.ers.epl@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=vkhemka@fb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).