linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <matthias.list@kaehlcke.net>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: "broonie@opensource.wolfsonmicro.com"
	<broonie@opensource.wolfsonmicro.com>,
	"sameo@linux.intel.com" <sameo@linux.intel.com>,
	"dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
	"rdunlap@xenotime.net" <rdunlap@xenotime.net>,
	"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] mfd/regulator: tps65217: Move regulator plat data handling to regulator
Date: Mon, 13 Aug 2012 22:02:50 +0200	[thread overview]
Message-ID: <20120813200250.GA3822@darwin> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA11ABF@DBDE01.ent.ti.com>

Hi AnilKumar,

El Mon, Aug 13, 2012 at 01:35:55PM +0000 AnilKumar, Chimata ha dit:

> > also the tps65217_board structure should be renamed to something like
> > tps65217_regulators, now that it is specific to the regulator
> 
> Not required because tps65217_board might contain platform data for WLED/
> Battery charger driver if require. So the struct was named as tps65217_board

the patch moves the allocation of the structure to the regulator
driver, so either it should be a subdevice specific structure or a
chip specific one which is allocated in the mfd driver. otherwise the
regulator driver will allocate memory which is never used when struct
tps65217_board is extended for other subdevices. and the same would
happen in the other subdevice drivers if they choose to allocate their
own struct tps65217_board instead of a sub-structure with just the
fields needed by the specific driver

regards

-- 
Matthias Kaehlcke
Embedded Linux Developer
Amsterdam

    Yo soy como soy y tú eres como eres, construyamos un mundo donde yo
    pueda ser sin dejar de ser yo, donde tú puedas ser sin dejar de ser
    tú, y donde ni yo ni tú obliguemos al otro a ser como yo o como tú
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2012-08-13 20:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20  9:30 [PATCH] mfd/regulator: tps65217: Move regulator plat data handling to regulator AnilKumar Ch
2012-07-27 12:48 ` Samuel Ortiz
2012-07-31 14:30   ` AnilKumar, Chimata
2012-08-01  5:25     ` AnilKumar, Chimata
     [not found]     ` <331ABD5ECB02734CA317220B2BBEABC13EA07402@DBDE01.ent.ti.com>
2012-08-06  7:10       ` AnilKumar, Chimata
2012-08-13  8:27 ` Matthias Kaehlcke
2012-08-13 13:35   ` AnilKumar, Chimata
2012-08-13 20:02     ` Matthias Kaehlcke [this message]

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=20120813200250.GA3822@darwin \
    --to=matthias.list@kaehlcke.net \
    --cc=anilkumar@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sameo@linux.intel.com \
    --cc=sfr@canb.auug.org.au \
    /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).