From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: <stefank@nvidia.com>, <thierry.reding@gmail.com>, <jonathanh@nvidia.com>
Cc: <jassisinghbrar@gmail.com>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v2 0/6] firmware: tegra: Add MRQ support for Tegra264.
Date: Wed, 10 May 2023 14:44:02 +0300 [thread overview]
Message-ID: <ZFuDgmLXmTs91FqI@44189d9-lcedt> (raw)
In-Reply-To: <20230510113129.4167493-1-pdeschrijver@nvidia.com>
On Wed, May 10, 2023 at 02:31:24PM +0300, Peter De Schrijver wrote:
> In Tegra264 the carveouts (GSCs) used to communicate between BPMP and
> CPU-NS may reside in DRAM. The location will be signalled using reserved
> memory node in DT. Additionally some minor updates to the HSP driver are
> done to support the new chip.
>
> Peter De Schrijver (4):
> dt-bindings: mailbox: tegra: Document Tegra264 HSP
> dt-bindings: Add bindings to support DRAM MRQ GSCs
> dt-bindings: memory-region property for tegra186-bpmp
> firmware: tegra: bpmp: Add support for DRAM MRQ GSCs
>
> Stefan Kristiansson (2):
> mailbox: tegra: add support for Tegra264
> soc: tegra: fuse: add support for Tegra264
Changes in v2:
- Added signoff messages
- Updated bindings to support DRAM MRQ GSCs
- Split out memory-region property for tegra186-bpmp
- Addressed sparse errors in bpmp-tegra186.c
prev parent reply other threads:[~2023-05-10 11:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 11:31 [PATCH v2 0/6] firmware: tegra: Add MRQ support for Tegra264 Peter De Schrijver
2023-05-10 11:31 ` [PATCH v2 1/6] dt-bindings: mailbox: tegra: Document Tegra264 HSP Peter De Schrijver
2023-05-10 13:50 ` Thierry Reding
2023-05-10 11:31 ` [PATCH v2 2/6] mailbox: tegra: add support for Tegra264 Peter De Schrijver
2023-05-10 13:50 ` Thierry Reding
2023-05-10 11:31 ` [PATCH v2 3/6] soc: tegra: fuse: " Peter De Schrijver
2023-05-10 14:35 ` Thierry Reding
2023-05-10 11:31 ` [PATCH v2 4/6] dt-bindings: Add bindings to support DRAM MRQ GSCs Peter De Schrijver
2023-05-10 12:47 ` Krzysztof Kozlowski
2023-05-10 11:31 ` [PATCH v2 5/6] dt-bindings: memory-region property for tegra186-bpmp Peter De Schrijver
2023-05-10 14:40 ` Thierry Reding
2023-05-10 11:31 ` [PATCH v2 6/6] firmware: tegra: bpmp: Add support for DRAM MRQ GSCs Peter De Schrijver
2023-05-10 14:33 ` Thierry Reding
2023-05-11 8:04 ` Peter De Schrijver
2023-05-10 11:44 ` Peter De Schrijver [this message]
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=ZFuDgmLXmTs91FqI@44189d9-lcedt \
--to=pdeschrijver@nvidia.com \
--cc=jassisinghbrar@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=stefank@nvidia.com \
--cc=thierry.reding@gmail.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.