From: Ashish Jangam <ashish.jangam@kpitcummins.com>
To: <guenter.roeck@ericsson.com>
Cc: <randy.dunlap@oracle.com>, <linaro-dev@lists.linaro.org>,
<dchen@diasemi.com>, <linux-kernel@vger.kernel.org>,
<lm-sensors@lm-sensors.org>
Subject: Re: [PATCH] HWMON: DA9052/53 hwmon driver v2
Date: Tue, 21 Feb 2012 17:13:48 +0530 [thread overview]
Message-ID: <1329824628.30549.187.camel@dhruva> (raw)
In-Reply-To: <C3AE124F08223B42BC95AEB82F0F6CED2B996CD9@KCHJEXMB01.kpit.com>
On Tue, 2012-02-21 at 16:48 +0530, Ashish Jangam wrote:
> On Fri, 2012-02-10 at 07:58 -0500, Ashish Jangam wrote:
> > The DA9052 PMIC provides an Analogue to Digital Converter with 10 bits
> > resolution and 10 channels.
> >
> > + * Dialog Semiconductors DA9052-BC and DA9053-AA/Bx PMICs
> > + Prefix: 'da9052'
> > + Datasheet: Kindly visit www.dialog-semiconductor.com/product_table.php
> > + and request for the official datasheet.
> > +
> Not really. From practical experience, the datasheet is not available
> except for Dialog Semiconductor customers - not even for me to review
> the driver (and that appears to be independent of my employer's
> relationship with Dialog Semiconductor). I think this should read "not
> publicly available". It is a bit misleading to suggest that it would be
> available if that is not the case.
Agreed.
>
> > +static const char * const input_names[] = {
> > + [DA9052_ADC_VDDOUT] = "VDDOUT",
> > + [DA9052_ADC_ICH] = "CHARGING CURRENT",
> > + [DA9052_ADC_TBAT] = "BATTERY TEMP",
> > + [DA9052_ADC_VBAT] = "BATTERY VOLTAGE",
> > + [DA9052_ADC_IN4] = "ADC IN4",
> > + [DA9052_ADC_IN5] = "ADC IN5",
> > + [DA9052_ADC_IN6] = "ADC IN6",
> > + [DA9052_ADC_TJUNC] = "BATTERY JUNCTION TEMP",
> > + [DA9052_ADC_VBBAT] = "BACK-UP BATTERY VOLTAGE",
> > +};
> > +
> Where are those defines, or, in other words, which repository/branch is
> your patch based on ? I don't see it in the current mainline kernel.
The incremental ADC patch to the da9052 mfd core takes care of all such
issues. However that patch is still under review...hoping to get it thru
soon.
next parent reply other threads:[~2012-02-21 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C3AE124F08223B42BC95AEB82F0F6CED2B996CD9@KCHJEXMB01.kpit.com>
2012-02-21 11:43 ` Ashish Jangam [this message]
2012-02-10 12:58 [PATCH] HWMON: DA9052/53 hwmon driver v2 Ashish Jangam
2012-02-10 14:50 ` Guenter Roeck
2012-02-20 21:15 ` Guenter Roeck
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=1329824628.30549.187.camel@dhruva \
--to=ashish.jangam@kpitcummins.com \
--cc=dchen@diasemi.com \
--cc=guenter.roeck@ericsson.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=randy.dunlap@oracle.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