From: Dhruva Gole <d-gole@ti.com>
To: Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Vignesh Raghavendra <vigneshr@ti.com>, <linux-pm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Dhruva Gole <d-gole@ti.com>
Subject: [PATCH 0/2] dt-bindings: opp: operating-points-v2-ti-cpu: Describe opp-supported-hw
Date: Tue, 3 Sep 2024 16:00:06 +0530 [thread overview]
Message-ID: <20240903-b4-opp-dt-binding-fix-v1-0-f7e186456d9f@ti.com> (raw)
dt-bindings: opp: operating-points-v2-ti-cpu: Describe opp-supported-hw
This series tries to bring back the description about what goes into
opp-supported-hw from the older binding.
While at it, also updating the maintainers entry.
Signed-off-by: Dhruva Gole <d-gole@ti.com>
---
Dhruva Gole (2):
dt-bindings: opp: operating-points-v2-ti-cpu: Describe opp-supported-hw
dt-bindings: opp: operating-points-v2-ti-cpu: Update maintainers
.../devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
---
base-commit: ecc768a84f0b8e631986f9ade3118fa37852fef0
change-id: 20240903-b4-opp-dt-binding-fix-73c6829751d2
Best regards,
--
Dhruva Gole <d-gole@ti.com>
next reply other threads:[~2024-09-03 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 10:30 Dhruva Gole [this message]
2024-09-03 10:30 ` [PATCH 1/2] dt-bindings: opp: operating-points-v2-ti-cpu: Describe opp-supported-hw Dhruva Gole
2024-09-03 15:27 ` Rob Herring
2024-09-03 10:30 ` [PATCH 2/2] dt-bindings: opp: operating-points-v2-ti-cpu: Update maintainers Dhruva Gole
2024-09-03 15:27 ` Rob Herring (Arm)
2024-09-04 6:50 ` Viresh Kumar
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=20240903-b4-opp-dt-binding-fix-v1-0-f7e186456d9f@ti.com \
--to=d-gole@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=vigneshr@ti.com \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@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;
as well as URLs for NNTP newsgroup(s).