From: Stephen Boyd <swboyd@chromium.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Satya Priya <quic_c_skakit@quicinc.com>
Cc: Lee Jones <lee.jones@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Das Srinagesh <gurus@codeaurora.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_collinsd@quicinc.com,
quic_subbaram@quicinc.com, quic_jprakash@quicinc.com
Subject: Re: [PATCH V7 3/5] regulator: Add a regulator driver for the PM8008 PMIC
Date: Fri, 18 Feb 2022 17:50:38 -0800 [thread overview]
Message-ID: <CAE-0n50GRE1hUxpeLcv_jdNtxHuABMpGNJO5oMvMGimQHxAwHA@mail.gmail.com> (raw)
In-Reply-To: <1645182064-15843-4-git-send-email-quic_c_skakit@quicinc.com>
Quoting Satya Priya (2022-02-18 03:01:01)
> Qualcomm Technologies, Inc. PM8008 is an I2C controlled PMIC
> containing 7 LDO regulators. Add a PM8008 regulator driver to
> support PMIC regulator management via the regulator framework.
>
> Signed-off-by: Satya Priya <quic_c_skakit@quicinc.com>
> diff --git a/drivers/regulator/qcom-pm8008-regulator.c b/drivers/regulator/qcom-pm8008-regulator.c
> new file mode 100644
> index 0000000..1c52864
> --- /dev/null
> +++ b/drivers/regulator/qcom-pm8008-regulator.c
> @@ -0,0 +1,205 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/* Copyright (c) 2022, The Linux Foundation. All rights reserved. */
> +
> +#include <linux/device.h>
> +#include <linux/kernel.h>
> +#include <linux/module.h>
> +#include <linux/of.h>
> +#include <linux/of_device.h>
> +#include <linux/platform_device.h>
> +#include <linux/regmap.h>
> +#include <linux/regulator/driver.h>
> +#include <linux/regulator/machine.h>
> +
> +#define VSET_STEP_MV 8
> +#define VSET_STEP_UV (VSET_STEP_MV * 1000)
> +
> +#define LDO_ENABLE_REG(base) ((base) + 0x46)
> +#define ENABLE_BIT BIT(7)
This is SPMI_COMMON_REG_ENABLE and SPMI_COMMON_ENABLE_MASK
> +
> +#define LDO_VSET_LB_REG(base) ((base) + 0x40)
> +
> +#define LDO_STEPPER_CTL_REG(base) ((base) + 0x3b)
> +#define DEFAULT_VOLTAGE_STEPPER_RATE 38400
> +#define STEP_RATE_MASK GENMASK(1, 0)
> +
> +struct regulator_data {
Please use a name like spmi_regulator_data :) Or pm8008_regulator_data?
Something that isn't so generic.
It seems similar to qcom_spmi-regulator.c so is there some reason we
can't shove this into there? Less code for things that aren't relevant I
guess?
> + const char *name;
> + const char *supply_name;
> + u16 base;
> + int min_uv;
> + int max_uv;
> + int min_dropout_uv;
> + const struct linear_range *voltage_range;
next prev parent reply other threads:[~2022-02-19 1:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 11:00 [PATCH V7 0/5] Add Qualcomm Technologies, Inc. PM8008 regulator driver Satya Priya
2022-02-18 11:00 ` [PATCH V7 1/5] dt-bindings: mfd: pm8008: Add pm8008 regulators Satya Priya
2022-02-19 1:39 ` Stephen Boyd
2022-02-28 14:14 ` Satya Priya Kakitapalli (Temp)
2022-02-28 20:31 ` Stephen Boyd
2022-02-18 11:01 ` [PATCH V7 2/5] mfd: pm8008: Add mfd cell struct to register LDOs Satya Priya
2022-02-18 11:01 ` [PATCH V7 3/5] regulator: Add a regulator driver for the PM8008 PMIC Satya Priya
2022-02-19 1:50 ` Stephen Boyd [this message]
2022-02-28 14:18 ` Satya Priya Kakitapalli (Temp)
2022-02-18 11:01 ` [PATCH V7 4/5] arm64: dts: qcom: pm8008: Add base dts file Satya Priya
2022-02-19 1:57 ` Stephen Boyd
2022-02-28 14:18 ` Satya Priya Kakitapalli (Temp)
2022-02-18 11:01 ` [PATCH V7 5/5] arm64: dts: qcom: sc7280: Add pm8008 support for sc7280-idp Satya Priya
2022-02-19 2:01 ` Stephen Boyd
2022-02-28 14:25 ` Satya Priya Kakitapalli (Temp)
2022-02-28 20:36 ` Stephen Boyd
2022-03-07 14:49 ` Satya Priya Kakitapalli (Temp)
2022-03-08 20:50 ` Stephen Boyd
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=CAE-0n50GRE1hUxpeLcv_jdNtxHuABMpGNJO5oMvMGimQHxAwHA@mail.gmail.com \
--to=swboyd@chromium.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gurus@codeaurora.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_c_skakit@quicinc.com \
--cc=quic_collinsd@quicinc.com \
--cc=quic_jprakash@quicinc.com \
--cc=quic_subbaram@quicinc.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).