From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Florian Eckert <fe@dev.tdt.de>,
mturquette@baylibre.com, sboyd@kernel.org, yzhu@maxlinear.com,
rtanwar@maxlinear.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Eckert.Florian@googlemail.com
Subject: Re: [PATCH 2/2] dt-bindings: clock: intel,cgu-lgm: add mxl,control-gate option
Date: Mon, 31 Jul 2023 14:03:24 +0200 [thread overview]
Message-ID: <780aa090-3a97-abab-271f-59790df29cc4@linaro.org> (raw)
In-Reply-To: <20230731100349.184553-3-fe@dev.tdt.de>
On 31/07/2023 12:03, Florian Eckert wrote:
> Add the new option 'mxl,control-gate'. Gate clocks can be controlled
> either from this cgu clk driver or directly from power management
> driver/daemon. It is dependent on the power policy/profile requirements
> of the end product. To take control of gate clks from this driver, add the
> name of the gate to this <mxl,control-gate> devicetree property.
> Please refer to 'drivers/clk/x86/clk-lgm.c' source file for the gate names.
Choosing which driver controls clocks is OS policy, not DT property. Any
reference to drivers in property description is already a warning sign.
You described the desired Linux feature or behavior, not the actual
hardware. The bindings are about the latter, so instead you need to
rephrase the property and its description to match actual hardware
capabilities/features/configuration etc.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-31 12:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 10:03 [PATCH 0/2] clk: mxl: add mxl,control-gate dts property Florian Eckert
2023-07-31 10:03 ` [PATCH 1/2] " Florian Eckert
2023-07-31 10:03 ` [PATCH 2/2] dt-bindings: clock: intel,cgu-lgm: add mxl,control-gate option Florian Eckert
2023-07-31 11:11 ` Rob Herring
2023-07-31 12:03 ` Krzysztof Kozlowski [this message]
2023-07-31 12:59 ` Florian Eckert
2023-07-31 13:01 ` Krzysztof Kozlowski
2023-08-01 8:09 ` Florian Eckert
2023-08-05 19:09 ` Krzysztof Kozlowski
2023-08-08 7:53 ` Yi xin Zhu
2023-08-09 8:56 ` Florian Eckert
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=780aa090-3a97-abab-271f-59790df29cc4@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Eckert.Florian@googlemail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fe@dev.tdt.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=rtanwar@maxlinear.com \
--cc=sboyd@kernel.org \
--cc=yzhu@maxlinear.com \
/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