All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	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: Thu, 19 Mar 2026 09:58:16 +0100	[thread overview]
Message-ID: <c46357c9-8cf4-45ec-8b48-8cf979de2e98@kernel.org> (raw)
In-Reply-To: <CAMuHMdX=DRnFWG1ky8wT7mK=LHeJ6LduL28nYd19QpASrn6mew@mail.gmail.com>

On 19/03/2026 09:54, Geert Uytterhoeven wrote:
>>
>>> +
>>> +/*
>>> + * MFIS variants before r8a78001 work with pairs of IICR and EICR registers.
>>> + * Usually, it is specified in the datasheets which of the two a specific core
>>> + * should use. Then, it does not need extra description in DT. For plain MFIS
>>> + * of r8a78000, this is selectable, though. According to the system design and
>>> + * the firmware in use, these channels need to be marked. This is not needed
>>> + * with other versions of the MFIS, not even with MFIS-SCP of r8a78000.
>>> + */
>>> +#define MFIS_CHANNEL_IICR    (0 << 1)
>>> +#define MFIS_CHANNEL_EICR    (1 << 1)
>>
>> Same here.
> 
> These are flags as the documentation for the #mbox-cells property in the
> bindings file states, to be ORed.

I did not get the driver so I cannot verify that. What sort of Linux ABI
does this bind?

Best regards,
Krzysztof

  reply	other threads:[~2026-03-19  8:58 UTC|newest]

Thread overview: 36+ 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 [this message]
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
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
2026-03-17 13:06 ` [PATCH 2/3] soc: renesas: Add Renesas R-Car MFIS driver Wolfram Sang
2026-03-19 12:58   ` Geert Uytterhoeven
2026-03-22 19:58     ` Wolfram Sang
2026-03-23  8:12       ` Geert Uytterhoeven
2026-03-23  9:29         ` Wolfram Sang
2026-03-23 10:06           ` Geert Uytterhoeven
2026-03-22  8:59   ` Sashiko review feedback (was Re: [PATCH 2/3] soc: renesas: Add Renesas R-Car MFIS driver) Wolfram Sang
2026-03-23 10:02     ` Geert Uytterhoeven
2026-03-23 10:58       ` Wolfram Sang
2026-03-24  2:21     ` Roman Gushchin
2026-03-24  6:18       ` Wolfram Sang
2026-03-24 14:54         ` Roman Gushchin
2026-03-30  8:57           ` Wolfram Sang
2026-03-30 13:50             ` Theodore Tso
2026-03-31  7:18               ` Wolfram Sang
2026-03-31  7:44                 ` Geert Uytterhoeven
2026-03-31  7:53                   ` Wolfram Sang
2026-03-29 17:05   ` [PATCH 2/3] soc: renesas: Add Renesas R-Car MFIS driver Jassi Brar
2026-03-31  9:03     ` Wolfram Sang
2026-03-17 13:06 ` [PATCH 3/3] soc: renesas: add X5H PRR support Wolfram Sang
2026-03-19  9:04   ` 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=c46357c9-8cf4-45ec-8b48-8cf979de2e98@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.