Linux-Devicetree Archive on lore.kernel.org
 help / color / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>, Rob Herring <robh@kernel.org>,
	Suman Anna <s-anna@ti.com>
Cc: Marc Zyngier <maz@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>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Device Tree Mailing List <devicetree@vger.kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH v5 00/10] irqchip: ti, sci-intr/inta: Update the dt bindings to accept different interrupt parents
Date: Tue, 4 Aug 2020 22:58:34 +0530
Message-ID: <74aee615-5dc4-20b2-293c-54a6b2768f73@ti.com> (raw)
In-Reply-To: <d7fed961-63ad-eacf-76ba-e8641315994a@ti.com>

On 8/4/20 10:46 PM, Lokesh Vutla wrote:
> Hi All,
> 
> On 02/08/20 4:04 pm, Sekhar Nori wrote:
>> On 8/1/20 2:29 AM, Rob Herring wrote:
>>> On Fri, Jul 31, 2020 at 01:24:17PM -0500, Suman Anna wrote:
>>>> On 7/31/20 1:16 PM, Rob Herring wrote:
>>>>> On Fri, Jul 31, 2020 at 06:01:50PM +0100, Marc Zyngier wrote:
>>>>>> On 2020-07-28 06:17, Lokesh Vutla wrote:
>>>>>>> Hi Marc,
>>>>>>> 	This is continuation of the RFC patches[0] regarding the driver
>>>>>>> updates to support for following interrupt parent connection:
>>>>>>> - INTR -> INTR
>>>>>>> - INTA -> GICv3
>>>>>>> The current existing driver assumes that INTR is always connected to
>>>>>>> GICv3 and INTA is always connected to INTR.
>>>>>>
>>>>>> I'm OK to take this if I can get an Ack from RobH on the three
>>>>>> DT patches that still need it.
>>>>>
>>>>> Reviewed-by: Rob Herring <robh@kernel.org>
>>>>>
>>>>> However, there's a dependency on
>>>>> bindings/arm/keystone/ti,k3-sci-common.yaml.
>>>>>
>>>>> That's a dependency on this being merged. I don't care if it breaks in
>>>>> your tree, but I care for -next and Linus' tree. There could also be
>>>>> other 'make dt_bindings_check' failures/warnings with this as the above
>>>>> dependency prevents further testing.
>>>>>
>>>>
>>>> Bjorn did pick up the above common binding file through the remoteproc tree,
>>>> and it is available in -next. That said, I donno the merge order between
>>>> remoteproc and irq subsystem trees into -next, and if that is a concern.
>>>
>>> I'm less concerned about merge order at this point. -rc1 not being 
>>> broken is the low bar I have...
>>
>> Looking at Bjorn's remoteproc tree[0], the common bindings patch is 
>> applied on top of other (unrelated) remoteproc patches, so merging it 
>> into Marc's tree is out of question unless Bjorn is willing to re-write 
>> his tree (probably not).
>>
>> The other option would be for Marc/Thomas to add these patches into a 
>> 'late' branch, to be sent to Linus after Bjorn's tree has been merged.
>> Bjorn could help by sending his pull request early and someone from TI 
>> can keep an eye out for when its safe to merge.
> 
> What can we do to take this forward? Once this series is merged, DT changes
> should also be merged. Else DMA will be broken as DT backward compatibility is
> broken.

The DT parts should have been posted in the same series then, so as to
not cause breakage after the series is applied, and to preserve bisect
as much as possible.

IMHO, the whole series needs to be merged together even if parts of it
come from individual maintainers as immutable commits.

Do the DT portions cause merge conflicts with what is already there in
-next?

I think the next step would be to post the series again, this time with
DT changes included. Whether it goes into v5.9 or v5.10, thats probably
needed anyway.

Thanks,
Sekhar


      reply index

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28  5:17 Lokesh Vutla
2020-07-28  5:17 ` [PATCH v5 01/10] firmware: ti_sci: Drop the device id to resource type translation Lokesh Vutla
2020-07-28  5:17 ` [PATCH v5 02/10] firmware: ti_sci: Drop unused structure ti_sci_rm_type_map Lokesh Vutla
2020-07-28  5:17 ` [PATCH v5 03/10] firmware: ti_sci: Add support for getting resource with subtype Lokesh Vutla
2020-07-28  5:17 ` [PATCH v5 04/10] dt-bindings: irqchip: ti,sci-intr: Update bindings to drop the usage of gic as parent Lokesh Vutla
2020-07-28  5:17 ` [PATCH v5 05/10] dt-bindings: irqchip: Convert ti,sci-intr bindings to yaml Lokesh Vutla
2020-07-28  5:17 ` [PATCH v5 06/10] irqchip/ti-sci-intr: Add support for INTR being a parent to INTR Lokesh Vutla
2020-07-28  5:17 ` [PATCH v5 07/10] dt-bindings: irqchip: ti,sci-inta: Update docs to support different parent Lokesh Vutla
2020-07-28  5:17 ` [PATCH v5 08/10] dt-bindings: irqchip: Convert ti,sci-inta bindings to yaml Lokesh Vutla
2020-07-28  5:17 ` [PATCH v5 09/10] irqchip/ti-sci-inta: Do not store TISCI device id in platform device id field Lokesh Vutla
2020-07-28  5:17 ` [PATCH v5 10/10] irqchip/ti-sci-inta: Add support for INTA directly connecting to GIC Lokesh Vutla
2020-07-31 17:01 ` [PATCH v5 00/10] irqchip: ti, sci-intr/inta: Update the dt bindings to accept different interrupt parents Marc Zyngier
2020-07-31 17:51   ` Lokesh Vutla
2020-07-31 18:16   ` Rob Herring
2020-07-31 18:24     ` Suman Anna
2020-07-31 20:59       ` Rob Herring
2020-08-02 10:34         ` Sekhar Nori
2020-08-04 17:16           ` Lokesh Vutla
2020-08-04 17:28             ` Sekhar Nori [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=74aee615-5dc4-20b2-293c-54a6b2768f73@ti.com \
    --to=nsekhar@ti.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lokeshvutla@ti.com \
    --cc=maz@kernel.org \
    --cc=nm@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=robh@kernel.org \
    --cc=s-anna@ti.com \
    --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

Linux-Devicetree Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-devicetree/0 linux-devicetree/git/0.git
	git clone --mirror https://lore.kernel.org/linux-devicetree/1 linux-devicetree/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-devicetree linux-devicetree/ https://lore.kernel.org/linux-devicetree \
		devicetree@vger.kernel.org
	public-inbox-index linux-devicetree

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-devicetree


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git