From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: [PATCH v2 6/8] regulator: sy8824x: add SY20276 support
Date: Wed, 28 Aug 2019 06:12:05 +0000 [thread overview]
Message-ID: <20190828140048.71df2899@xhacker.debian> (raw)
In-Reply-To: <20190828135646.52457ac3@xhacker.debian>
The differences between SY8824C and SY20276 are different vsel_min,
vsel_step, vsel_count and regs for mode/enable.
Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
---
drivers/regulator/sy8824x.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/drivers/regulator/sy8824x.c b/drivers/regulator/sy8824x.c
index c93c49e64315..10d9180a0d77 100644
--- a/drivers/regulator/sy8824x.c
+++ b/drivers/regulator/sy8824x.c
@@ -171,6 +171,15 @@ static const struct sy8824_config sy8824e_cfg = {
.vsel_count = 64,
};
+static const struct sy8824_config sy20276_cfg = {
+ .vol_reg = 0x00,
+ .mode_reg = 0x01,
+ .enable_reg = 0x01,
+ .vsel_min = 600000,
+ .vsel_step = 10000,
+ .vsel_count = 128,
+};
+
static const struct of_device_id sy8824_dt_ids[] = {
{
.compatible = "silergy,sy8824c",
@@ -180,6 +189,10 @@ static const struct of_device_id sy8824_dt_ids[] = {
.compatible = "silergy,sy8824e",
.data = &sy8824e_cfg
},
+ {
+ .compatible = "silergy,sy20276",
+ .data = &sy20276_cfg
+ },
{ }
};
MODULE_DEVICE_TABLE(of, sy8824_dt_ids);
--
2.23.0.rc1
next prev parent reply other threads:[~2019-08-28 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 6:08 [PATCH v2 0/8] regulator: support Silergy SY8824C/SY8824E etc Jisheng Zhang
2019-08-28 6:08 ` [PATCH v2 1/8] regulator: add binding for the SY8824C voltage regulator Jisheng Zhang
2019-08-28 6:09 ` [PATCH v2 2/8] regulator: add support for SY8824C regulator Jisheng Zhang
2019-08-28 6:10 ` [PATCH v2 3/8] dt-bindings: sy8824x: Document SY8824E support Jisheng Zhang
2019-08-28 6:10 ` [PATCH v2 4/8] regulator: sy8824x: add " Jisheng Zhang
2019-08-28 6:11 ` [PATCH v2 5/8] dt-bindings: sy8824x: Document SY20276 support Jisheng Zhang
2019-08-28 6:12 ` Jisheng Zhang [this message]
2019-08-28 6:12 ` [PATCH v2 7/8] dt-bindings: sy8824x: Document SY20278 support Jisheng Zhang
2019-08-28 6:13 ` [PATCH v2 8/8] regulator: sy8824x: add " Jisheng Zhang
2019-08-28 10:08 ` [PATCH v2 0/8] regulator: support Silergy SY8824C/SY8824E etc Mark Brown
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=20190828140048.71df2899@xhacker.debian \
--to=jisheng.zhang@synaptics.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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).