Received-SPF: pass (google.com: domain of linux-kernel+bounces-136529-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
From: Peng Fan <peng.fan@nxp.com>
To: Sudeep Holla <sudeep.holla@arm.com>, "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>, "devicetree@vger.kernel.org"
	<devicetree@vger.kernel.org>, "imx@lists.linux.dev" <imx@lists.linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>, "linux-kernel@vger.kernel.org"
	<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 3/6] firmware: arm_scmi: add initial support for i.MX
 BBM protocol
Thread-Topic: [PATCH v2 3/6] firmware: arm_scmi: add initial support for i.MX
 BBM protocol
Thread-Index: AQHah1U7U7PbHuwUVkuCiXWcSbaKerFer8yAgAD57wCAAACBQA==
Date: Tue, 9 Apr 2024 09:13:33 +0000
Message-ID:
 <DU0PR04MB94175384AD9113AC6F60546588072@DU0PR04MB9417.eurprd04.prod.outlook.com>
References: <20240405-imx95-bbm-misc-v2-v2-0-9fc9186856c2@nxp.com>
 <20240405-imx95-bbm-misc-v2-v2-3-9fc9186856c2@nxp.com>
 <ZhQxu8LVNKf5QDLm@pluto> <ZhUDZGJilhczKlDD@bogus>
In-Reply-To: <ZhUDZGJilhczKlDD@bogus>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0:
 =?us-ascii?Q?w5yWex9aDsSVsc23kZDRYLRJBnMWNELV8NBxnoxa7uKVoBRIpDQRIxjQQxMM?=
 =?us-ascii?Q?HRWhIiv+0csoaJh5WcQXorcVdqK35MlsrCHPHwG7W61E8iMU9O1+i1O+PXg1?=
 =?us-ascii?Q?rzlYbpgBPp/m7OXAI3FMp21qx6zGKTsPKpeVku81x1k23Hz/LGxqCl1wy3Wx?=
 =?us-ascii?Q?awwDZxUjhIuDc+GUnIyajvMUoJpovZ0j0rog5ive6ufp3ilt/fm7eH75l9wb?=
 =?us-ascii?Q?a6HWx0VXmEXEfCdqNvYdWq5tuhIB2tFj/Jz6Tg1oFG+0uDSsE4v3xNInJnah?=
 =?us-ascii?Q?fNMq7kuyFBpm+MhInpXOnkHei4HSb4nSu782x1sZSpKYhTqre6H75WrYfEdf?=
 =?us-ascii?Q?+ag8Lsir6ea9ielh1M3X8ehVwuCqdljBTr0Z8owUZ0p6S65UIix0nIgW9Tpf?=
 =?us-ascii?Q?dOrynAl75RHMPeqCe6pci29YeuSTaVgjckBCnFhiuzpD+TqbMIbhD2v2I8c1?=
 =?us-ascii?Q?fvZB8jMGUW77CPyGMC0Cc+pKeSIVGs6RU1yh1EsqYtk2EMsm+xpb2gcreNVU?=
 =?us-ascii?Q?n7TrIH8w5oBITqtO3NjhlDlT56x2om+hHd347KlKZ5Kz1clCRRxnnoE78pq8?=
 =?us-ascii?Q?Nzz0RvlNpEsxyC2IvIp0fqKK3C188Y33wFrZIFAiYjyVoi22JRCof/age9aE?=
 =?us-ascii?Q?nsNuWig1e/Ty9Kjw2sf532XKDb6nbkLclMoYHzJw70gKFDwKZiVrKiJPRc1E?=
 =?us-ascii?Q?q6/+Xx6PtylwWL89XL8y8/qyIF7TA5g5VQ3nVlB5yfhQrbXBRX7mDO52C2TD?=
 =?us-ascii?Q?T4hZ7wrUqz4JTHqqrrLtdUnIfY22L8h9ShxF+JPnsbRIEBDuGGr3XsWZZdTX?=
 =?us-ascii?Q?A/u1t04RFyKBnIP2qGrEYg3zaDyjizDyU9KTrIck9CVUWxuQQXRJZt0gMABs?=
 =?us-ascii?Q?XaCYWIllvz3UftHCsIZmg4NiMx5QaAeYcPHcIOUWCtT0iXeRCDdm71Ik5V3p?=
 =?us-ascii?Q?FLu91JztArvgG4DpHv6h7r2+74ARn5bmSZQtHZu6SWREcdlrnpDCuAyaAmWI?=
 =?us-ascii?Q?yLlh2QGkHRLmURhyMoh8Q8hqrElMkjuhrVGMWk5dTEC/0HUGc9O1lf2C65oV?=
 =?us-ascii?Q?Chv2PcJnyQDuune4rUu7WRD3mmc9lDGJSAUCpq82ZbI8it/gMWKy8ZKEWalN?=
 =?us-ascii?Q?jDLSR95LuH2GG59xMBgddSu/bi//evs/3RSsIXDecugDR+F30K6r+A3J8Y1o?=
 =?us-ascii?Q?e3EABQ1u7jrl17RdUfg4mS+Kd2FBktMxkDhguBaYDGXFiQiUBnjRL/zzwkRd?=
 =?us-ascii?Q?95BEtaNCVTOH+LNvfcCLmogn3S6H8LEW/V97JSS+2mPYHpo78N5GAhikNPoF?=
 =?us-ascii?Q?Bklesybr9lRNhPSslb1MhtwcAmSp53pNXfdwIr0lSPtR6lbYTEHuHJVZWXFr?=
 =?us-ascii?Q?Gfj+zaL+6z4Nnq7Pg7rM3DzuPGk9MbDDVG+rBk6Pgn17fJQrKkVmuuEjqj0L?=
 =?us-ascii?Q?M6HmvLt29Ml1YbKhp0uuLHxwxvSnGbRVDJbPSd6VTa9f0D72olgDVHMWiX+s?=
 =?us-ascii?Q?oIIxOIov37dWDC6AVGzo1YIk3F/uztrF9PK/Hov8/Sdj3hbNZ47xtd/mV6fW?=
 =?us-ascii?Q?Bgd4xyCuf6gsY3S+r2Q=3D?=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
X-OriginatorOrg: nxp.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DU0PR04MB9417.eurprd04.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7d8ca76e-9c4d-4f74-7b45-08dc587554a1
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Apr 2024 09:13:33.3588
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Aj2mM2JNB+sOTnTMZ0+D+JLj4uhWn+VeG7v/iCR2Z0DcDzYz+/GvX503GfOYnqPj2vVQeVaADpH9WhCs4687gw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AS8PR04MB8721

Hi Sudeep,

> Subject: Re: [PATCH v2 3/6] firmware: arm_scmi: add initial support for i=
MX
> BBM protocol
>=20
> 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://eur01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Flor=
e
> > .kernel.org%2Flinux-arm-
> kernel%2FZeGtoJ7ztSe8Kg8R%40bogus%2F%23t&data=3D
> >
> 05%7C02%7Cpeng.fan%40nxp.com%7Ce92ff78b9126447afe9708dc587358d
> 4%7C686e
> >
> a1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C638482499632395762%7C
> Unknown%7C
> >
> TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiL
> CJXVC
> >
> I6Mn0%3D%7C0%7C%7C%7C&sdata=3D7QP%2BkkjHA3Sa0CdcbbObGG4kgYYK
> XAGA2r%2F%2F
> > x0MogqU%3D&reserved=3D0
> >
>=20
> I have decided to ignore all these vendor protocol patches until they hav=
e
> some documentation to understand what these protocol are for, what are th=
e
> commands, their input/output parameter details, any conditions are the
> caller and callee,..etc very similar to SCMI spec.

Where do you expect the documentation to be put?

similar as scmi_protocol.h, put in scmi_imx_protcol.h?=20
>=20
> To start with can you please expand what is BBM or MISC protocol is ?

ok. Sorry for missing your previous comment in v1. Let me write here briefl=
y
first.

The Battery Backup (BB) Domain contains the Battery Backed Security
Module (BBSM) and the Battery Backed Non-Secure Module (BBNSM).
BBM protocol is to manage i.MX BBSM and BBNSM. This protocol supports
#define COMMAND_PROTOCOL_VERSION             0x0U                          =
                        =20
#define COMMAND_PROTOCOL_ATTRIBUTES          0x1U                          =
                        =20
#define COMMAND_PROTOCOL_MESSAGE_ATTRIBUTES  0x2U                          =
                        =20
#define COMMAND_BBM_GPR_SET                  0x3U                          =
                        =20
#define COMMAND_BBM_GPR_GET                  0x4U                          =
                        =20
#define COMMAND_BBM_RTC_ATTRIBUTES           0x5U                          =
                        =20
#define COMMAND_BBM_RTC_TIME_SET             0x6U                          =
                        =20
#define COMMAND_BBM_RTC_TIME_GET             0x7U                          =
                        =20
#define COMMAND_BBM_RTC_ALARM_SET            0x8U                          =
                        =20
#define COMMAND_BBM_BUTTON_GET               0x9U                          =
                        =20
#define COMMAND_BBM_RTC_NOTIFY               0xAU                          =
                        =20
#define COMMAND_BBM_BUTTON_NOTIFY            0xBU                          =
                        =20
#define COMMAND_NEGOTIATE_PROTOCOL_VERSION   0x10U

For now in this patchset for linux, we only use RTC, and BUTTON
for system wakeup

For MISC protocol, it is for various misc things, such as discover
build info, get rom passed data, get reset reason, get i.mx
cfg name, control set(for gpio expander under m33 control and
etc). The command as below:
51 #define COMMAND_PROTOCOL_VERSION             0x0U                       =
                           =20
  52 #define COMMAND_PROTOCOL_ATTRIBUTES          0x1U                     =
                             =20
  53 #define COMMAND_PROTOCOL_MESSAGE_ATTRIBUTES  0x2U                     =
                             =20
  54 #define COMMAND_MISC_CONTROL_SET             0x3U                     =
                             =20
  55 #define COMMAND_MISC_CONTROL_GET             0x4U                     =
                             =20
  56 #define COMMAND_MISC_CONTROL_ACTION          0x5U                     =
                             =20
  57 #define COMMAND_MISC_DISCOVER_BUILD_INFO     0x6U                     =
                             =20
  58 #define COMMAND_MISC_ROM_PASSOVER_GET        0x7U                     =
                             =20
  59 #define COMMAND_MISC_CONTROL_NOTIFY          0x8U                     =
                             =20
  60 #define COMMAND_MISC_REASON_ATTRIBUTES       0x9U                     =
                             =20
  61 #define COMMAND_MISC_RESET_REASON            0xAU                     =
                             =20
  62 #define COMMAND_MISC_SI_INFO                 0xBU                     =
                             =20
  63 #define COMMAND_MISC_CFG_INFO                0xCU                     =
                             =20
  64 #define COMMAND_MISC_SYSLOG                  0xDU                     =
                             =20
  65 #define COMMAND_NEGOTIATE_PROTOCOL_VERSION   0x10U

I will add the information in v3.

But as of now I am not sure
how to proceed with dt-binding, add in vendor stuff
in arm,scmi.yaml or add imx,scmi.yaml

Thanks,
Peng.

> Don't expect me to respond if the requested details are still missing in =
the
> future versions, I am going to ignore it silently.
>=20
> 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.
>=20
> --
> Regards,
> Sudeep