From: Conor Dooley <conor@kernel.org>
To: Md Danish Anwar <a0501179@ti.com>
Cc: srk@ti.com, devicetree@vger.kernel.org,
Conor Dooley <conor+dt@kernel.org>,
linux-omap@vger.kernel.org, vigneshr@ti.com,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
MD Danish Anwar <danishanwar@ti.com>,
nm@ti.com, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: remoteproc: pru: Add Interrupt property
Date: Tue, 8 Aug 2023 11:48:02 +0100 [thread overview]
Message-ID: <20230808-unwomanly-generic-67d20f0e51cd@spud> (raw)
In-Reply-To: <910a4a98-712a-5517-5a5b-ffb962f83463@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 2146 bytes --]
On Tue, Aug 08, 2023 at 03:14:31PM +0530, Md Danish Anwar wrote:
> Hi Conor,
>
> On 07/08/23 8:09 pm, Conor Dooley wrote:
> > On Mon, Aug 07, 2023 at 04:38:36PM +0530, MD Danish Anwar wrote:
> >> Add interrupts and interrupt-names protperties for PRU and RTU cores.
> >>
> >> Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
> >> ---
> >> .../bindings/remoteproc/ti,pru-rproc.yaml | 22 +++++++++++++++++++
> >> 1 file changed, 22 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.yaml
> >> index cd55d80137f7..6970316943bb 100644
> >> --- a/Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.yaml
> >> +++ b/Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.yaml
> >> @@ -66,6 +66,16 @@ properties:
> >> Should contain the name of the default firmware image
> >> file located on the firmware search path.
> >>
> >> + interrupts:
> >> + maxItems: 1
> >> + description:
> >> + Interrupt specifiers enable the virtio/rpmsg communication between MPU
> >> + and the PRU/RTU cores.
> >> +
> >> + interrupt-names:
> >> + items:
> >> + - const: vring
> >> +
> >> if:
> >> properties:
> >> compatible:
> >> @@ -171,6 +181,9 @@ examples:
> >> <0x22400 0x100>;
> >> reg-names = "iram", "control", "debug";
> >> firmware-name = "am65x-pru0_0-fw";
> >> + interrupt-parent = <&icssg0_intc>;
> >> + interrupts = <16 2 2>;
> >> + interrupt-names = "vring";
> >> };
> >
> > These examples would probably be more helpful if they used the
> > appropriate defines, no?
> >
>
> PRUSS Interrupt controller doesn't have any appropriate defines. This doesn't
> use GIC so defines from arm-gic.h can not be used here. These are specific to
> PRUSS INTC.
I was deliberately vague in case the gic stuff applied too, but my main
question was about the standard defines used for interrupt types.
> I think these example are OK. Please let me know if this is OK to you.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-08 10:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 11:08 [PATCH] dt-bindings: remoteproc: pru: Add Interrupt property MD Danish Anwar
2023-08-07 14:39 ` Conor Dooley
2023-08-08 9:44 ` Md Danish Anwar
2023-08-08 10:18 ` Krzysztof Kozlowski
2023-08-08 10:57 ` Md Danish Anwar
2023-08-08 14:53 ` Krzysztof Kozlowski
2023-08-08 10:48 ` Conor Dooley [this message]
2023-08-08 11:00 ` Md Danish Anwar
2023-08-08 11:28 ` Conor Dooley
2023-08-08 12:52 ` Md Danish Anwar
2023-08-11 11:18 ` Md Danish Anwar
2023-08-11 15:21 ` Conor Dooley
2023-08-14 5:13 ` Md Danish Anwar
2023-08-14 6:59 ` Conor Dooley
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=20230808-unwomanly-generic-67d20f0e51cd@spud \
--to=conor@kernel.org \
--cc=a0501179@ti.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=srk@ti.com \
--cc=vigneshr@ti.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