From: Thierry Reding <thierry.reding@avionic-design.de>
To: Jean Delvare <khali@linux-fr.org>
Cc: Guenter Roeck <guenter.roeck@ericsson.com>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hwmon: lm63: Add support for the NatSemi LM96163.
Date: Tue, 8 Nov 2011 10:05:34 +0100 [thread overview]
Message-ID: <20111108090534.GE27841@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <20111108095925.0d99aea5@endymion.delvare>
[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]
* Jean Delvare wrote:
> Hi Thierry,
>
> On Tue, 8 Nov 2011 08:30:52 +0100, Thierry Reding wrote:
> > * Guenter Roeck wrote:
> > > Hi,
> > >
> > > On Mon, 2011-11-07 at 05:20 -0500, Thierry Reding wrote:
> > > > Signed-off-by: Thierry Reding <thierry.reding@avionic-design.de>
> > > > ---
> > > > drivers/hwmon/lm63.c | 2 +-
> > > > 1 files changed, 1 insertions(+), 1 deletions(-)
> > > >
> > > > diff --git a/drivers/hwmon/lm63.c b/drivers/hwmon/lm63.c
> > > > index 508cb29..94e373c 100644
> > > > --- a/drivers/hwmon/lm63.c
> > > > +++ b/drivers/hwmon/lm63.c
> > > > @@ -483,7 +483,7 @@ static int lm63_detect(struct i2c_client *new_client,
> > > > return -ENODEV;
> > > > }
> > > >
> > > > - if (chip_id == 0x41 && address == 0x4c)
> > > > + if ((chip_id == 0x41 || chip_id == 0x49) && address == 0x4c)
> > > > strlcpy(info->type, "lm63", I2C_NAME_SIZE);
> > > > else if (chip_id == 0x51 && (address == 0x18 || address == 0x4e))
> > > > strlcpy(info->type, "lm64", I2C_NAME_SIZE);
> > >
> > > Minor - the new chip should be mentioned in drivers/hwmon/Kconfig and in
> > > Documentation/hwmon/lm63.
> >
> > I don't see how to list this variant meaningfully in the documentation.
> > Since, as you mention, no functionality specific to the LM96163 is added,
> > this patch really only adds support for one more lm63 chip.
>
> The new chip name should at least be listed in
> Documentation/hwmon/lm63, drivers/hwmon/Kconfig.
Okay.
> > > My main concern is that LM96163 supports a high resolution PWM mode.
> > > Since that mode is much more convenient than the LM63-compatible mode, I
> > > think it is likely to be enabled in designs using LM96163, and it should
> > > be supported by the driver if we add support for LM96163.
> >
> > Unfortunately our design doesn't use the PWM at all. It is only used for
> > temperature measurements, so I'm not able to test any of the PWM code.
>
> You still need to ensure that nothing bad will happen if users load the
> lm63 driver with a LM96163 chip (if nothing else, by disabling the
> unimplemented/untested feature.)
Okay. I'll make sure to mention that in the documentation as well.
Thanks,
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-11-08 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 10:20 [PATCH] hwmon: lm63: Add support for the NatSemi LM96163 Thierry Reding
2011-11-07 16:49 ` Guenter Roeck
2011-11-08 7:30 ` Thierry Reding
2011-11-08 8:59 ` Jean Delvare
2011-11-08 9:05 ` Thierry Reding [this message]
2011-11-09 17:42 ` Guenter Roeck
2011-11-08 9:15 ` Jean Delvare
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=20111108090534.GE27841@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=guenter.roeck@ericsson.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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