public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jassi Brar <jassisinghbrar@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: soc: renesas: add MFIS binding documentation
Date: Tue, 31 Mar 2026 09:52:13 +0200	[thread overview]
Message-ID: <3915fd13-1b0b-4faf-81f2-0acb97880766@kernel.org> (raw)
In-Reply-To: <act6gTgkYE6Az5hK@shikoro>

On 31/03/2026 09:40, Wolfram Sang wrote:
> 
>>> 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
>>
>> 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

DT, but we talk about bindings. Bindings is not DT. Bindings bind the SW
and DTS.

> agnostic. So, the flags are to describe the hardware. The Linux driver

Well, then no. Bindings headers do not describe the hardware.


> then does the proper things according to these flags. Other OS driver
> might do other things.
> 
>>> shifts instead of plain numbers):
>>>
>>> include/dt-bindings/mailbox/tegra186-hsp.h
> 
> And I still have no idea why my header is different than the Tegra one.
> 

No clue what is there. I am not going even to investigate, because this
is argument of "I found a bug somewhere, so I can implement same bug".

I responded to this *MULTIPLE* times already on the lists. I explained
the rationale, I even provided old messages from Arnd and other people.

Best regards,
Krzysztof

  reply	other threads:[~2026-03-31  7:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 13:06 [PATCH 0/3] soc: renesas: add MFIS driver Wolfram Sang
2026-03-17 13:06 ` [PATCH 1/3] dt-bindings: soc: renesas: add MFIS binding documentation Wolfram Sang
2026-03-18  9:17   ` Krzysztof Kozlowski
2026-03-18  9:19     ` Krzysztof Kozlowski
2026-03-19  8:54     ` Geert Uytterhoeven
2026-03-19  8:58       ` Krzysztof Kozlowski
2026-03-31  7:10         ` Wolfram Sang
2026-03-31  7:14           ` Krzysztof Kozlowski
2026-03-31  7:40             ` Wolfram Sang
2026-03-31  7:52               ` Krzysztof Kozlowski [this message]
2026-03-31  7:18           ` Krzysztof Kozlowski
2026-03-31  7:33             ` Wolfram Sang
2026-03-19  9:15     ` Wolfram Sang
2026-03-18  9:17   ` Krzysztof Kozlowski
2026-03-19  8:58   ` Geert Uytterhoeven

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=3915fd13-1b0b-4faf-81f2-0acb97880766@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=robh@kernel.org \
    --cc=wsa+renesas@sang-engineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox