From: cyndis@kapsi.fi (Mikko Perttunen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/8] dt-bindings: tegra186-hsp: Add shared interrupts
Date: Tue, 19 Jun 2018 15:41:05 +0300 [thread overview]
Message-ID: <3b5708ef-c82f-c4b2-da50-2cb2afa3edb2@kapsi.fi> (raw)
In-Reply-To: <2bed23e6-19d5-66f8-774e-d613a91b1607@nvidia.com>
On 22.05.2018 18:15, Jon Hunter wrote:
>
> On 08/05/18 12:43, Mikko Perttunen wrote:
>> Non-doorbell interrupts are routed through "shared interrupts". These
>> interrupts can be mapped to various internal interrupt lines. Add
>> interrupt properties for shared interrupts to the tegra186-hsp device
>> tree bindings.
>
> Reading the Tegra documentation, although the doorbells have dedicated
> interrupts, it appears that the doorbell interrupts can also be routed
> via these shared interrupts.
Thanks, I changed the text slightly to account for this.
>
>> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
>> ---
>> ? Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.txt |
>> 2 ++
>> ? 1 file changed, 2 insertions(+)
>>
>> diff --git
>> a/Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.txt
>> b/Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.txt
>> index b99d25fc2f26..9edcdf82d719 100644
>> --- a/Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.txt
>> +++ b/Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.txt
>> @@ -21,6 +21,8 @@ Required properties:
>> ????? Contains a list of names for the interrupts described by the
>> interrupt
>> ????? property. May contain the following entries, in any order:
>> ????? - "doorbell"
>> +??? - "sharedN", where 'N' is a number from zero up to the number of
>> +????? external interrupts supported by the HSP instance minus one.
>> ????? Users of this binding MUST look up entries in the interrupt
>> property
>> ????? by name, using this interrupt-names property to do so.
>> ? - interrupts
>
> How is the mapping of shared-mailboxes interrupts to the actual
> 'sharedN' interrupt managed?
Currently the driver always uses shared0 for mailbox-full interrupt, and
nothing else, which is what downstream does as well. It's difficult to
do anything else as we can trample on some other driver's configuration..
>
> Cheers
> Jon
>
Thanks,
Mikko
next prev parent reply other threads:[~2018-06-19 12:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 11:43 [PATCH 0/8] Tegra Combined UART driver Mikko Perttunen
2018-05-08 11:43 ` [PATCH 1/8] dt-bindings: tegra186-hsp: Add shared interrupts Mikko Perttunen
2018-05-22 15:15 ` Jon Hunter
2018-06-19 12:41 ` Mikko Perttunen [this message]
2018-05-08 11:43 ` [PATCH 2/8] dt-bindings: serial: Add bindings for nvidia, tegra194-tcu Mikko Perttunen
2018-05-22 15:15 ` [PATCH 2/8] dt-bindings: serial: Add bindings for nvidia,tegra194-tcu Jon Hunter
2018-05-22 20:18 ` Rob Herring
2018-05-22 20:20 ` Rob Herring
2018-05-08 11:43 ` [PATCH 3/8] mailbox: Add transmit done by blocking option Mikko Perttunen
2018-05-08 11:43 ` [PATCH 4/8] mailbox: tegra-hsp: Refactor in preparation of mailboxes Mikko Perttunen
2018-05-22 15:36 ` Jon Hunter
2018-06-19 12:52 ` Mikko Perttunen
2018-05-08 11:44 ` [PATCH 5/8] mailbox: tegra-hsp: Add support for shared mailboxes Mikko Perttunen
2018-05-22 16:20 ` Jon Hunter
2018-05-08 11:44 ` [PATCH 6/8] serial: Add Tegra Combined UART driver Mikko Perttunen
2018-05-13 14:16 ` Andy Shevchenko
2018-05-13 18:04 ` Mikko Perttunen
2018-05-13 22:20 ` Andy Shevchenko
2018-05-14 7:36 ` Mikko Perttunen
2018-05-13 15:36 ` Jassi Brar
2018-05-13 18:06 ` Mikko Perttunen
2018-05-08 11:44 ` [PATCH 7/8] arm64: tegra: Add nodes for tcu on Tegra194 Mikko Perttunen
2018-05-22 16:28 ` Jon Hunter
2018-05-08 11:44 ` [PATCH 8/8] arm64: tegra: Mark tcu as primary serial port on Tegra194 P2888 Mikko Perttunen
2018-05-22 16:29 ` Jon Hunter
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=3b5708ef-c82f-c4b2-da50-2cb2afa3edb2@kapsi.fi \
--to=cyndis@kapsi.fi \
--cc=linux-arm-kernel@lists.infradead.org \
/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