From: Sudeep Holla <sudeep.holla@arm.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
matthias.bgg@gmail.com, cristian.marussi@arm.com,
Sudeep Holla <sudeep.holla@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, arm-scmi@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v1 2/2] firmware: arm_scmi: Add MediaTek TinySYS SCMI Protocol support
Date: Mon, 23 Jun 2025 13:16:21 +0100 [thread overview]
Message-ID: <20250623-free-puzzling-wrasse-0fdb7e@sudeepholla> (raw)
In-Reply-To: <20250623120136.109311-3-angelogioacchino.delregno@collabora.com>
On Mon, Jun 23, 2025 at 02:01:36PM +0200, AngeloGioacchino Del Regno wrote:
> Add a driver for the SCMI protocol extensions for MediaTek TinySYS.
> This is used to communicate with various remote processors in some
> MediaTek SoCs, which mainly handle power management related tasks.
>
Please provide the detailed documentation for this vendor protocol/extension.
Refer drivers/firmware/arm_scmi/vendors/imx/imx95.rst for example.
It is hard to do any useful review without the detailed documentation.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-06-23 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 12:01 [PATCH v1 0/2] firmware: Add MediaTek TinySYS SCMI Protocol AngeloGioacchino Del Regno
2025-06-23 12:01 ` [PATCH v1 1/2] dt-bindings: firmware: Add MediaTek TinySYS SCMI Extension protocol AngeloGioacchino Del Regno
2025-06-27 10:19 ` Cristian Marussi
2025-06-27 20:14 ` Rob Herring
2025-06-23 12:01 ` [PATCH v1 2/2] firmware: arm_scmi: Add MediaTek TinySYS SCMI Protocol support AngeloGioacchino Del Regno
2025-06-23 12:16 ` Sudeep Holla [this message]
2025-06-24 3:01 ` Peng Fan
2025-06-27 8:20 ` kernel test robot
2025-06-27 11:43 ` Cristian Marussi
2025-06-23 12:17 ` [PATCH v1 0/2] firmware: Add MediaTek TinySYS SCMI Protocol Cristian Marussi
2025-06-23 12:32 ` AngeloGioacchino Del Regno
2025-06-23 13:30 ` 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=20250623-free-puzzling-wrasse-0fdb7e@sudeepholla \
--to=sudeep.holla@arm.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arm-scmi@vger.kernel.org \
--cc=conor+dt@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@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).