devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kartik <kkartik@nvidia.com>
To: <robh@kernel.org>
Cc: <devicetree@vger.kernel.org>, <jassisinghbrar@gmail.com>,
	<jonathanh@nvidia.com>, <kkartik@nvidia.com>,
	<krzk+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-tegra@vger.kernel.org>, <thierry.reding@gmail.com>
Subject: Re: [PATCH 2/3] dt-bindings: tegra186-hsp: add type for shared mailboxes
Date: Mon, 18 Apr 2022 16:31:12 +0530	[thread overview]
Message-ID: <1650279672-11757-1-git-send-email-kkartik@nvidia.com> (raw)
In-Reply-To: <YlgnXKGHqcCgItlb@robh.at.kernel.org>

On 14/04/2022 13:53, Rob Herring wrote:
>> Tegra234 supports sending/receiving 32-bit and 128-bit data over
>> a shared mailbox. Based on the data size to be used, clients need
>> to specify the type of shared mailbox in the device tree.
>> 
>> Add a macro for 128-bit shared mailbox. Mailbox clients can use this
>> macro as a flag in device tree to enable 128-bit data support for a
>> shared mailbox.
>> 
>> Signed-off-by: Kartik <kkartik@nvidia.com>
>
>Need a full name here.

This is my legal name as per the government ID's.

>
>> ---
>>  .../devicetree/bindings/mailbox/nvidia,tegra186-hsp.yaml | 9 +++++++++
>>  include/dt-bindings/mailbox/tegra186-hsp.h               | 5 +++++
>>  2 files changed, 14 insertions(+)
>> 
>> diff --git a/Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.yaml b/Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.yaml
>> index 9f7a7296b57f..a3e87516d637 100644
>> --- a/Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.yaml
>> +++ b/Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.yaml
>> @@ -26,6 +26,15 @@ description: |
>>    second cell is used to identify the mailbox that the client is going
>>    to use.
>>  
>> +  For shared mailboxes, the first cell composed of two fields:
>> +    - bits 15..8:
>> +        A bit mask of flags that further specifies the type of shared
>> +        mailbox to be used (based on the data size). If no flag is
>> +        specified then, 32-bit shared mailbox is used.
>> +    - bits 7..0:
>> +        Defines the type of the mailbox to be used. This field should be
>> +        TEGRA_HSP_MBOX_TYPE_SM for shared mailboxes.
>> +
>>    For doorbells, the second cell specifies the index of the doorbell to
>>    use.
>>  
>> diff --git a/include/dt-bindings/mailbox/tegra186-hsp.h b/include/dt-bindings/mailbox/tegra186-hsp.h
>> index 3bdec7a84d35..b9ccae2aa9e2 100644
>> --- a/include/dt-bindings/mailbox/tegra186-hsp.h
>> +++ b/include/dt-bindings/mailbox/tegra186-hsp.h
>> @@ -15,6 +15,11 @@
>>  #define TEGRA_HSP_MBOX_TYPE_SS 0x2
>>  #define TEGRA_HSP_MBOX_TYPE_AS 0x3
>>  
>> +/*
>> + * These define the types of shared mailbox supported based on data size.
>> + */
>> +#define TEGRA_HSP_MBOX_TYPE_SM_128BIT (1 << 8)
>> +
>>  /*
>>   * These defines represent the bit associated with the given master ID in the
>>   * doorbell registers.
>> -- 
>> 2.17.1
>> 
>> 

  reply	other threads:[~2022-04-18 11:01 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 [this message]
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 ` [PATCH 0/3] Add 128-bit support mailbox for Tegra234 chips Kartik
2022-06-30  9:06   ` 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=1650279672-11757-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@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).