devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: jason@lakedaemon.net, robh+dt@kernel.org, nm@ti.com,
	linux-kernel@vger.kernel.org, maz@kernel.org,
	devicetree@vger.kernel.org, t-kristo@ti.com,
	linux-arm-kernel@lists.infradead.org, lokeshvutla@ti.com,
	ssantosh@kernel.org, tglx@linutronix.de
Subject: Re: [PATCH 1/2] dt-bindings: irqchip: ti, sci-inta: Update for unmapped event handling
Date: Tue, 29 Sep 2020 14:43:50 -0500	[thread overview]
Message-ID: <20200929194350.GA1038748@bogus> (raw)
In-Reply-To: <20200928063930.12012-2-peter.ujfalusi@ti.com>

On Mon, 28 Sep 2020 09:39:29 +0300, Peter Ujfalusi wrote:
> The new DMA architecture introduced with AM64 introduced new event types:
> unampped events.
> 
> These events are mapped within INTA in contrast to other K3 devices where
> the events with similar function was originating from the UDMAP or ringacc.
> 
> The ti,unmapped-event-sources should contain phandle array to the devices
> in the system (typically DMA controllers) from where the unmapped events
> originate.
> 
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
>  .../bindings/interrupt-controller/ti,sci-inta.yaml           | 5 +++++
>  1 file changed, 5 insertions(+)
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2020-09-29 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28  6:39 [PATCH 0/2] irqchip/ti-sci-inta: Support for unmapped events Peter Ujfalusi
2020-09-28  6:39 ` [PATCH 1/2] dt-bindings: irqchip: ti,sci-inta: Update for unmapped event handling Peter Ujfalusi
2020-09-29 19:43   ` Rob Herring [this message]
2020-09-28  6:39 ` [PATCH 2/2] irqchip/ti-sci-inta: Add support " Peter Ujfalusi
2020-09-28  7:54   ` Peter Ujfalusi

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=20200929194350.GA1038748@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=maz@kernel.org \
    --cc=nm@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=t-kristo@ti.com \
    --cc=tglx@linutronix.de \
    /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).