From: Cristian Marussi <cristian.marussi@arm.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH v3 1/2] firmware: arm_scmi: clock: support clock parents
Date: Mon, 2 Oct 2023 18:13:08 +0100 [thread overview]
Message-ID: <ZRr6JKR4uizvulcV@pluto> (raw)
In-Reply-To: <20231001-scmi-clock-v2-v3-1-898bd92d8939@nxp.com>
On Sun, Oct 01, 2023 at 12:38:43PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> SCMI v3.2 spec introduces CLOCK_POSSIBLE_PARENTS_GET, CLOCK_PARENT_SET
> and CLOCK_PARENT_GET. This patch is to add the upper three new
> commands.
>
Hi,
I tested this on some emulated setup and it works fine, can see well
formed SCMI messages going back and forth.
Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>
Thanks,
Cristian
WARNING: multiple messages have this Message-ID (diff)
From: Cristian Marussi <cristian.marussi@arm.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH v3 1/2] firmware: arm_scmi: clock: support clock parents
Date: Mon, 2 Oct 2023 18:13:08 +0100 [thread overview]
Message-ID: <ZRr6JKR4uizvulcV@pluto> (raw)
In-Reply-To: <20231001-scmi-clock-v2-v3-1-898bd92d8939@nxp.com>
On Sun, Oct 01, 2023 at 12:38:43PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> SCMI v3.2 spec introduces CLOCK_POSSIBLE_PARENTS_GET, CLOCK_PARENT_SET
> and CLOCK_PARENT_GET. This patch is to add the upper three new
> commands.
>
Hi,
I tested this on some emulated setup and it works fine, can see well
formed SCMI messages going back and forth.
Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>
Thanks,
Cristian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-02 17:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 4:38 [PATCH v3 0/2] firmware: arm_scmi: clock: support parents commands Peng Fan (OSS)
2023-10-01 4:38 ` Peng Fan (OSS)
2023-10-01 4:38 ` [PATCH v3 1/2] firmware: arm_scmi: clock: support clock parents Peng Fan (OSS)
2023-10-01 4:38 ` Peng Fan (OSS)
2023-10-02 17:13 ` Cristian Marussi [this message]
2023-10-02 17:13 ` Cristian Marussi
2023-10-02 18:52 ` Sudeep Holla
2023-10-02 18:52 ` Sudeep Holla
2023-10-01 4:38 ` [PATCH v3 2/2] clk: scmi: add set/get_parent support Peng Fan (OSS)
2023-10-01 4:38 ` Peng Fan (OSS)
2023-10-02 16:23 ` Sudeep Holla
2023-10-02 16:23 ` Sudeep Holla
2023-10-02 17:57 ` Cristian Marussi
2023-10-02 17:57 ` Cristian Marussi
2023-10-03 9:45 ` Peng Fan
2023-10-03 9:45 ` Peng Fan
2023-10-02 17:11 ` [PATCH v3 0/2] firmware: arm_scmi: clock: support parents commands Cristian Marussi
2023-10-02 17:11 ` Cristian Marussi
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=ZRr6JKR4uizvulcV@pluto \
--to=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=peng.fan@oss.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.