All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>,
	Bjorn Andersson <bjorn.andersson@sonymobile.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Kumar Gala <galak@codeaurora.org>,
	Lee Jones <lee.jones@linaro.org>,
	Josh Cartwright <joshc@codeaurora.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 1/3] soc: devicetree: bindings: Add Qualcomm RPM DT binding
Date: Wed, 18 Jun 2014 09:34:08 +0100	[thread overview]
Message-ID: <53A14F00.9010904@linaro.org> (raw)
In-Reply-To: <53A0D651.20605@codeaurora.org>



On 18/06/14 00:59, Stephen Boyd wrote:
> On 06/16/14 11:46, Bjorn Andersson wrote:
>> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,rpm.txt b/Documentation/devicetree/bindings/soc/qcom/qcom,rpm.txt
>> new file mode 100644
>> index 0000000..0366533
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,rpm.txt
>> @@ -0,0 +1,260 @@
>> +Qualcomm Resource Power Manager (RPM)
>> +
> [...]
>> +
>> +- reg:
>> +	Usage: required
>> +	Value type: <prop-encoded-array>
>> +	Definition: two entries specifying the RPM's message ram and ipc register
>> +
>> +- reg-names:
>> +	Usage: required
>> +	Value type: <string-array>
>> +	Definition: must contain the following, in order:
>> +		    "msg_ram"
>> +		    "ipc"
>
> ipc is concerning....
>
>> +	rpm@108000 {
>> +		compatible = "qcom,rpm-msm8960";
>> +		reg = <0x108000 0x1000 0x2011008 0x4>;
>> +
>
> (reg-names is missing from the example)
>
> because ipc is actually a register inside the Krait complex's global
> clock control/distribution hardware block (it's located at 0x2011000).
>  From what I can tell, this is the only non-clock/power register inside
> there. I plan to send out a driver for this hardware block so that I can
> switch the L2 aux source mux over to PLL8 instead of PXO (done with a
> single register write to 0x2011028) and this mapping/use here is going
> to conflict with that unless I only map the single register like is done
> here.
>
> I wonder if we'd be better off making this region a separate node and
> having some phandle to it here in the RPM node? That way we have a

Can't we use syscon based on regmap here?  syscon is a better way to 
share a common register space across multiple drivers.

> driver that provides a clock and some IPC handle the RPM driver can get.
> The SMD driver also uses the same register to kick other processors so
> having some generic IPC handle may be useful there too.
>

WARNING: multiple messages have this Message-ID (diff)
From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/3] soc: devicetree: bindings: Add Qualcomm RPM DT binding
Date: Wed, 18 Jun 2014 09:34:08 +0100	[thread overview]
Message-ID: <53A14F00.9010904@linaro.org> (raw)
In-Reply-To: <53A0D651.20605@codeaurora.org>



On 18/06/14 00:59, Stephen Boyd wrote:
> On 06/16/14 11:46, Bjorn Andersson wrote:
>> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,rpm.txt b/Documentation/devicetree/bindings/soc/qcom/qcom,rpm.txt
>> new file mode 100644
>> index 0000000..0366533
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,rpm.txt
>> @@ -0,0 +1,260 @@
>> +Qualcomm Resource Power Manager (RPM)
>> +
> [...]
>> +
>> +- reg:
>> +	Usage: required
>> +	Value type: <prop-encoded-array>
>> +	Definition: two entries specifying the RPM's message ram and ipc register
>> +
>> +- reg-names:
>> +	Usage: required
>> +	Value type: <string-array>
>> +	Definition: must contain the following, in order:
>> +		    "msg_ram"
>> +		    "ipc"
>
> ipc is concerning....
>
>> +	rpm at 108000 {
>> +		compatible = "qcom,rpm-msm8960";
>> +		reg = <0x108000 0x1000 0x2011008 0x4>;
>> +
>
> (reg-names is missing from the example)
>
> because ipc is actually a register inside the Krait complex's global
> clock control/distribution hardware block (it's located at 0x2011000).
>  From what I can tell, this is the only non-clock/power register inside
> there. I plan to send out a driver for this hardware block so that I can
> switch the L2 aux source mux over to PLL8 instead of PXO (done with a
> single register write to 0x2011028) and this mapping/use here is going
> to conflict with that unless I only map the single register like is done
> here.
>
> I wonder if we'd be better off making this region a separate node and
> having some phandle to it here in the RPM node? That way we have a

Can't we use syscon based on regmap here?  syscon is a better way to 
share a common register space across multiple drivers.

> driver that provides a clock and some IPC handle the RPM driver can get.
> The SMD driver also uses the same register to kick other processors so
> having some generic IPC handle may be useful there too.
>

  parent reply	other threads:[~2014-06-18  8:34 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 18:46 [PATCH v3 0/3] Qualcomm Resource Power Manager driver Bjorn Andersson
2014-06-16 18:46 ` Bjorn Andersson
2014-06-16 18:46 ` Bjorn Andersson
2014-06-16 18:46 ` [PATCH v3 1/3] soc: devicetree: bindings: Add Qualcomm RPM DT binding Bjorn Andersson
2014-06-16 18:46   ` Bjorn Andersson
2014-06-16 18:46   ` Bjorn Andersson
2014-06-17 23:59   ` Stephen Boyd
2014-06-17 23:59     ` Stephen Boyd
     [not found]     ` <53A0D651.20605-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-06-18  5:19       ` Bjorn Andersson
2014-06-18  5:19         ` Bjorn Andersson
2014-06-18  5:19         ` Bjorn Andersson
2014-06-18  8:34     ` Srinivas Kandagatla [this message]
2014-06-18  8:34       ` Srinivas Kandagatla
2014-06-18 19:16       ` Stephen Boyd
2014-06-18 19:16         ` Stephen Boyd
2014-07-04  6:05   ` Pramod Gurav
2014-07-04  6:05     ` Pramod Gurav
2014-07-04  6:05     ` Pramod Gurav
2014-06-16 18:46 ` [PATCH v3 2/3] soc: qcom-rpm: Driver for the Qualcomm RPM Bjorn Andersson
2014-06-16 18:46   ` Bjorn Andersson
2014-06-16 18:46   ` Bjorn Andersson
2014-07-04  6:16   ` pramod gurav
2014-07-04  6:16     ` pramod gurav
2014-06-16 18:46 ` [PATCH v3 3/3] regulator: qcom-rpm: Regulator driver " Bjorn Andersson
2014-06-16 18:46   ` Bjorn Andersson
2014-06-16 18:46   ` Bjorn Andersson
2014-06-17 17:07 ` [PATCH v3 0/3] Qualcomm Resource Power Manager driver Kevin Hilman
2014-06-17 17:07   ` Kevin Hilman
2014-06-17 17:07   ` Kevin Hilman
2014-06-17 17:15   ` Bjorn Andersson
2014-06-17 17:15     ` Bjorn Andersson
2014-06-18 15:53     ` Kevin Hilman
2014-06-18 15:53       ` Kevin Hilman
2014-06-18 15:53       ` Kevin Hilman
2014-06-18 16:03       ` Kumar Gala
2014-06-18 16:03         ` Kumar Gala
2014-06-18 16:44         ` Kevin Hilman
2014-06-18 16:44           ` Kevin Hilman
2014-06-18 16:44           ` Kevin Hilman
     [not found]           ` <7hegym6uca.fsf-4poPxKt068f/PtFMR13I2A@public.gmane.org>
2014-06-19  3:55             ` Jassi Brar
2014-06-19  3:55               ` Jassi Brar
2014-06-19  3:55               ` Jassi Brar
2014-06-19 18:22               ` Bjorn Andersson
2014-06-19 18:22                 ` Bjorn Andersson
2014-06-19 20:01                 ` Jassi Brar
2014-06-19 20:01                   ` Jassi Brar
2014-06-20  4:59                   ` Bjorn Andersson
2014-06-20  4:59                     ` Bjorn Andersson
2014-06-20  5:17           ` Bjorn Andersson
2014-06-20  5:17             ` Bjorn Andersson
2014-06-20 13:18             ` Jassi Brar
2014-06-20 13:18               ` Jassi Brar
2014-06-18 16:48         ` Lee Jones
2014-06-18 16:48           ` Lee Jones
2014-06-17 21:49 ` Srinivas Kandagatla
2014-06-17 21:49   ` Srinivas Kandagatla
2014-06-17 21:49   ` Srinivas Kandagatla

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=53A14F00.9010904@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=joshc@codeaurora.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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.