From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: <stefank@nvidia.com>, <thierry.reding@gmail.com>, <jonathanh@nvidia.com>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
"Joe Perches" <joe@perches.com>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>,
Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH v5 2/5] mailbox: tegra: add support for Tegra264
Date: Tue, 20 Jun 2023 16:12:47 +0300 [thread overview]
Message-ID: <ZJGlz7AoaZ6YB095@44189d9-lcedt> (raw)
In-Reply-To: <20230529135044.2746339-3-pdeschrijver@nvidia.com>
Ping! Jassi, any objections?
On Mon, May 29, 2023 at 04:50:45PM +0300, Peter De Schrijver wrote:
> From: Stefan Kristiansson <stefank@nvidia.com>
>
> Tegra264 has a slightly different doorbell register layout than
> previous chips.
>
> Acked-by: Thierry Reding <treding@nvidia.com>
> Signed-off-by: Stefan Kristiansson <stefank@nvidia.com>
> Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
> ---
> drivers/mailbox/tegra-hsp.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
Thanks,
Peter.
next prev parent reply other threads:[~2023-06-20 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 13:50 [PATCH v5 0/5] firmware: tegra: Add MRQ support for Tegra264 Peter De Schrijver
2023-05-29 13:50 ` [PATCH v5 1/5] dt-bindings: mailbox: tegra: Document Tegra264 HSP Peter De Schrijver
2023-05-29 13:50 ` [PATCH v5 2/5] mailbox: tegra: add support for Tegra264 Peter De Schrijver
2023-06-20 13:12 ` Peter De Schrijver [this message]
2023-06-20 15:08 ` Jassi Brar
2023-06-21 12:06 ` Peter De Schrijver
2023-05-29 13:50 ` [PATCH v5 3/5] dt-bindings: reserved-memory: Add support for DRAM MRQ GSCs Peter De Schrijver
2023-05-29 13:50 ` [PATCH v5 4/5] dt-bindings: firmware: Add support for tegra186-bpmp " Peter De Schrijver
2023-05-29 13:50 ` [PATCH v5 5/5] firmware: tegra: bpmp: Add support for " Peter De Schrijver
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=ZJGlz7AoaZ6YB095@44189d9-lcedt \
--to=pdeschrijver@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=joe@perches.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=stefank@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.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).