From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Brian Masney <masneyb@onstation.org>
Cc: georgi.djakov@linaro.org, linux-arm-msm@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 1/2] dt-bindings: interconnect: qcom: add msm8974 bindings
Date: Wed, 4 Sep 2019 12:03:57 -0700 [thread overview]
Message-ID: <20190904190357.GI574@tuxbook-pro> (raw)
In-Reply-To: <20190904102042.GA14484@onstation.org>
On Wed 04 Sep 03:20 PDT 2019, Brian Masney wrote:
> On Tue, Sep 03, 2019 at 10:01:03PM -0700, Bjorn Andersson wrote:
> > On Mon 02 Sep 14:19 PDT 2019, Brian Masney wrote:
> > > + mmssnoc: interconnect@fc478000 {
> > > + reg = <0xfc478000 0x4000>;
> > > + compatible = "qcom,msm8974-mmssnoc";
> > > + #interconnect-cells = <1>;
> > > + clock-names = "bus", "bus_a";
> > > + clocks = <&rpmcc RPM_SMD_MMSSNOC_AHB_CLK>,
> > > + <&rpmcc RPM_SMD_MMSSNOC_AHB_A_CLK>;
> >
> > Isn't MMSS_S0_AXI_CLK the bus clock of the mmssnoc (which somehow seems
> > to depend on mmssnoc_ahb_clk)?
>
> I'll give that a try. Do you know which clock I should use for bus_a
> here? On the mmcc, I see the following mmss clocks available:
>
> MMSS_AHB_CLK_SRC
> MMSS_AXI_CLK_SRC
> MMSS_RBCPR_CLK_SRC
> MMSS_MISC_AHB_CLK
> MMSS_MMSSNOC_AHB_CLK
> MMSS_MMSSNOC_BTO_AHB_CLK
> MMSS_MMSSNOC_AXI_CLK
> MMSS_S0_AXI_CLK
>
> I'm also unsure of what's going on at the hardware level that the second
> clock (bus_a) is needed.
>
In msm-3.4 clock-8974.c both bus and bus_a is defined as
mmss_s0_axi_clk. But iirc I also needed mmssnoc_axi_clk to get DSI
working on my devices, which is listed as .depends of the s0_axi clock.
So that probably needs some more investigation...But easiest would
probably be to just have the mmss_noc use them both listed as bus
clocks?
Regards,
Bjorn
> > > + mdss: mdss@fd900000 {
> >
> > I think you can omit the client, as this adheres to the standard binding
> > for interconnect clients. And you don't need to have an example that
> > covers all compatibles either...
>
> OK, I'll drop some of these.
>
> > > diff --git a/include/dt-bindings/interconnect/qcom,msm8974.h b/include/dt-bindings/interconnect/qcom,msm8974.h
> > > new file mode 100644
> > > index 000000000000..58acf7196410
> > > --- /dev/null
> > > +++ b/include/dt-bindings/interconnect/qcom,msm8974.h
> > > @@ -0,0 +1,146 @@
> > > +/* SPDX-License-Identifier: GPL-2.0 */
> >
> > Would you mind dual licensing this part as well?
>
> Sure, that was an oversight on my part.
>
> > Apart from that, I think this binding looks good.
>
> Thanks,
>
> Brian
next prev parent reply other threads:[~2019-09-04 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 21:19 [PATCH RFC 0/2] interconnect: qcom: add msm8974 driver Brian Masney
2019-09-02 21:19 ` [PATCH RFC 1/2] dt-bindings: interconnect: qcom: add msm8974 bindings Brian Masney
2019-09-04 5:01 ` Bjorn Andersson
2019-09-04 10:20 ` Brian Masney
2019-09-04 19:03 ` Bjorn Andersson [this message]
2019-09-02 21:19 ` [PATCH RFC 2/2] interconnect: qcom: add msm8974 driver Brian Masney
2019-09-04 5:39 ` Bjorn Andersson
2019-09-04 11:10 ` Marc Gonzalez
2019-09-28 9:57 ` Brian Masney
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=20190904190357.GI574@tuxbook-pro \
--to=bjorn.andersson@linaro.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=masneyb@onstation.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).