From: Kartik <kkartik@nvidia.com>
To: <jassisinghbrar@gmail.com>
Cc: <devicetree@vger.kernel.org>, <jonathanh@nvidia.com>,
<krzk+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <robh+dt@kernel.org>,
<thierry.reding@gmail.com>, <kkartik@nvidia.com>
Subject: Re: [PATCH 0/3] Add 128-bit support mailbox for Tegra234 chips
Date: Thu, 30 Jun 2022 00:26:27 +0530 [thread overview]
Message-ID: <1656528987-29280-1-git-send-email-kkartik@nvidia.com> (raw)
In-Reply-To: <1649921757-16919-1-git-send-email-kkartik@nvidia.com>
On 14/04/2022 13:05 +530, Kartik Wrote:
> This series of patches adds support for 128-bit shared mailbox found
> on Tegra234 chips. It also introduce tegra_hsp_sm_ops to abstract
> send & receive APIs for 32-bit and 128-bit shared mailboxes.
>
> Kartik (3):
> mailbox: tegra-hsp: Add tegra_hsp_sm_ops
> dt-bindings: tegra186-hsp: add type for shared mailboxes
> mailbox: tegra-hsp: Add 128-bit shared mailbox support
>
> .../bindings/mailbox/nvidia,tegra186-hsp.yaml | 9 ++
> drivers/mailbox/tegra-hsp.c | 149 ++++++++++++++----
> include/dt-bindings/mailbox/tegra186-hsp.h | 5 +
> 3 files changed, 134 insertions(+), 29 deletions(-)
Hi Jassi,
Any comments on this from the mailbox side?
Regards,
Kartik
next prev parent reply other threads:[~2022-06-29 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 7:35 [PATCH 0/3] Add 128-bit support mailbox for Tegra234 chips Kartik
2022-04-14 7:35 ` [PATCH 1/3] mailbox: tegra-hsp: Add tegra_hsp_sm_ops Kartik
2022-04-14 7:35 ` [PATCH 2/3] dt-bindings: tegra186-hsp: add type for shared mailboxes Kartik
2022-04-14 13:53 ` Rob Herring
2022-04-18 11:01 ` Kartik
2022-04-20 19:55 ` Rob Herring
2022-04-14 7:35 ` [PATCH 3/3] mailbox: tegra-hsp: Add 128-bit shared mailbox support Kartik
2022-06-29 18:56 ` Kartik [this message]
2022-06-30 9:06 ` [PATCH 0/3] Add 128-bit support mailbox for Tegra234 chips Thierry Reding
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=1656528987-29280-1-git-send-email-kkartik@nvidia.com \
--to=kkartik@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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 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).