devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Arnd Bergmann <arnd.bergmann@linaro.org>,
	Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH 1/2] clocksource/drivers/ostm: Delay driver registration
Date: Thu, 30 Aug 2018 11:16:48 +0200	[thread overview]
Message-ID: <ba334f02-ac37-0908-ec0c-da8a6459fab4@linaro.org> (raw)
In-Reply-To: <CAMuHMdV3Ai+CLHBJ_GH9d=JN0cmiaQT3eSfNGRgiiMffgK7stg@mail.gmail.com>


[Added Arnd Bergmann, Bartosz Golaszewski and Mark Brown]

On 30/08/2018 10:48, Geert Uytterhoeven wrote:
> Hi Daniel,

[ ... ]

>> Yeah, I got this point. But it is the meaning of your sentence: "...
>> which causes issues with complex dependencies.".
>>
>> It is ambiguous *what* causes the issues.
>>
>> Did you meant an attempt was done to support EPROBE_DEFER with
>> *_OF_DECLARE but caused too much issues with the complex dependencies?
>>
>> Or the current situation is causing too much issues with the complex
>> dependencies?
>>
>> (I know the latter is true, it is about the meaning of the sentence).
> 
> I meant the latter.
> 
> AFAIK no attempt was done to support EPROBE_DEFER with *_OF_DECLARE.
> IMHO it would be pointless, as it would be much easier to just switch to real
> platform drivers.

May be, may be not.

>From your point of view, the change is simple because it touches only a
single driver.

>From my point of view, the change implies a split in the approach while
I'm trying to unify the drivers little by little and there are hundred
of them.

It is not the first time we face this situation and Bartosz Golaszewski
has a similar problem [1].

We have all the frameworks we need to solve this properly but I would
like something we can propagate to all drivers (OF and !OF) so we end up
with unified code.

It is time we clearly state the dependency issues and we find a proper
way to solve it.




[1] https://lkml.org/lkml/2018/4/26/657

-- 
 <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

  reply	other threads:[~2018-08-30  9:16 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
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 [this message]
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=ba334f02-ac37-0908-ec0c-da8a6459fab4@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=Chris.Brandt@renesas.com \
    --cc=arnd.bergmann@linaro.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=broonie@linaro.org \
    --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).