From: Stephen Warren <swarren@nvidia.com>
To: "sameo@linux.intel.com" <sameo@linux.intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"achew@nvidai.com" <achew@nvidai.com>,
"olofj@chromium.org" <olofj@chromium.org>
Subject: RE: [PATCH] mfd: tps6586x: Remove device ID check
Date: Thu, 16 Dec 2010 12:35:17 -0800 [thread overview]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF030FD78609@HQMAIL01.nvidia.com> (raw)
In-Reply-To: <1291915811-17227-1-git-send-email-swarren@nvidia.com>
> From: Stephen Warren [mailto:swarren@nvidia.com]
> Sent: Thursday, December 09, 2010 10:30 AM
>
> ... and convert it to a dev_info print at probe time.
Samuel,
Sorry to ping you, but does this updated patch look OK and address your
concerns? Thanks.
> There are many variants of this chip with different values of VERSIONCRC.
> The set of values is large, and not useful to enumerate. All are SW
> compatible. The difference lies in default settings of the various power
> rails, and other similar differences. The driver, or clients of the
> driver, shouldn't be affected by this, since all rails should be
> programmed into the desired state in all cases for correct operation.
>
> Derived-from-code-by: Andrew Chew <achew@nvidia.com>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> drivers/mfd/tps6586x.c | 8 +-------
> 1 files changed, 1 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/mfd/tps6586x.c b/drivers/mfd/tps6586x.c
> index b4931ab..3575739 100644
> --- a/drivers/mfd/tps6586x.c
> +++ b/drivers/mfd/tps6586x.c
> @@ -46,8 +46,6 @@
>
> /* device id */
> #define TPS6586X_VERSIONCRC 0xcd
> -#define TPS658621A_VERSIONCRC 0x15
> -#define TPS658621C_VERSIONCRC 0x2c
>
> struct tps6586x_irq_data {
> u8 mask_reg;
> @@ -498,11 +496,7 @@ static int __devinit tps6586x_i2c_probe(struct i2c_client *client,
> return -EIO;
> }
>
> - if ((ret != TPS658621A_VERSIONCRC) &&
> - (ret != TPS658621C_VERSIONCRC)) {
> - dev_err(&client->dev, "Unsupported chip ID: %x\n", ret);
> - return -ENODEV;
> - }
> + dev_info(&client->dev, "VERSIONCRC is %02x\n", ret);
>
> tps6586x = kzalloc(sizeof(struct tps6586x), GFP_KERNEL);
> if (tps6586x == NULL)
> --
> 1.7.0.4
--
nvpublic
next prev parent reply other threads:[~2010-12-16 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 18:33 Stephen Warren
2010-12-02 21:02 ` Andrew Chew
2010-12-09 13:58 ` Samuel Ortiz
2010-12-09 17:30 ` Stephen Warren
2010-12-16 20:35 ` Stephen Warren [this message]
2010-12-19 22:43 ` Samuel Ortiz
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=74CDBE0F657A3D45AFBB94109FB122FF030FD78609@HQMAIL01.nvidia.com \
--to=swarren@nvidia.com \
--cc=achew@nvidai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olofj@chromium.org \
--cc=sameo@linux.intel.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
all inboxes | Powered by JetHome®