All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@aj.id.au>
To: Joel Stanley <joel@jms.id.au>
Cc: "YangBrianC.W 楊嘉偉 TAO" <yang.brianc.w@inventec.com>,
	"Chen.KenYY 陳永營 TAO" <Chen.KenYY@inventec.com>,
	"OpenBMC Maillist" <openbmc@lists.ozlabs.org>,
	"Lei YU" <mine260309@gmail.com>
Subject: Re: FW: [PATCH linux dev-4.13 v1] ARM: dts: aspeed: Add Inventec Lanyang BMC
Date: Thu, 19 Apr 2018 11:06:05 +0930	[thread overview]
Message-ID: <1524101765.2367494.1343094608.58E4CC87@webmail.messagingengine.com> (raw)
In-Reply-To: <CACPK8XeRZ_NbaduF-jbPoSA+-HO6O4Zoy3M1-geqkhkyohq6ag@mail.gmail.com>

On Thu, 19 Apr 2018, at 10:27, Joel Stanley wrote:
> On 17 April 2018 at 11:35, Andrew Jeffery <andrew@aj.id.au> wrote:
> 
> >> >> +&i2c11 {
> >> >> +     status = "okay";
> >> >> +};
> >> >
> >> > Do we need to enable all of the above i2c buses? By comparison, Zaius enables i2c0, i2c1, i2c4, i2c7 and i2c8.
> >>
> >> Thank you for your review.
> >>
> >> We need to enable all of the above i2c buses because we want to verify
> >> the i2c bus is fine by i2ctool.
> >>
> >> Because we use the above i2c buses on Lanyang platform.
> >
> > Okay, it's still not clear to me. Are there devices on all the buses? If so, do any have bindings that we could use to describe them here? It looks odd enabling all the buses but not "using" any of them.
> >
> > If you're just enabling them to test the bus with i2ctool then I feel that we might be better with that staying as a local change for your testing, rather than merging this as is. Joel?
> 
> If they exist on in the design, then enabling them is fine.
> 
> The distinction I've gone with is it doesn't make sense to have them
> enabled when the i2c pads on the SoC are not broken out, or if they're
> only connected to ground, so there's no way of them ever "working".
> 
> I'm happy with the dt as is it is. If you're happy then I will merge.

Yeah I don't feel strongly about it, just it looked odd.

Acked-by: Andrew Jeffery <andrew@aj.id.au>

  reply	other threads:[~2018-04-19  1:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11  7:42 [PATCH linux dev-4.13 v1] ARM: dts: aspeed: Add Inventec Lanyang BMC Brian Yang
2018-04-11  9:29 ` Joel Stanley
2018-04-11 11:18   ` YangBrianC.W 楊嘉偉 TAO
2018-04-13  1:57 ` Andrew Jeffery
     [not found]   ` <39E6480C5A587146BAA4D885C7BCF7EEC6B7921E@IEC1-EX2010-MX4.iec.inventec>
2018-04-16 11:09     ` FW: " YangBrianC.W 楊嘉偉 TAO
2018-04-17  2:05       ` Andrew Jeffery
2018-04-17  3:24         ` YangBrianC.W 楊嘉偉 TAO
2018-04-19  0:57         ` Joel Stanley
2018-04-19  1:36           ` Andrew Jeffery [this message]
2018-04-26  2:53             ` Joel Stanley

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=1524101765.2367494.1343094608.58E4CC87@webmail.messagingengine.com \
    --to=andrew@aj.id.au \
    --cc=Chen.KenYY@inventec.com \
    --cc=joel@jms.id.au \
    --cc=mine260309@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=yang.brianc.w@inventec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.