From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH v2 0/2] firmware: arm_scmi: clock: support parents commands
Date: Mon, 25 Sep 2023 16:47:41 +0800 [thread overview]
Message-ID: <20230925-scmi-clock-v2-v2-0-2d4d7127ebc1@nxp.com> (raw)
V2:
Add determine_rate hooks
SCMI v3.2 spec adds parents commands, this patchset is to support them:
CLOCK_POSSIBLE_PARENTS_GET
CLOCK_PARENT_SET
CLOCK_PARENT_GET
Besides firmware api clock driver update, the clk_scmi driver also
updated to support set_parent and get_parent ops.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
Peng Fan (2):
firmware: arm_scmi: clock: support clock parents
clk: scmi: add set/get_parent support
drivers/clk/clk-scmi.c | 50 +++++++++++-
drivers/firmware/arm_scmi/clock.c | 156 ++++++++++++++++++++++++++++++++++++--
include/linux/scmi_protocol.h | 5 ++
3 files changed, 204 insertions(+), 7 deletions(-)
---
base-commit: 8fff9184d1b5810dca5dd1a02726d4f844af88fc
change-id: 20230925-scmi-clock-v2-042cf8e5cb77
Best regards,
--
Peng Fan <peng.fan@nxp.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-09-25 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 8:47 Peng Fan (OSS) [this message]
2023-09-25 8:47 ` [PATCH v2 1/2] firmware: arm_scmi: clock: support clock parents Peng Fan (OSS)
2023-09-27 16:33 ` Cristian Marussi
2023-09-25 8:47 ` [PATCH v2 2/2] clk: scmi: add set/get_parent support Peng Fan (OSS)
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=20230925-scmi-clock-v2-v2-0-2d4d7127ebc1@nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=sboyd@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).