From: Pascal PAILLET-LME <p.paillet@st.com>
To: Axel Lin <axel.lin@ingics.com>, Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: stpmic1: Remove regul_id and *regmap from struct stpmic1_regulator
Date: Mon, 11 Feb 2019 08:46:20 +0000 [thread overview]
Message-ID: <5C61365C.8050709@st.com> (raw)
In-Reply-To: <20190209043935.24637-1-axel.lin@ingics.com>
Hello Axel,
Le 02/09/2019 05:39 AM, Axel Lin a écrit :
> At the context with *rdev available, there is no problem to get regulator
> id and *regmap, so no need to store them in struct stpmic1_regulator.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> drivers/regulator/stpmic1_regulator.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/regulator/stpmic1_regulator.c b/drivers/regulator/stpmic1_regulator.c
> index 963e67fa9ca6..dd5c8fb1ff86 100644
> --- a/drivers/regulator/stpmic1_regulator.c
> +++ b/drivers/regulator/stpmic1_regulator.c
> @@ -30,20 +30,16 @@ struct stpmic1_regulator_cfg {
>
> /**
> * stpmic1 regulator data: this structure is used as driver data
> - * @regul_id: regulator id
> * @reg_node: DT node of regulator (unused on non-DT platforms)
> * @cfg: stpmic specific regulator description
> * @mask_reset: mask_reset bit value
> * @irq_curlim: current limit interrupt number
> - * @regmap: point to parent regmap structure
> */
> struct stpmic1_regulator {
> - unsigned int regul_id;
> struct device_node *reg_node;
> const struct stpmic1_regulator_cfg *cfg;
> u8 mask_reset;
> int irq_curlim;
> - struct regmap *regmap;
> };
>
> static int stpmic1_set_mode(struct regulator_dev *rdev, unsigned int mode);
> @@ -477,7 +473,7 @@ static int stpmic1_set_icc(struct regulator_dev *rdev)
> struct stpmic1_regulator *regul = rdev_get_drvdata(rdev);
>
> /* enable switch off in case of over current */
> - return regmap_update_bits(regul->regmap, regul->cfg->icc_reg,
> + return regmap_update_bits(rdev->regmap, regul->cfg->icc_reg,
> regul->cfg->icc_mask, regul->cfg->icc_mask);
Maybe this is not compatible with a recommandation from
include/linux/regulator/driver.h:438:
* This should *not* be used directly by anything except the regulator
* core and notification injection (which should take the mutex and do
* no other direct access).
> }
>
...
thank you,
pascal
prev parent reply other threads:[~2019-02-11 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 4:39 [PATCH] regulator: stpmic1: Remove regul_id and *regmap from struct stpmic1_regulator Axel Lin
2019-02-11 8:46 ` Pascal PAILLET-LME [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=5C61365C.8050709@st.com \
--to=p.paillet@st.com \
--cc=axel.lin@ingics.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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