From: Jean Delvare <khali@linux-fr•org>
To: "Jon Smirl" <jonsmirl@gmail•com>
Cc: Linuxppc-dev@ozlabs•org, Alan Clucas <alanc@pipstechnology•co.uk>,
Detlev Zundel <dzu@denx•de>,
lm-sensors@lm-sensors•org
Subject: Re: [PATCH] Support for DS75 thermal sensor
Date: Wed, 16 Jul 2008 16:29:42 +0200 [thread overview]
Message-ID: <20080716162942.6fcb526d@hyperion.delvare> (raw)
In-Reply-To: <9e4733910807160718y580292abi5f44a05f466fd358@mail.gmail.com>
On Wed, 16 Jul 2008 10:18:26 -0400, Jon Smirl wrote:
> On 7/16/08, Grant Likely <grant.likely@secretlab•ca> wrote:
> > On Wed, Jul 16, 2008 at 12:10:59PM +0200, Jean Delvare wrote:
> > > On Wed, 16 Jul 2008 11:50:15 +0200, Wolfgang Grandegger wrote:
> > > > Jean Delvare wrote:
> > > >
> >
> > > > Yep, as probing might not be acceptable in some cases, I makes sense to
> > > > add a property to suppress probing:
> > >
> > > It'd rather make no-probing the default if possible. My understanding
> > > is that all systems using i2c-mpc should have proper platform data.
> >
> >
> > Total ACK. From my perspective, probing should be off by default because the
> > typical use case in powerpc land is to trust data in the device tree. Add the
> > property to turn on probing, not to turn it off. Also, you'll need to
> > document the semantics of such a property. ie. what exactly does it
> > mean when the probing property is present and the spi bus node has child
> > nodes?
>
> I've found this thread now. Why can't we totally remove probing from
> i2c-mpc? These are embedded systems, not open boxes like a PC. If a
> i2c client hasn't been converted to the new model yet, convert it
> before deploying with the new i2c-mpc driver. It's not very hard to
> convert the client drivers.
I tend to agree. And the number of unconverted drivers is getting very
low these days. Only 2 RTC drivers are left, and by the end of the day,
almost all hwmon drivers will be converted as well.
--
Jean Delvare
next prev parent reply other threads:[~2008-07-16 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <487331DC.2020601@grandegger.com>
[not found] ` <20080708115319.111226e6@hyperion.delvare>
[not found] ` <4873670C.6080204@grandegger.com>
[not found] ` <20080708152935.7457bc90@hyperion.delvare>
[not found] ` <487754DA.1060207@grandegger.com>
[not found] ` <20080711145613.14380360@hyperion.delvare>
2008-07-16 9:12 ` [lm-sensors] [PATCH] Support for DS75 thermal sensor Wolfgang Grandegger
2008-07-16 9:33 ` Jean Delvare
2008-07-16 9:50 ` Wolfgang Grandegger
2008-07-16 10:10 ` Jean Delvare
2008-07-16 10:23 ` Wolfgang Grandegger
2008-07-16 14:08 ` Grant Likely
2008-07-16 14:18 ` Jon Smirl
2008-07-16 14:29 ` Jean Delvare [this message]
2008-07-17 7:31 ` Wolfgang Grandegger
2008-07-17 7:33 ` Grant Likely
2008-07-17 10:39 ` Wolfgang Grandegger
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=20080716162942.6fcb526d@hyperion.delvare \
--to=khali@linux-fr$(echo .)org \
--cc=Linuxppc-dev@ozlabs$(echo .)org \
--cc=alanc@pipstechnology$(echo .)co.uk \
--cc=dzu@denx$(echo .)de \
--cc=jonsmirl@gmail$(echo .)com \
--cc=lm-sensors@lm-sensors$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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