From: Erick Chen <erick.chen@spreadtrum.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: Mark Brown <broonie@kernel.org>,
Baolin Wang <baolin.wang@spreadtrum.com>,
Liam Girdwood <lgirdwood@gmail.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: sc2731: Fix defines for SC2731_WR_UNLOCK and SC2731_PWR_WR_PROT_VALUE
Date: Mon, 1 Jan 2018 14:14:05 +0800 [thread overview]
Message-ID: <20180101061404.GA29748@spreadtrum.com> (raw)
In-Reply-To: <20171229061218.14766-1-axel.lin@ingics.com>
Hi Axel,
O 五, 12月 29, 2017 at 02:12:18下午 +0800, Axel Lin wrote:
> The define for SC2731_WR_UNLOCK and SC2731_PWR_WR_PROT_VALUE are
> swapped, so the code calling regmap_write() looks strange. Fix it.
> regmap_write takes reg parameter first then val.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> Hi Erick,
> I don't have the datasheet. Can you check this?
These definitions are following our datasheet's naming rule, may seem
puzzling. And your patch could be better, my suggestions are as follows.
Thanks,
> Thanks,
> Axel
> drivers/regulator/sc2731-regulator.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/regulator/sc2731-regulator.c b/drivers/regulator/sc2731-regulator.c
> index 794fcd504b3d..7f2b137bb98a 100644
> --- a/drivers/regulator/sc2731-regulator.c
> +++ b/drivers/regulator/sc2731-regulator.c
> @@ -13,8 +13,8 @@
> /*
> * SC2731 regulator lock register
> */
> -#define SC2731_PWR_WR_PROT_VALUE 0xf0c
> -#define SC2731_WR_UNLOCK 0x6e7f
> +#define SC2731_WR_UNLOCK 0xf0c
> +#define SC2731_PWR_WR_PROT_VALUE 0x6e7f
#define SC2731_PWR_WR_PROT 0xf0c
#define SC2731_WR_UNLOCK_VALUE 0x6e7f
> /*
> * SC2731 enable register
> @@ -203,8 +203,8 @@ static struct regulator_desc regulators[] = {
>
> static int sc2731_regulator_unlock(struct regmap *regmap)
> {
> - return regmap_write(regmap, SC2731_PWR_WR_PROT_VALUE,
> - SC2731_WR_UNLOCK);
> + return regmap_write(regmap, SC2731_WR_UNLOCK,
> + SC2731_PWR_WR_PROT_VALUE);
return regmap_write(regmap, SC2731_PWR_WR_PROT,
SC2731_WR_UNLOCK_VALUE);
> }
>
> static int sc2731_regulator_probe(struct platform_device *pdev)
> --
> 2.14.1
>
prev parent reply other threads:[~2018-01-01 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 6:12 [PATCH] regulator: sc2731: Fix defines for SC2731_WR_UNLOCK and SC2731_PWR_WR_PROT_VALUE Axel Lin
2018-01-01 6:14 ` Erick Chen [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=20180101061404.GA29748@spreadtrum.com \
--to=erick.chen@spreadtrum.com \
--cc=axel.lin@ingics.com \
--cc=baolin.wang@spreadtrum.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.