From: Peter Griffin <peter.griffin@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Tudor Ambarus <tudor.ambarus@linaro.org>,
Jassi Brar <jassisinghbrar@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, andre.draszik@linaro.org,
kernel-team@android.com, willmcvicker@google.com,
daniel.lezcano@linaro.org, vincent.guittot@linaro.org,
ulf.hansson@linaro.org, arnd@arndb.de
Subject: Re: [PATCH v5 1/3] dt-bindings: mailbox: add google,gs101-mbox
Date: Wed, 18 Dec 2024 11:23:38 +0000 [thread overview]
Message-ID: <CADrjBPq4mTsvCivBJPmADP3pfUORBV8hGeP5GrTg9YxASJLHXg@mail.gmail.com> (raw)
In-Reply-To: <wlvvuq2ldv4funye2ylnccq7soyrqkqggg36oimnvmhxbbjvnl@yyy4y5nyruzn>
Hi,
On Wed, 18 Dec 2024 at 09:29, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>
> On Tue, Dec 17, 2024 at 09:40:20AM +0000, Tudor Ambarus wrote:
> > +description: |
> > + The samsung exynos mailbox controller has 16 flag bits for hardware interrupt
>
> If there is going to be any new posting:
>
> The Samsung Exynos mailbox controller, used on Google GS101 SoC, ....
>
> > + generation and a shared register for passing mailbox messages. When the
> > + controller is used by the ACPM protocol the shared register is ignored and
> > + the mailbox controller acts as a doorbell. The controller just raises the
> > + interrupt to the firmware after the ACPM protocol has written the message to
> > + SRAM.
> > +
> > +properties:
> > + compatible:
> > + const: google,gs101-mbox
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + clocks:
> > + maxItems: 1
> > +
> > + clock-names:
> > + items:
> > + - const: pclk
> > +
> > + interrupts:
> > + description: IRQ line for the RX mailbox.
> > + maxItems: 1
> > +
> > + '#mbox-cells':
> > + description: |
> > + <&phandle type channel>
> > + phandle : label name of controller.
> > + type : channel type, doorbell or data-transfer.
> > + channel : channel number.
> > +
> > + Here is how a client can reference them:
> > + mboxes = <&ap2apm_mailbox DOORBELL 2>;
> > + mboxes = <&ap2apm_mailbox DATA 3>;
>
> This ordering assumes there is channel "2" in doorbel and in data, so
> two times "2" and of course the same for all others. If this is
> configuration of one channel, so "2" is either doorbell or data, then
> type should be the last.
My understanding was each channel is either configured for doorbell or
data, but Tudor can confirm. With Krzysztof's feedback addressed:
Reviewed-by: Peter Griffin <peter.griffin@linaro.org>
regards,
Peter.
next prev parent reply other threads:[~2024-12-18 11:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 9:40 [PATCH v5 0/3] mailbox: add Samsung Exynos driver Tudor Ambarus
2024-12-17 9:40 ` [PATCH v5 1/3] dt-bindings: mailbox: add google,gs101-mbox Tudor Ambarus
2024-12-18 9:29 ` Krzysztof Kozlowski
2024-12-18 11:23 ` Peter Griffin [this message]
2024-12-18 12:39 ` Tudor Ambarus
2024-12-19 10:50 ` Tudor Ambarus
2024-12-21 2:19 ` Jassi Brar
2024-12-21 6:45 ` Tudor Ambarus
2025-01-03 3:39 ` Jassi Brar
2025-01-03 9:57 ` Tudor Ambarus
2025-01-08 9:38 ` Tudor Ambarus
2025-01-12 16:59 ` Jassi Brar
2025-01-13 9:34 ` Tudor Ambarus
2025-01-13 16:52 ` Jassi Brar
2024-12-17 9:40 ` [PATCH v5 2/3] mailbox: add Samsung Exynos driver Tudor Ambarus
2024-12-18 10:20 ` Krzysztof Kozlowski
2024-12-18 11:58 ` Peter Griffin
2024-12-18 16:58 ` Jassi Brar
2024-12-17 9:40 ` [PATCH v5 3/3] MAINTAINERS: add entry for Samsung Exynos mailbox driver Tudor Ambarus
2024-12-18 10:20 ` Krzysztof Kozlowski
2024-12-18 11:08 ` Peter Griffin
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=CADrjBPq4mTsvCivBJPmADP3pfUORBV8hGeP5GrTg9YxASJLHXg@mail.gmail.com \
--to=peter.griffin@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=willmcvicker@google.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;
as well as URLs for NNTP newsgroup(s).