public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Marangi <ansuelsmth@gmail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Takashi Iwai <tiwai@suse.de>,
	Christian Brauner <brauner@kernel.org>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Marc Herbert <marc.herbert@intel.com>,
	James Smart <jsmart2021@gmail.com>,
	Justin Tee <justin.tee@broadcom.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v5 2/5] dt-bindings: arm: msm: Convert kpss-acc driver Documentation to yaml
Date: Fri, 16 Sep 2022 22:13:17 +0200	[thread overview]
Message-ID: <6324d8e1.170a0220.aba35.ba4f@mx.google.com> (raw)
In-Reply-To: <CAA8EJprEQOsm4TxGWJYZo04D1PagT3QmhDdYQkEid-KSP-tpTw@mail.gmail.com>

On Fri, Sep 16, 2022 at 11:06:35PM +0300, Dmitry Baryshkov wrote:
> On Fri, 16 Sept 2022 at 22:43, Christian Marangi <ansuelsmth@gmail.com> wrote:
> >
> > On Fri, Sep 16, 2022 at 02:17:15PM -0500, Rob Herring wrote:
> > > On Wed, Sep 14, 2022 at 04:22:53PM +0200, Christian Marangi wrote:
> > > > Convert kpss-acc driver Documentation to yaml.
> > > > The original Documentation was wrong all along. Fix it while we are
> > > > converting it.
> > > > The example was wrong as kpss-acc-v2 should only expose the regs but we
> > > > don't have any driver that expose additional clocks. The kpss-acc driver
> > > > is only specific to v1. For this exact reason, limit all the additional
> > > > bindings (clocks, clock-names, clock-output-names and #clock-cells) to
> > > > v1 and also flag that these bindings should NOT be used for v2.
> > >
> > > Odd that a clock controller has no clocks, but okay.
> > >
> >
> > As said in the commit v2 is only used for regs. v2 it's only used in
> > arch/arm/mach-qcom/platsmp.c to setup stuff cpu hotplug and bringup.
> >
> > Should we split the 2 driver? To me the acc naming seems to be just
> > recycled for v2 and it's not really a clk controller.
> >
> > So keeping v2 in arm/msm/qcom,kpss-acc-v2.yaml and v1 moved to clock?
> 
> I suspect that qcom,kpss-acc-v2 is misnamed as the "clock-controller".
> According to msm-3.10, these regions are used by the Krait core
> regulators.
>

Well we need to understand how to handle this... change the compatible
it's a nono for sure. In platsmp.c they are used for cpu power control
so could be that they are actually used to regulators. I would honestly
move v1 to clock and leave v2 to arm/msm but I'm not cetain on what name
to assign to the 2 yaml.

What do you think?

-- 
	Ansuel

  reply	other threads:[~2022-09-16 20:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 14:22 [PATCH v5 0/5] Krait Documentation conversion Christian Marangi
2022-09-14 14:22 ` [PATCH v5 1/5] dt-bindings: clock: Convert qcom,krait-cc to yaml Christian Marangi
2022-09-14 14:22 ` [PATCH v5 2/5] dt-bindings: arm: msm: Convert kpss-acc driver Documentation " Christian Marangi
2022-09-14 16:47   ` Rob Herring
2022-09-14 16:54     ` Christian Marangi
2022-09-16 19:17   ` Rob Herring
2022-09-16 19:42     ` Christian Marangi
2022-09-16 20:06       ` Dmitry Baryshkov
2022-09-16 20:13         ` Christian Marangi [this message]
2022-09-16 20:22           ` Dmitry Baryshkov
2022-09-16 20:27             ` Christian Marangi
2022-09-16 20:31               ` Dmitry Baryshkov
2022-09-16 21:54                 ` Christian Marangi
2022-09-17 13:45                   ` Dmitry Baryshkov
2022-09-17 18:57                     ` Christian Marangi
2022-09-17 19:44                       ` Christian Marangi
2022-09-17 20:46                         ` Dmitry Baryshkov
2022-09-17 20:58                           ` Christian Marangi
2022-09-14 14:22 ` [PATCH v5 3/5] dt-bindings: arm: msm: Rework kpss-gcc " Christian Marangi
2022-09-14 16:47   ` Rob Herring
2022-09-15  9:34   ` Krzysztof Kozlowski
2022-09-16 19:19   ` Rob Herring
2022-09-14 14:22 ` [PATCH v5 4/5] ARM: dts: qcom: fix various wrong definition for kpss-gcc node Christian Marangi
2022-12-23 10:17   ` Krzysztof Kozlowski
2022-12-23 10:17     ` Krzysztof Kozlowski
2022-09-14 14:22 ` [PATCH v5 5/5] ARM: dts: qcom: fix various wrong definition for kpss-acc Christian Marangi

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=6324d8e1.170a0220.aba35.ba4f@mx.google.com \
    --to=ansuelsmth@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=brauner@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=jsmart2021@gmail.com \
    --cc=justin.tee@broadcom.com \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.herbert@intel.com \
    --cc=martin.petersen@oracle.com \
    --cc=mturquette@baylibre.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=tiwai@suse.de \
    /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