From: Robin Gong <b38343@freescale.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: linux-kernel@vger.kernel.org, grant.likely@linaro.org,
rob.herring@calxeda.com, lgirdwood@gmail.com, broonie@kernel.org,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
rob@landley.net
Subject: Re: [PATCH v2] regulator: pfuze100: add pfuze100 regulator driver
Date: Mon, 15 Jul 2013 14:40:39 +0800 [thread overview]
Message-ID: <20130715064037.GA4722@Robin-OptiPlex-780> (raw)
In-Reply-To: <20130715012233.GA2730@S2101-09.ap.freescale.net>
Shawn, Thanks for your carefully review and I will correct it and send the patch again. some comments below:
> > +
> > +struct pfuze_regulator {
> > + struct regulator_desc desc;
> > + unsigned char stby_reg;
> > + unsigned char stby_mask;
> > +};
> > +
> > +enum pfuze_id {
> > + PFUZE_ID_PFUZE100,
> > + PFUZE_ID_INVALID,
> > +};
>
> Have a blank line here.
>
> Is there any other valid ID other than PFUZE_ID_PFUZE100? If not, we
> may not need this pfuze_id at all. All the use of it is in
> pfuze_identify() for dev_info output.
>
Yes, Now there is only one chip PFUZE100 here, but I'm told before there will be a series of pfuze family such as PFUZE101,PFUZE102..etc, so I keep the place for future.
> > +struct pfuze_chip {
> > + struct pfuze_regulator *regulators_desc;
> > + int num_regulators;
> > + struct regmap *regmap;
> > + struct device *dev;
> > + enum pfuze_id chip; /*chip type*/
>
> /* comment */
>
> Also I do not see much necessity of this member. It's only used in
> function pfuze_identify(), from what I can see.
>
Ditto
> > + struct regulator_dev *regulators[];
> > +};
> > +
> > +static struct regulator_ops pfuze100_ldo_regulator_ops;
> > +static struct regulator_ops pfuze100_fixed_regulator_ops;
> > +static struct regulator_ops pfuze100_sw_regulator_ops;
> > +static struct regulator_ops pfuze100_swb_regulator_ops;
> > +
> > +static const int pfuze100_swbst[] = {
> > + 5000000, 5050000, 5100000, 5150000,
> > +};
> > +
> > +static const int pfuze100_vsnvs[] = {
> > + 1000000, 1100000, 1200000, 1300000, 1500000, 1800000, 3000000,
> > +};
> > +
> > +static const struct i2c_device_id pfuze_device_id[] = {
> > + {.name = "pfuze100", .driver_data = PFUZE_ID_PFUZE100},
>
> You do not use .driver_data in the driver at all, and can just drop it.
>
> > + {},
> > +};
> > +MODULE_DEVICE_TABLE(i2c, pfuze_device_id);
> > +
> > +
>
> Drop one blank line.
>
> > +static const struct of_device_id pfuze_dt_ids[] = {
> > + { .compatible = "fsl,pfuze100", .data = (void *)PFUZE_ID_PFUZE100},
>
> You do not use .data in the driver at all, and can just drop it.
>
good catch. .driver_data of i2c_device_id and .data of of_device_id are two different ways to let driver know which chip used now by DTS or not. I should use them to know which chip used now ,although I can know by reading chipid register.
next prev parent reply other threads:[~2013-07-15 6:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 4:54 [PATCH v2] regulator: pfuze100: add pfuze100 regulator driver Robin Gong
[not found] ` <1373604855-17714-1-git-send-email-b38343-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-07-12 14:40 ` Mark Brown
2013-07-12 16:15 ` Robin Gong
2013-07-15 15:09 ` Mark Brown
2013-07-15 1:22 ` Shawn Guo
2013-07-15 6:40 ` Robin Gong [this message]
2013-07-15 6:49 ` Shawn Guo
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=20130715064037.GA4722@Robin-OptiPlex-780 \
--to=b38343@freescale.com \
--cc=broonie@kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=shawn.guo@linaro.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).