From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jorge Marques <gastmaier@gmail.com>
Cc: Jorge Marques <jorge.marques@analog.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Frank Li <Frank.Li@nxp.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-i3c@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: i3c: Add adi-i3c-master
Date: Thu, 19 Jun 2025 08:15:44 +0200 [thread overview]
Message-ID: <9798e5e1-f4be-4c8b-b375-fadc915b3fe8@kernel.org> (raw)
In-Reply-To: <dfejhrchaxwze7gkipdgcx5byefv6hudi456na25yrts6viqvw@lfnv55dgvk32>
On 18/06/2025 21:55, Jorge Marques wrote:
>> Usually 0 has a meaning as well. Where is this used DTS snippet used (on
>> which platform)?
>>
>
> The example provided is used on AMD xilinx arm,cortex-a9-gic.
> The IP core is tested on AMD Xilinx, Altera FPGAs (arm, microblaze, arm64).
> Test/support to RiscV-based Lattice FPGAs should eventually also come.
>
> In this example 0 means Shared Peripheral Interrupt, but has no header
Of course it has... just like 100% of bindings for devices in a SoC.
> file defining. I guess I could make it generic and set to
>
> interrupts = <3 IRQ_TYPE_LEVEL_HIGH>;
>
That's fine as well.
Best regards,
Krzysztof
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2025-06-19 6:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 7:16 [PATCH v3 0/2] Add ADI I3C Controller Jorge Marques
2025-06-18 7:16 ` [PATCH v3 1/2] dt-bindings: i3c: Add adi-i3c-master Jorge Marques
2025-06-18 8:40 ` Rob Herring (Arm)
2025-06-18 9:21 ` Krzysztof Kozlowski
2025-06-18 12:15 ` Jorge Marques
2025-06-18 15:45 ` Krzysztof Kozlowski
2025-06-18 19:55 ` Jorge Marques
2025-06-19 6:15 ` Krzysztof Kozlowski [this message]
2025-06-18 7:16 ` [PATCH v3 2/2] i3c: master: Add driver for Analog Devices I3C Controller IP Jorge Marques
2025-06-18 19:40 ` Frank Li
2025-06-18 22:17 ` Jorge Marques
2025-06-19 2:18 ` Frank Li
2025-06-19 10:32 ` Jorge Marques
2025-06-19 15:10 ` Frank Li
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=9798e5e1-f4be-4c8b-b375-fadc915b3fe8@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gastmaier@gmail.com \
--cc=jorge.marques@analog.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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