From: Mark Brown <broonie@kernel.org>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Jonas Karlman <jonas@kwiboo.se>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
lkml <linux-kernel@vger.kernel.org>,
Neil Armstrong <narmstrong@baylibre.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH v6 2/4] driver core: add deferring probe reason to devices_deferred property
Date: Fri, 10 Jul 2020 12:07:40 +0100 [thread overview]
Message-ID: <20200710110740.GB5653@sirena.org.uk> (raw)
In-Reply-To: <8b228571-d124-e5e2-2f53-57ea4b46b904@samsung.com>
[-- Attachment #1.1: Type: text/plain, Size: 635 bytes --]
On Fri, Jul 10, 2020 at 09:42:49AM +0200, Andrzej Hajda wrote:
> But the provider does not know if *get is called in probe context or
> not, so it is not able to differentiate it.
> So the whole idea is for me suspicious/wrong. Kind of proof:
> 1. If you insist that provider's EPROBE_ERROR must be always propagated
> to driver core then.
> 2. You must enforce that resources can be gathered only from probe.
> 3. But this is against current practice, even if majority of drivers
> does it from probe, there are many which doesn't.
Those drivers are probably buggy anyway at this point given probe
deferral.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-10 11:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200626100108eucas1p2c6d68625f3755a467d7316dd27704f7c@eucas1p2.samsung.com>
2020-06-26 10:00 ` [PATCH v6 0/4] driver core: add probe error check helper Andrzej Hajda
[not found] ` <CGME20200626100109eucas1p25331652d017cd17d21c0ae60541d1f73@eucas1p2.samsung.com>
2020-06-26 10:01 ` [PATCH v6 1/4] driver core: add device probe log helper Andrzej Hajda
2020-06-26 15:41 ` Rafael J. Wysocki
2020-06-26 16:22 ` Sam Ravnborg
2020-07-01 9:29 ` Grygorii Strashko
[not found] ` <CGME20200626100110eucas1p2c5b91f2c98a5c6e5739f5af3207d192e@eucas1p2.samsung.com>
2020-06-26 10:01 ` [PATCH v6 2/4] driver core: add deferring probe reason to devices_deferred property Andrzej Hajda
2020-06-26 15:43 ` Rafael J. Wysocki
2020-06-26 17:11 ` Grygorii Strashko
2020-06-29 11:28 ` Andrzej Hajda
2020-06-30 8:59 ` Grygorii Strashko
2020-06-30 15:41 ` Andrzej Hajda
2020-06-30 18:00 ` Dmitry Torokhov
2020-07-02 6:57 ` Andrzej Hajda
2020-07-07 4:14 ` Dmitry Torokhov
2020-07-10 7:42 ` Andrzej Hajda
2020-07-10 11:07 ` Mark Brown [this message]
[not found] ` <CGME20200626100110eucas1p24327c924dada0c2e86ecf0ab5b5af571@eucas1p2.samsung.com>
2020-06-26 10:01 ` [PATCH v6 3/4] drm/bridge/sii8620: fix resource acquisition error handling Andrzej Hajda
2020-06-29 8:33 ` Neil Armstrong
[not found] ` <CGME20200626100111eucas1p18e175e6c77af483bd80fb90c171b05db@eucas1p1.samsung.com>
2020-06-26 10:01 ` [PATCH v6 4/4] drm/bridge: lvds-codec: simplify " Andrzej Hajda
2020-06-29 8:33 ` Neil Armstrong
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=20200710110740.GB5653@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=andy.shevchenko@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=grygorii.strashko@ti.com \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=narmstrong@baylibre.com \
--cc=rafael@kernel.org \
/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).