public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v6 3/6] dt-bindings: arm: msm: Rework kpss-gcc driver Documentation to yaml
Date: Thu, 12 Jan 2023 19:30:00 -0600	[thread overview]
Message-ID: <167357340002.589187.8338617302523243292.robh@kernel.org> (raw)
In-Reply-To: <20230110183259.19142-4-ansuelsmth@gmail.com>


On Tue, 10 Jan 2023 19:32:56 +0100, Christian Marangi wrote:
> Rework kpss-gcc driver Documentation to yaml Documentation and move it
> to clock as it's a clock-controller.
> The current kpss-gcc Documentation have major problems and can't be
> converted directly. Introduce various changes to the original
> Documentation.
> 
> Add #clock-cells additional binding as this clock outputs a static clk
> named acpu_l2_aux with supported compatible.
> Only some compatible require and outputs a clock, for the others, set
> only the reg as a required binding to correctly export the kpss-gcc
> registers. As the reg is shared also add the required syscon compatible.
> 
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
>  .../bindings/arm/msm/qcom,kpss-gcc.txt        | 44 ----------
>  .../bindings/clock/qcom,kpss-gcc.yaml         | 88 +++++++++++++++++++
>  2 files changed, 88 insertions(+), 44 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/arm/msm/qcom,kpss-gcc.txt
>  create mode 100644 Documentation/devicetree/bindings/clock/qcom,kpss-gcc.yaml
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2023-01-13  1:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 18:32 [PATCH v6 0/6] Krait Documentation conversion Christian Marangi
2023-01-10 18:32 ` [PATCH v6 1/6] dt-bindings: clock: Convert qcom,krait-cc to yaml Christian Marangi
2023-01-10 18:32 ` [PATCH v6 2/6] dt-bindings: arm: msm: Convert and split kpss-acc driver Documentation " Christian Marangi
2023-01-12  4:00   ` Dmitry Baryshkov
2023-01-13 13:18     ` Christian Marangi
2023-01-10 18:32 ` [PATCH v6 3/6] dt-bindings: arm: msm: Rework kpss-gcc " Christian Marangi
2023-01-13  1:30   ` Rob Herring [this message]
2023-01-10 18:32 ` [PATCH v6 4/6] ARM: dts: qcom: fix various wrong definition for kpss-gcc node Christian Marangi
2023-01-12  4:11   ` Dmitry Baryshkov
2023-01-10 18:32 ` [PATCH v6 5/6] ARM: dts: qcom: fix various wrong definition for kpss-acc-v1 Christian Marangi
2023-01-12  4:08   ` Dmitry Baryshkov
2023-01-10 18:32 ` [PATCH v6 6/6] ARM: dts: qcom: fix various wrong definition for kpss-acc-v2 Christian Marangi
2023-01-12  4:12   ` Dmitry Baryshkov

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=167357340002.589187.8338617302523243292.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=ansuelsmth@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.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=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.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