The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Vincent Palatin <vpalatin@chromium.org>,
	lm-sensors@lm-sensors.org,
	Grant Likely <grant.likely@secretlab.ca>,
	Rob Herring <rob.herring@calxeda.com>,
	linux-kernel@vger.kernel.org, Olof Johansson <olofj@chromium.org>,
	Sameer Nanda <snanda@chromium.org>
Subject: Re: [PATCH] hwmon: (lm90) Add device tree support
Date: Fri, 1 Feb 2013 22:57:49 +0100	[thread overview]
Message-ID: <20130201225749.4b17d42d@endymion.delvare> (raw)
In-Reply-To: <20130201213640.GA1606@roeck-us.net>

On Fri, 1 Feb 2013 13:36:40 -0800, Guenter Roeck wrote:
> On Fri, Feb 01, 2013 at 01:18:22PM -0800, Vincent Palatin wrote:
> > When the kernel has device tree support, we avoid doing the auto-detection
> > as probing the busses might mess-up sensitive I2C devices or trigger long
> > timeouts on non-functional busses.
> (...)
> As for the detect function, I am not entirely sure if we want or should get
> rid of it just because OF is configured. That may have unintended side effects.
> Either case, I would argue that if we do want to do that, it should be done
> for _all_ I2C devices and not just for the lm90 driver. In other words, it
> should be done in the I2C subsystem, maybe with a separate configuration option.

I can't think of any reason for doing that. Detection only happens on
I2C buses which request it (by setting i2c_adapter.class.) I2C system
bus drivers for OF-based platforms would simply not set any class flag,
so detection won't be triggered on them.

-- 
Jean Delvare

      reply	other threads:[~2013-02-01 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 21:18 [PATCH] hwmon: (lm90) Add device tree support Vincent Palatin
2013-02-01 21:36 ` Guenter Roeck
2013-02-01 21:57   ` Jean Delvare [this message]

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=20130201225749.4b17d42d@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lm-sensors@lm-sensors.org \
    --cc=olofj@chromium.org \
    --cc=rob.herring@calxeda.com \
    --cc=snanda@chromium.org \
    --cc=vpalatin@chromium.org \
    /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