From: Stephen Boyd <sboyd@kernel.org>
To: Jacky Bai <ping.bai@nxp.com>,
cristian.marussi@arm.com, mturquette@baylibre.com,
sudeep.holla@arm.com
Cc: arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-clk@vger.kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH] clk: scmi: Add duty cycle ops only when duty cycle is supported
Date: Fri, 19 Sep 2025 22:50:37 -0700 [thread overview]
Message-ID: <175834743791.4354.15798053146130121164@lazor> (raw)
In-Reply-To: <20250728070446.949095-1-ping.bai@nxp.com>
Quoting Jacky Bai (2025-07-28 00:04:46)
> For some of the SCMI based platforms, the oem extended config may be
> supported, but not for duty cycle purpose. Skip the duty cycle ops if
> err return when trying to get duty cycle info.
>
> Signed-off-by: Jacky Bai <ping.bai@nxp.com>
> ---
Applied to clk-next
prev parent reply other threads:[~2025-09-20 5:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 7:04 [PATCH] clk: scmi: Add duty cycle ops only when duty cycle is supported Jacky Bai
2025-08-19 11:02 ` Sudeep Holla
2025-09-20 5:50 ` Stephen Boyd [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=175834743791.4354.15798053146130121164@lazor \
--to=sboyd@kernel.org \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=imx@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=ping.bai@nxp.com \
--cc=sudeep.holla@arm.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