linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stefan@agner.ch (Stefan Agner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] mfd: tps6586x: add version detection
Date: Wed, 27 Nov 2013 22:44:52 +0100	[thread overview]
Message-ID: <ddd65b4d645cb99c3288960ea2dbe7a3@agner.ch> (raw)
In-Reply-To: <529624CA.6030604@wwwdotorg.org>

Am 2013-11-27 17:58, schrieb Stephen Warren:
<snip>
>> +	tps6586x = devm_kzalloc(&client->dev, sizeof(*tps6586x), GFP_KERNEL);
>> +	if (tps6586x == NULL) {
>> +		dev_err(&client->dev, "memory for tps6586x alloc failed\n");
>> +		return -ENOMEM;
>> +	}
> 
>> +	tps6586x->version = (enum tps6586x_version)ret;
> 
> Why not make the version variable an integer of some kind. Then, the
> cast wouldn't be required. The values like TPS658621A can be #defines or
> const u32.
> 
Yep this would work too. Whatever is preferred, maybe define would be
more consistent since SLEW_RATE are defines too (both, the VERSIONCRC
and SLEW_RATE values are possible content of registers).

>> +	switch (ret) {
> 
> That should switch on tps6586x->version since that's been assigned;
> it'll make the purpose a bit clearer.
> 
>> +	default:
>> +		name = "TPS6586X";
>> +		break;
>>  	}
> 
> I hope the rest of the code deals with unknown values of
> tps6586x->version OK.
>
Well, the tps6586x->version is not completly unknown, its something
valid which is returned by i2c_smbus_read_byte_data. According to the
data sheet this should be a 8-Bit value.

However, the patch should handle every version, since I tried to make
the change backward compatible: The driver now and then supports every
device version, just the default voltage table are applied if there are
no specific tables available.

  reply	other threads:[~2013-11-27 21:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 23:45 [PATCH 0/3] regulator: tps6586x: add version detection and voltage tables Stefan Agner
2013-11-26 23:45 ` [PATCH 1/3] mfd: tps6586x: add version detection Stefan Agner
2013-11-27 13:09   ` Lee Jones
2013-11-27 13:11     ` Lee Jones
2013-11-27 13:49     ` Stefan Agner
2013-11-27 13:55       ` Lee Jones
     [not found]         ` <cfb203a896eda67c106794d89e668d56@agner.ch>
     [not found]           ` <20131127143429.GN3296@lee--X1>
2013-11-27 14:36             ` Lee Jones
2013-11-27 15:26               ` Stefan Agner
2013-11-27 15:30                 ` Lee Jones
2013-11-27 15:52                   ` Stefan Agner
2013-11-27 16:14                     ` Lee Jones
2013-11-27 16:58   ` Stephen Warren
2013-11-27 21:44     ` Stefan Agner [this message]
2013-11-26 23:45 ` [PATCH 2/3] regulator: tps6586x: add voltage table for tps658643 Stefan Agner
2013-11-27 17:09   ` Stephen Warren
2013-11-27 21:56     ` Stefan Agner
2013-11-28  8:30       ` Thierry Reding
2013-11-26 23:45 ` [PATCH 3/3] ARM: tegra: set SM2 voltage correct Stefan Agner
2013-11-27  9:59   ` Lucas Stach
2013-11-27 11:05     ` Stefan Agner
2013-11-27 11:06       ` Lucas Stach
2013-11-27 17:13   ` Stephen Warren
2013-11-27 22:03     ` Stefan Agner
2013-11-28  9:49     ` Lucas Stach
2013-11-30 16:24       ` Stefan Agner
2013-11-28  8:13 ` [PATCH 0/3] regulator: tps6586x: add version detection and voltage tables Thierry Reding
2013-11-29  8:20   ` Kai Poggensee

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=ddd65b4d645cb99c3288960ea2dbe7a3@agner.ch \
    --to=stefan@agner.ch \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).