From: Sudeep Holla <sudeep.holla@arm.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/6] firmware: arm_scmi: add initial support for i.MX BBM protocol
Date: Tue, 9 Apr 2024 09:59:16 +0100 [thread overview]
Message-ID: <ZhUDZGJilhczKlDD@bogus> (raw)
In-Reply-To: <ZhQxu8LVNKf5QDLm@pluto>
On Mon, Apr 08, 2024 at 07:04:43PM +0100, Cristian Marussi wrote:
> On Fri, Apr 05, 2024 at 08:39:25PM +0800, Peng Fan (OSS) wrote:
> > From: Peng Fan <peng.fan@nxp.com>
> >
> > The i.MX BBM protocol is for managing i.MX BBM module which provides
> > RTC and BUTTON feature.
> >
>
> I appreciate that you added versioning but I think a bit of documentation
> about what the protocol and its comamnds purpose is still lacking, as asked
> by Sudeep previously
>
> https://lore.kernel.org/linux-arm-kernel/ZeGtoJ7ztSe8Kg8R@bogus/#t
>
I have decided to ignore all these vendor protocol patches until they have
some documentation to understand what these protocol are for, what are
the commands, their input/output parameter details, any conditions are the
caller and callee,..etc very similar to SCMI spec.
To start with can you please expand what is BBM or MISC protocol is ?
Don't expect me to respond if the requested details are still missing in
the future versions, I am going to ignore it silently.
I have asked for these in atleast 2 different threads may be not just NXP
patches but in one instance Qcom patches, but they apply equally here.
--
Regards,
Sudeep
next prev parent reply other threads:[~2024-04-09 8:59 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 12:39 [PATCH v2 0/6] firmware: support i.MX95 SCMI BBM/MISC Extenstion Peng Fan (OSS)
2024-04-05 12:39 ` [PATCH v2 1/6] dt-bindings: firmware: arm,scmi: set additionalProperties to true Peng Fan (OSS)
2024-04-06 10:57 ` Krzysztof Kozlowski
2024-04-07 0:37 ` Peng Fan
2024-04-07 8:55 ` Krzysztof Kozlowski
2024-04-07 10:04 ` Peng Fan
2024-04-07 16:15 ` Krzysztof Kozlowski
2024-04-07 23:50 ` Peng Fan
2024-04-08 5:57 ` Krzysztof Kozlowski
2024-04-08 6:08 ` Peng Fan
2024-04-08 7:18 ` Krzysztof Kozlowski
2024-04-08 7:23 ` Peng Fan
2024-04-09 9:25 ` Peng Fan
2024-04-09 12:01 ` Cristian Marussi
2024-04-09 14:09 ` Rob Herring
2024-04-09 14:56 ` Cristian Marussi
2024-04-11 1:50 ` Peng Fan
2024-04-05 12:39 ` [PATCH v2 2/6] dt-bindings: firmware: add i.MX SCMI Extension protocol Peng Fan (OSS)
2024-04-06 11:02 ` Krzysztof Kozlowski
2024-04-07 0:51 ` Peng Fan
2024-04-07 1:50 ` Peng Fan
2024-04-07 8:57 ` Krzysztof Kozlowski
2024-04-07 10:15 ` Peng Fan
2024-04-10 17:19 ` Rob Herring
2024-04-10 23:47 ` Peng Fan
2024-04-05 12:39 ` [PATCH v2 3/6] firmware: arm_scmi: add initial support for i.MX BBM protocol Peng Fan (OSS)
2024-04-08 18:04 ` Cristian Marussi
2024-04-08 23:35 ` Peng Fan
2024-04-09 8:59 ` Sudeep Holla [this message]
2024-04-09 9:13 ` Peng Fan
2024-04-09 10:49 ` Sudeep Holla
2024-04-09 11:19 ` Peng Fan
2024-04-09 12:52 ` Sudeep Holla
2024-04-09 13:01 ` Peng Fan
2024-04-05 12:39 ` [PATCH v2 4/6] firmware: arm_scmi: add initial support for i.MX MISC protocol Peng Fan (OSS)
2024-04-05 16:44 ` Marco Felsch
2024-04-07 1:03 ` Peng Fan
2024-04-07 11:02 ` Marco Felsch
2024-04-07 11:16 ` Peng Fan
2024-04-05 12:39 ` [PATCH v2 5/6] firmware: imx: support BBM module Peng Fan (OSS)
2024-04-05 12:39 ` [PATCH v2 6/6] firmware: imx: add i.MX95 MISC driver 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=ZhUDZGJilhczKlDD@bogus \
--to=sudeep.holla@arm.com \
--cc=conor+dt@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).