From: Nishanth Menon <nm@ti.com>
To: Dhruva Gole <d-gole@ti.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Stephen Boyd" <sboyd@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Tony Lindgren" <tony@atomide.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Vibhore Vardhan" <vibhore@ti.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3 2/2] dt-bindings: cpufreq: Convert ti-cpufreq to json schema
Date: Wed, 9 Aug 2023 06:25:48 -0500 [thread overview]
Message-ID: <20230809112548.cf5o7yxqeu3nfqdq@kobold> (raw)
In-Reply-To: <20230809043012.gcsnn5bfr7j25ow7@dhruva>
On 10:00-20230809, Dhruva Gole wrote:
[..]
> > +description:
> > + Certain TI SoCs, like those in the am335x, am437x, am57xx, am62x and dra7xx
> > + families support different OPPs depending on the silicon variant in use.
> > + The ti-cpufreq driver can use revision and an efuse value from the SoC to
>
> Just learned about this yesterday, hence missed it in my earlier review.
> Looks like the kernel docs [0] say that we DON'T refer to Linux or
> "device driver" in bindings.
>
> Bindings should be based on what the hardware has, not what an OS and
> driver currently support.
Thanks for catching this. will fix in the next rev.
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2023-08-09 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 2:30 [PATCH V3 0/2] dt-bindings: opp/cpufreq: Convert ti-cpufreq to json schema Nishanth Menon
2023-08-09 2:30 ` [PATCH V3 1/2] dt-bindings: opp: Convert ti-omap5-opp-supply " Nishanth Menon
2023-08-09 4:48 ` Dhruva Gole
2023-08-09 11:40 ` Nishanth Menon
2023-08-09 2:30 ` [PATCH V3 2/2] dt-bindings: cpufreq: Convert ti-cpufreq " Nishanth Menon
2023-08-09 4:30 ` Dhruva Gole
2023-08-09 11:25 ` Nishanth Menon [this message]
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=20230809112548.cf5o7yxqeu3nfqdq@kobold \
--to=nm@ti.com \
--cc=bcousson@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tony@atomide.com \
--cc=vibhore@ti.com \
--cc=viresh.kumar@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