From: Conor Dooley <conor.dooley@microchip.com>
To: Md Danish Anwar <a0501179@ti.com>
Cc: Conor Dooley <conor@kernel.org>,
MD Danish Anwar <danishanwar@ti.com>, Suman Anna <s-anna@ti.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <vigneshr@ti.com>,
<srk@ti.com>, <nm@ti.com>
Subject: Re: [PATCH] dt-bindings: remoteproc: pru: Add Interrupt property
Date: Mon, 14 Aug 2023 07:59:51 +0100 [thread overview]
Message-ID: <20230814-circus-preachy-b5b9f6ad07d0@wendy> (raw)
In-Reply-To: <ce22155c-31b9-3dd1-8336-275fa92c234d@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2060 bytes --]
On Mon, Aug 14, 2023 at 10:43:58AM +0530, Md Danish Anwar wrote:
> On 11/08/23 8:51 pm, Conor Dooley wrote:
> > On Fri, Aug 11, 2023 at 04:48:28PM +0530, Md Danish Anwar wrote:
> >
> >>>> There are no standard defines for these interrupt types. However I can create a
> >>>> new .h file defining all the three interrupt cells and their values for both
> >>>> PRU and RTU cores if you think that is required. Otherwise we can go with
> >>>> hardcoded values.
> >>>>
> >>>> Please let me know what you think should be done here.
> >>>
> >>> It'd be good to reference to the documentation for the cells, I don't
> >>> think adding a header is necessary here.
> >>>
> >>
> >> How should I reference to the documentation for the cells?
> >>
> >> Should I just add the details of cells in description of interrupt property here.
> >>
> >> interrupts:
> >> maxItems: 1
> >> description:
> >> Interrupt specifiers enable the virtio/rpmsg communication between MPU
> >> and the PRU/RTU cores. The value of the interrupts should be the PRU
> >> System event number [cell 1], PRU channel [cell 2] and PRU host_event
> >> (target) [cell 3].
> >>
> >> Please let me know if this looks OK to you.
> >
> > I was thinking there'd be an binding for the interrupt controller that
> > you could mentioned.
>
> There is a binding for interrupt-controller [1] that I can mention. I tried using
>
> - $ref: /schemas/interrupt-controller/ti,pruss-intc.yaml#
>
> But it was throwing dt binding errors so I didn't add the ref.
Yeah, you're not a pruss-itc so that makes sense.
>
> I will mention this file name in the description of the property like below,
>
> description:
> Interrupt specifiers enable the virtio/rpmsg communication between MPU
> and the PRU/RTU cores. For the values of the interrupt cells please
> refer to interrupt-controller/ti,pruss-intc.yaml schema.
>
> Please let me know if this looks OK to you.
This is what I would've expected, yea
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-08-14 7:01 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
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 [this message]
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=20230814-circus-preachy-b5b9f6ad07d0@wendy \
--to=conor.dooley@microchip.com \
--cc=a0501179@ti.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@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=s-anna@ti.com \
--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