devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Bjorn Andersson <bjorn@kryo.se>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Mike Turquette <mturquette@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Kumar Gala <galak@codeaurora.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	Eduardo Valentin <edubezval@gmail.com>,
	nrajan@codeaurora.com, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2 1/2] clk: qcom: gcc-msm8960: add child devices support.
Date: Fri, 30 Jan 2015 14:03:50 -0800	[thread overview]
Message-ID: <54CBFFC6.9080302@codeaurora.org> (raw)
In-Reply-To: <CAJAp7Og5eJkKVoaizNd4MxY9SK3kAg8=4rxS3Gm0iYeQKk8vUA@mail.gmail.com>

On 01/30/15 14:00, Bjorn Andersson wrote:
> On Fri, Jan 30, 2015 at 1:16 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>> On 01/30/15 10:06, Srinivas Kandagatla wrote:
> [..]
>>> Stephen Any comments?
>> I don't understand any of this. We should be making a specific tsens
>> device directly in the gcc driver probe and not doing any sort of
>> of_platform_populate(). This is what I had, but it probably could be
>> done better so that we can assign the struct device's of_node pointer
>> before registering on the platform bus.
>>
>>         platform_device_register_data(&pdev->dev, "tsens8960-tm", -1,
>>                         &pdev->dev.of_node, sizeof(&pdev->dev.of_node));
>>
>> Then if we need to add any properties like #sensor-cells or coefficients
>> the tsens driver can use the same of_node that gcc is using.
>>
> That makes sense and the dt will describe the hardware nicely, but how
> do you get access to the register space from the tsens driver?
>
> Will dev_get_regmap(pdev->dev.parent, NULL); find the mmio regmap of
> gcc perhaps?
>

Yes that's the plan. We'll have to do slightly different stuff for 8974
where tsens is split out from gcc into its own space. That should still
be easy enough though by checking the of_node against some compatible
string.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-01-30 22:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30  9:50 [PATCH 0/2] clk: qcom: gcc: Add support to child devices Srinivas Kandagatla
2015-01-30  9:51 ` [PATCH 1/2] clk: qcom: gcc-msm8960: add child devices support Srinivas Kandagatla
2015-01-30  9:51 ` [PATCH 2/2] clk: qcom: gcc bindings: Update to add child node support Srinivas Kandagatla
2015-01-30 10:16 ` [PATCH v2 0/2] clk: qcom: gcc: Add support to child devices Srinivas Kandagatla
2015-01-30 10:17   ` [PATCH v2 1/2] clk: qcom: gcc-msm8960: add child devices support Srinivas Kandagatla
2015-01-30 16:57     ` Bjorn Andersson
2015-01-30 18:06       ` Srinivas Kandagatla
2015-01-30 21:16         ` Stephen Boyd
     [not found]           ` <54CBF4B4.6080208-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-01-30 22:00             ` Bjorn Andersson
2015-01-30 22:03               ` Stephen Boyd [this message]
2015-02-03 10:44           ` Srinivas Kandagatla
2015-01-30 10:18   ` [PATCH v2 2/2] clk: qcom: gcc bindings: Update to add child node support 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=54CBFFC6.9080302@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=arnd@arndb.de \
    --cc=bjorn@kryo.se \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=nrajan@codeaurora.com \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.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).