devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: Rob Herring <robh@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>, Nishanth Menon <nm@ti.com>,
	Tero Kristo <t-kristo@ti.com>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	Sekhar Nori <nsekhar@ti.com>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Device Tree Mailing List <devicetree@vger.kernel.org>
Subject: Re: [PATCH 04/12] dt-bindings: irqchip: ti,sci-intr: Update bindings to drop the usage of gic as parent
Date: Fri, 29 May 2020 11:18:26 +0100	[thread overview]
Message-ID: <4ea8c6110a16900220a65f1d44145146@kernel.org> (raw)
In-Reply-To: <f803f646-2a55-4f15-9682-1dc616d7c714@ti.com>

On 2020-05-29 11:14, Lokesh Vutla wrote:
> Hi Rob,
> 
> On 29/05/20 3:44 am, Rob Herring wrote:
>> On Wed, May 20, 2020 at 06:14:46PM +0530, Lokesh Vutla wrote:
>>> Drop the firmware related dt-bindings and use the hardware specified
>>> interrupt numbers within Interrupt Router. This ensures interrupt 
>>> router
>>> DT node need not assume any interrupt parent type.
>> 
>> I didn't like this binding to begin with, but now you're breaking
>> compatibility.
> 
> Yes, I do agree that this change is breaking backward compatibility. 
> But IMHO,
> this does cleanup of firmware specific properties from DT. Since this 
> is not
> deployed out yet in the wild market, I took the leverage of breaking 
> backward
> compatibility. Before accepting these changes from firmware team, I did
> discuss[0] with Marc on this topic.

And I assume that should anyone complain about the kernel being broken
because they have an old firmware, you'll be OK with the patches being
reverted, right?

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2020-05-29 10:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 12:44 [PATCH 00/12] irqchip: ti,sci-intr/inta: Update the dt bindings to accept different interrupt parents Lokesh Vutla
2020-05-20 12:44 ` [PATCH 01/12] firmware: ti_sci: Drop the device id to resource type translation Lokesh Vutla
2020-05-20 12:44 ` [PATCH 02/12] firmware: ti_sci: Drop unused structure ti_sci_rm_type_map Lokesh Vutla
2020-05-20 12:44 ` [PATCH 03/12] firmware: ti_sci: Add support for getting resource with subtype Lokesh Vutla
2020-05-20 12:44 ` [PATCH 04/12] dt-bindings: irqchip: ti,sci-intr: Update bindings to drop the usage of gic as parent Lokesh Vutla
2020-05-28 22:14   ` Rob Herring
2020-05-29 10:14     ` Lokesh Vutla
2020-05-29 10:18       ` Marc Zyngier [this message]
2020-06-01 11:36         ` [PATCH 04/12] dt-bindings: irqchip: ti, sci-intr: " Lokesh Vutla
2020-06-15  8:03           ` Lokesh Vutla
2020-06-15  8:34             ` Marc Zyngier
2020-07-09  9:40               ` Lokesh Vutla
2020-05-29 11:13     ` [PATCH 04/12] dt-bindings: irqchip: ti,sci-intr: " Lokesh Vutla
2020-05-20 12:44 ` [PATCH 05/12] dt-bindings: irqchip: Convert ti,sci-intr bindings to yaml Lokesh Vutla
2020-05-20 12:44 ` [PATCH 06/12] irqchip/ti-sci-intr: Add support for INTR being a parent to INTR Lokesh Vutla
2020-05-20 12:44 ` [PATCH 07/12] dt-bindings: irqchip: ti,sci-inta: Update docs to support different parent Lokesh Vutla
2020-05-20 12:44 ` [PATCH 08/12] dt-bindings: irqchip: Convert ti,sci-inta bindings to yaml Lokesh Vutla
2020-05-20 12:44 ` [PATCH 09/12] irqchip/ti-sci-inta: Add support for INTA directly connecting to GIC Lokesh Vutla
2020-05-20 12:44 ` [PATCH 10/12] arm64: dts: k3-j721e: ti-sci-inta/intr: Update to latest bindings Lokesh Vutla
2020-05-20 12:44 ` [PATCH 11/12] arm64: dts: k3-am65: " Lokesh Vutla
2020-05-20 12:44 ` [PATCH 12/12] arm64: dts: k3-am65: Update the RM resource types Lokesh Vutla

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=4ea8c6110a16900220a65f1d44145146@kernel.org \
    --to=maz@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lokeshvutla@ti.com \
    --cc=nm@ti.com \
    --cc=nsekhar@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=robh@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).