From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Chris Brandt <Chris.Brandt@renesas.com>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms+renesas@verge.net.au>
Subject: Re: [PATCH 1/2] clocksource/drivers/ostm: Delay driver registration
Date: Thu, 30 Aug 2018 10:08:49 +0200 [thread overview]
Message-ID: <c4bd550f-5319-9d92-a30a-1d12fc9bbcab@linaro.org> (raw)
In-Reply-To: <CAMuHMdX9nXYan-m14k6h7OU1UCGW_irDLvMMi==dnM0cdUR_nA@mail.gmail.com>
On 30/08/2018 09:54, Geert Uytterhoeven wrote:
> Hi Daniel,
>
> On Wed, Aug 29, 2018 at 6:26 PM Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>> On 29/08/2018 17:44, Chris Brandt wrote:
>>> On Wednesday, August 29, 2018 1, Daniel Lezcano wrote:
>>>> Can the boot constraints [1] solve this issue instead of the changes you
>>>> are proposing ?
>>>>
>>>> [1] https://lwn.net/Articles/747250/
>>>
>>> Thanks for the suggestion, but...
>>>
>>> I grepped for "boot_constraint" and it shows up nowhere in the current
>>> kernel.
>>>
>>> Also, this article was written Feb 16, 2018, and I can see that the
>>> patch series was still being submitted (V7) as of Feb 23, 2018.
>>
>> Ah ok, fair enough, I thought it was merged. In any case, after thinking
>> about it, it wouldn't have helped.
>>
>> My concern is if we can avoid changing the TIMER_OF_DECLARE because of
>> the boot order, it would be better.
>>
>> Can returning EPROBE_DEFER fix this issue? Or use the 'complex
>> dependencies' [1]?
>
> *_OF_DECLARE() is not compatible with EPROBE_DEFER, which causes
> issues with complex dependencies.
What causes issues ? Add support for EPROBE_DEFER with OF_DECLARE or not
having support of it ?
> That's exactly why many subsystems are moving away from it.
> E.g. IOMMU_OF_DECLARE was removed in v4.19-rc1.
Ok, thanks for information.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2018-08-30 8:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 13:29 [PATCH 0/2] clocksource: ostm: Add support for RZ/A2 Chris Brandt
2018-08-29 13:29 ` [PATCH 1/2] clocksource/drivers/ostm: Delay driver registration Chris Brandt
2018-08-29 15:09 ` Daniel Lezcano
2018-08-29 15:44 ` Chris Brandt
2018-08-29 16:26 ` Daniel Lezcano
2018-08-29 18:17 ` Chris Brandt
2018-08-29 19:57 ` Chris Brandt
2018-08-30 7:54 ` Geert Uytterhoeven
2018-08-30 8:08 ` Daniel Lezcano [this message]
2018-08-30 8:27 ` Geert Uytterhoeven
2018-08-30 8:37 ` Daniel Lezcano
2018-08-30 8:48 ` Geert Uytterhoeven
2018-08-30 9:16 ` Daniel Lezcano
2018-08-30 9:38 ` Bartosz Golaszewski
2018-09-07 15:16 ` Chris Brandt
2018-09-10 13:48 ` Rob Herring
2018-09-10 17:20 ` Chris Brandt
2018-09-11 16:01 ` Rob Herring
2018-09-11 18:42 ` Chris Brandt
2018-09-13 13:17 ` Daniel Lezcano
2018-09-13 13:20 ` Geert Uytterhoeven
2018-09-13 14:54 ` Chris Brandt
2018-09-14 11:39 ` Geert Uytterhoeven
2018-09-17 18:56 ` Chris Brandt
2018-09-18 7:24 ` Geert Uytterhoeven
2018-09-18 11:55 ` Chris Brandt
2018-09-18 12:58 ` Geert Uytterhoeven
2018-09-18 15:04 ` Chris Brandt
2018-09-18 15:10 ` Geert Uytterhoeven
2018-09-18 15:51 ` Chris Brandt
2018-09-18 16:16 ` Geert Uytterhoeven
2018-09-18 16:31 ` Chris Brandt
2018-08-29 13:29 ` [PATCH 2/2] dt-bindings: timer: ostm: Add R7S9210 support Chris Brandt
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=c4bd550f-5319-9d92-a30a-1d12fc9bbcab@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=Chris.Brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--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).