From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DCEA53C9EE2 for ; Tue, 31 Mar 2026 07:40:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774942855; cv=none; b=QpG+PrwemBTGZfQb0CtrmiYtcgGl6ta1/KrVEwJH1K9BNIzz2X0/JZuvic0xgIYB9XEWm4X1XjXnm0gne4k+Jp4EjxQFoJyf72E0rTZH9lfp92PcSDIMNmAZW+suCYwp8c+KxpYcN9yHzdcG/hzHCQcMJxE8LRkZCSpjgYLgdeY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774942855; c=relaxed/simple; bh=mxJa4OnZPZQ4isZ3ivPlpL7XmqxbvJctjnvIPc+Fj3w=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=qkhr3QDvoVrRQ/Fup6iaOwgYu4FPjhw4GQue59ZKTggDLJhh+KtiUa57wbjtsg11gOWQ4/9fI+LB0T2nUg05G+9SiKwDdEHW2fSoGNQ7yjX4aSkloFsbxuTgpWM4b7ydbfK434AdUDmsa+JdbckU619+++GEE5yBvTGMNccMx0Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=dqIJETCH; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="dqIJETCH" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=k1; bh=dBDL mmVEXCJX6ppu/jfbo13ZIge5FZycIk9NKQr8cSY=; b=dqIJETCHGpcK9LGT8iDv AzhxEv6BiOW/TE6/U+Eew4mOzrWnXWxqrX1RS4rGDcUjVttO19bkmanmzeV00wIq t04IIvLlqFPLWqDLS9ZrZtxkpzzugea3oYNX2YRNzdrLeRmpj2POMe/WAOfvH8fT 6UcxddCZzKhqqRQY8pXgqN6wFNmaSGbY/vafn+CIyAWpgrnpgMwv9wenM4FS9jbh MjnE7SykQwcX5ewpZNzgnMT8buj15dxX5cv14K8Hdth3QzdHGuzepinQu+Nq5kBZ n7E3/goLYGIKjLVxKArHuqIZZxkxbJFBgiGerP2JmS78dOFGXu6cxj7dB/2pqF+n 8g== Received: (qmail 1589924 invoked from network); 31 Mar 2026 09:40:49 +0200 Received: by mail.zeus03.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 31 Mar 2026 09:40:49 +0200 X-UD-Smtp-Session: l3s3148p1@scQEFk1Ols4ujnu8 Date: Tue, 31 Mar 2026 09:40:49 +0200 From: Wolfram Sang To: Krzysztof Kozlowski Cc: Geert Uytterhoeven , linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org, Jassi Brar , Geert Uytterhoeven , Magnus Damm , Rob Herring , Krzysztof Kozlowski , Conor Dooley , devicetree@vger.kernel.org Subject: Re: [PATCH 1/3] dt-bindings: soc: renesas: add MFIS binding documentation Message-ID: References: <20260317130638.2804-1-wsa+renesas@sang-engineering.com> <20260317130638.2804-2-wsa+renesas@sang-engineering.com> <20260318-camouflaged-umber-oxpecker-b2b29e@quoll> <8988012f-b006-4aa8-bb8f-571b8526a15c@kernel.org> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="YS1M1StTrmdXNQ1e" Content-Disposition: inline In-Reply-To: <8988012f-b006-4aa8-bb8f-571b8526a15c@kernel.org> --YS1M1StTrmdXNQ1e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > > In case you mean this as unanswered questions to v1: This describes the > > device specific second mbox cell. Like Tegra does it here (even with >=20 > I asked Linux ABI. Device specific numbers is not Linux ABI, because > Linux is not device. I have no idea what you want here. I see it like this: DT is OS agnostic. So, the flags are to describe the hardware. The Linux driver then does the proper things according to these flags. Other OS driver might do other things. > > shifts instead of plain numbers): > >=20 > > include/dt-bindings/mailbox/tegra186-hsp.h And I still have no idea why my header is different than the Tegra one. > > I really have no idea what is still missing? >=20 > It's not a binding, drop the header from the bindings. So, I should add the header to the driver? Can do, but then I have to remove the reference to the header from the binding doc. Namely, this paragraph: + The first cell is the channel number as specified in the documentati= on + of the SoC. The second cell may specify flags as described in the fi= le + . Not helpful for the user, or? --YS1M1StTrmdXNQ1e Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAmnLen0ACgkQFA3kzBSg KbZ2pxAAhcWDq2zcakZq3ltjpX1rLg+FBVpPX7VgyIyUWSN/TU7jVHmSMmyoyK3c l2p7RkWLDei1LFBw1XcLevI8Y9jktic3o2TgU+7XuDBdyFRn41TWc5HVN0eZ4ZMT +OkBSfu7QdFx3RjSbcRUa6DYd3PJhQVBLtadFaLTfKRkkOI5RWw/VyZnihtxmB+/ 0niYY6xbVpm6jFucqs6bMfT0hI4UnUQIeev0CJCYi9ot5y5g51ZvWorDuou40j0C opOQyc4lCTGTExeGRNP4C0nC/aYiLkchRWNk/NdIrhteyA+yolf8ci0ejZdMiB2T /exSgjcrceNsQSqnTjsNFM+K4T8RYQGvrdj9f4SGKHthCb/QWZghbw0vv7gjLe8C FVuX21o4wJZKTeKOmc5eJkrmcaczqTeqW6cbnhhpb+fwZvOTLgVOS9XpJI8x7mrC 4klcGaE1J4aJTwvd8BWpov2SB5N82TvVIJY6G0aczsyX0uqDMt2kZwO73LjbeS5s emfcaREnFSjU8dE6CiUD3U8Wvt5FXdpbmH9FS1gYCSC/zT9fWV+Cu7TTT5r6GMmm 5/NNx5QSpOc0VnilygBswrWpaN0oU4f4pJmVw5tYT67DvNniEPRwTARJr1miPA4I 59Y3Nktofj1ZT1cfbfFaT7Z9r2QFRvo/TsNQzzGCTzr/YiP5QGU= =z5US -----END PGP SIGNATURE----- --YS1M1StTrmdXNQ1e--