From: Mark Brown <broonie@kernel.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Georgi Djakov <georgi.djakov@linaro.org>,
Lina Iyer <lina.iyer@linaro.org>,
lgirdwood@gmail.com, andy.gross@linaro.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4] regulator: qcom-saw: Add support for SAW regulators
Date: Wed, 10 Feb 2016 18:43:27 +0000 [thread overview]
Message-ID: <20160210184327.GB13270@sirena.org.uk> (raw)
In-Reply-To: <20160210183651.GH30978@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
On Wed, Feb 10, 2016 at 10:36:51AM -0800, Stephen Boyd wrote:
> On 02/10, Georgi Djakov wrote:
> > The purpose of this patch it to add support for 8064. Supporting other
> > SoCs requires just read/writing at different offsets. To handle this we
> > can convert the above defines to a table containing the offsets for each
> > SoC. I don't think these are extensive changes or do i miss something?
> In some designs we have to talk to the PMIC with SPMI
> transactions to change the mode depending on the voltages. How do
> we plan to handle that case where the regulator control is split
> between two busses, SPMI and MMIO?
Mixed control interfaces are in general a diaster with Linux, I'd
suggest remonstrating with your system designers about doing them but in
this case since it's a syscon presumably you could hang the device off
the SPMI bus in the cases where that's in use.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-02-10 18:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 13:12 [PATCH v4] regulator: qcom-saw: Add support for SAW regulators Georgi Djakov
2016-02-09 18:20 ` Applied "regulator: qcom-saw: Add support for SAW regulators" to the regulator tree Mark Brown
2016-02-09 22:21 ` [PATCH v4] regulator: qcom-saw: Add support for SAW regulators Lina Iyer
2016-02-10 10:13 ` Mark Brown
2016-02-10 16:42 ` Lina Iyer
2016-02-10 18:54 ` Mark Brown
2016-02-10 12:52 ` Georgi Djakov
2016-02-10 18:36 ` Stephen Boyd
2016-02-10 18:43 ` Mark Brown [this message]
2016-02-10 19:04 ` Stephen Boyd
2016-02-10 19:21 ` Mark Brown
2016-02-10 22:46 ` Stephen Boyd
2016-02-11 10:17 ` Georgi Djakov
2016-02-12 0:17 ` Stephen Boyd
2016-02-12 23:03 ` Mark Brown
2016-02-19 16:07 ` Mark Brown
2016-03-15 9:29 ` Applied "regulator: qcom-saw: Add support for SAW regulators" to the regulator tree Mark Brown
2016-03-15 9:30 ` 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=20160210184327.GB13270@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy.gross@linaro.org \
--cc=georgi.djakov@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=lina.iyer@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@codeaurora.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.