public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel•org>
To: Marc Zyngier <maz@kernel•org>
Cc: devicetree@vger•kernel.org, Jason Cooper <jason@lakedaemon•net>,
	Saravana Kannan <saravanak@google•com>,
	kernel-team@android•com, Hanks Chen <hanks.chen@mediatek•com>,
	linux-kernel@vger•kernel.org,
	Bjorn Andersson <bjorn.andersson@linaro•org>,
	Matthias Brugger <matthias.bgg@gmail•com>,
	Andy Gross <agross@kernel•org>,
	John Stultz <john.stultz@linaro•org>,
	Enric Balletbo i Serra <enric.balletbo@collabora•com>,
	Frank Wunderlich <linux@fw-web•de>,
	Frank Rowand <frowand.list@gmail•com>,
	Thomas Gleixner <tglx@linutronix•de>,
	linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH 0/6] irqchip: Hybrid probing
Date: Tue, 15 Sep 2020 15:13:54 -0600	[thread overview]
Message-ID: <20200915211354.GA2469362@bogus> (raw)
In-Reply-To: <20200912125148.1271481-1-maz@kernel.org>

On Sat, Sep 12, 2020 at 01:51:42PM +0100, Marc Zyngier wrote:
> A recent attempt at converting a couple of interrupt controllers from
> early probing to standard platform drivers have badly failed, as it
> became evident that although an interrupt controller can easily probe
> late, device drivers for the endpoints connected to it are rarely
> equipped to deal with probe deferral. Changes were swiftly reverted.
>
> However, there is some value in *optionally* enabling this, if only
> for development purposes, as there is otherwise a "chicken and egg"
> problem, and a few people (cc'd) are working on a potential solution.
> 
> This short series enables the infrastructure for modular building
> whilst retaining the usual early probing for monolithic build, and
> introduces it to the three drivers that were previously made to probe
> as platform drivers.

I hardly expected more OF_DECLARE macros when I opened this up. Given 
desires to get rid of them, I don't think adding to it is the way 
forward. That wrapping a platform driver around OF_DECLARE looks pretty 
horrible IMO. 

I browsed some of the discussion around this. It didn't seem like it's 
a large number of drivers that have to be fixed to defer probe 
correctly. Am I missing something?

I'd rather keep the pressure on getting fw_devlink on by default.

Rob

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-09-15 21:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-12 12:51 [PATCH 0/6] irqchip: Hybrid probing Marc Zyngier
2020-09-12 12:51 ` [PATCH 1/6] of: Add basic infrastructure to create early probe arrays Marc Zyngier
2020-09-12 23:20   ` Bjorn Andersson
2020-09-13  2:40   ` Bjorn Andersson
2020-09-12 12:51 ` [PATCH 2/6] irqchip: Make IRQCHIP_MATCH() type safe Marc Zyngier
2020-09-12 23:20   ` Bjorn Andersson
2020-09-12 12:51 ` [PATCH 3/6] irqchip: Introduce IRQCHIP_HYBRID_DRIVER_{BEGIN, END} macros Marc Zyngier
2020-09-12 23:21   ` Bjorn Andersson
2020-09-12 12:51 ` [PATCH 4/6] irqchip/mtk-cirq: Allow modular build Marc Zyngier
2020-09-12 23:22   ` Bjorn Andersson
2020-09-16  8:26     ` Enric Balletbo Serra
2020-09-12 12:51 ` [PATCH 5/6] irqchip/mtk-sysirq: " Marc Zyngier
2020-09-12 23:22   ` Bjorn Andersson
2020-09-16  8:22     ` Enric Balletbo Serra
2020-09-12 12:51 ` [PATCH 6/6] irqchip/qcom-pdc: " Marc Zyngier
2020-09-12 23:22   ` Bjorn Andersson
2020-09-14 20:33 ` [PATCH 0/6] irqchip: Hybrid probing John Stultz
2020-09-15 21:13 ` Rob Herring [this message]
2020-09-16  8:51   ` Marc Zyngier
2020-09-16 15:18     ` Rob Herring

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=20200915211354.GA2469362@bogus \
    --to=robh@kernel$(echo .)org \
    --cc=agross@kernel$(echo .)org \
    --cc=bjorn.andersson@linaro$(echo .)org \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=enric.balletbo@collabora$(echo .)com \
    --cc=frowand.list@gmail$(echo .)com \
    --cc=hanks.chen@mediatek$(echo .)com \
    --cc=jason@lakedaemon$(echo .)net \
    --cc=john.stultz@linaro$(echo .)org \
    --cc=kernel-team@android$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux@fw-web$(echo .)de \
    --cc=matthias.bgg@gmail$(echo .)com \
    --cc=maz@kernel$(echo .)org \
    --cc=saravanak@google$(echo .)com \
    --cc=tglx@linutronix$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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