public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rhyland Klein <rklein@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	"devicetree-discuss@lists.ozlabs.org" 
	<devicetree-discuss@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Rob Herring <rob.herring@calxeda.com>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 1/4] regulator: tps65910: update type for regmap
Date: Wed, 18 Apr 2012 13:19:31 -0700	[thread overview]
Message-ID: <1334780371.32315.66.camel@rklein-linux> (raw)
In-Reply-To: <1334779402.32315.63.camel@rklein-linux>

On Wed, 2012-04-18 at 13:03 -0700, Rhyland Klein wrote:
> On Wed, 2012-04-18 at 02:25 -0700, Mark Brown wrote:
> > * PGP Signed by an unknown key
> > 
> > On Tue, Apr 17, 2012 at 06:00:26PM -0700, Rhyland Klein wrote:
> > > When accessing the regmap via the read/write functions, we need to use a
> > > unsigned int * instead of a u8 * otherwise corruption will occur.
> > > 
> > > Signed-off-by: Rhyland Klein <rklein@nvidia.com>
> > 
> > >  static inline int tps65910_read(struct tps65910_reg *pmic, u8 reg)
> > >  {
> > > -	u8 val;
> > > +	unsigned int val;
> > >  	int err;
> > >  
> > >  	err = pmic->mfd->read(pmic->mfd, reg, 1, &val);
> > 
> > Ugh, this interface is just broken all round - there's absolutely no
> > type safety here and all users of these functions will be broken (a
> > similar issue applies on write).  It's much better to fix this for 3.4
> > by converting the core code to use regmap_raw_ functions which take
> > native formatted data for the device like the function driver API
> > actually expects.
> 
> Which interface are you saying is broken? The regmap interface or the
> one internal to the tps65910 code? 
> 
> > 
> > Looking at the MFD code the fix for 3.5 should at the very least involve
> > making the functions take typed pointers, though given the way they're
> > implemented right now with direct references in the subdevices I'd also
> > consider just having the subdevices uses regmap directly as the wrappers
> > are just adding an opportunity for error (the bit operations could be
> > converted into static inlines in the header too).
> > 
> 
> So to be clear... Your recommendation is to change the tps65910 code to
> remove the common read/write callbacks and to use regmap directly in
> each component, and then when using regmap, do use the regmap raw
> functions instead of the bulkread/write?

Looking at the code, I would think it makes more sense use regmap_read
which enforces types since the tps65910 code only ever seems to use
regmap to access a single register at a time. Do you agree?

-rhyland
--- 
nvpublic



  reply	other threads:[~2012-04-18 20:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18  1:00 [PATCH 0/4] Update TPS65910 to boot using devicetree Rhyland Klein
2012-04-18  1:00 ` [PATCH 1/4] regulator: tps65910: update type for regmap Rhyland Klein
2012-04-18  9:25   ` Mark Brown
2012-04-18 20:03     ` Rhyland Klein
2012-04-18 20:19       ` Rhyland Klein [this message]
2012-04-19 12:54         ` Mark Brown
2012-04-18  1:00 ` [PATCH 2/4] regulator: tps65910: Add device tree bindings Rhyland Klein
2012-04-18  8:35   ` Mark Brown
2012-04-18  1:00 ` [PATCH 3/4] mfd: tps65910: Add device-tree support Rhyland Klein
2012-04-18  9:01   ` Mark Brown
2012-04-18 19:35     ` Rhyland Klein
2012-04-19 12:50       ` Mark Brown
2012-04-19 15:35         ` Stephen Warren
2012-04-19 16:34           ` Mark Brown
2012-04-18  1:00 ` [PATCH 4/4] ARM: Tegra: Add support for TPS65910 PMIC Rhyland Klein

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=1334780371.32315.66.camel@rklein-linux \
    --to=rklein@nvidia.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=rob.herring@calxeda.com \
    --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