linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Georgi Djakov <georgi.djakov@linaro.org>
To: Lina Iyer <lina.iyer@linaro.org>
Cc: broonie@kernel.org, lgirdwood@gmail.com, andy.gross@linaro.org,
	sboyd@codeaurora.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 14:52:57 +0200	[thread overview]
Message-ID: <56BB32A9.7090002@linaro.org> (raw)
In-Reply-To: <20160209222154.GB1646@linaro.org>

Hi Lina,
Thanks for reviewing.

On 02/10/2016 12:21 AM, Lina Iyer wrote:
> On Tue, Feb 09 2016 at 06:13 -0700, Georgi Djakov wrote:
[..]
>> +#define    SPM_REG_STS_1            0x10
>> +#define    SPM_REG_VCTL            0x14
>> +#define    SPM_REG_PMIC_DATA_0        0x28
>> +#define    SPM_REG_PMIC_DATA_1        0x2c
>> +#define    SPM_REG_RST            0x30
>> +
> These register offsets are SoC specific. You may want to follow the model
> of drivers/soc/qcom/spm.c in getting register offsets.
> 
> While I see that you are only supporting APQ8064 with this patch, you
> probably would want to think a bit far ahead. To support any other QCOM
> SoC, you would need extensive changes.
> 

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?

[..]
>> +
>> +module_platform_driver(qcom_saw_regulator_driver);
>> +
> builtin_platform_driver() perhaps ?
> 

It's tested as module too, so there is no reason to change to builtin.

Thanks,
Georgi

  parent reply	other threads:[~2016-02-10 12:52 UTC|newest]

Thread overview: 15+ 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 22:21 ` 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 [this message]
2016-02-10 18:36     ` Stephen Boyd
2016-02-10 18:43       ` Mark Brown
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

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=56BB32A9.7090002@linaro.org \
    --to=georgi.djakov@linaro.org \
    --cc=andy.gross@linaro.org \
    --cc=broonie@kernel.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 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).