From: Thomas Gleixner <tglx@linutronix.de>
To: Saravana Kannan <saravanak@google.com>,
Ionela Voinescu <ionela.voinescu@arm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-tip-commits@vger.kernel.org, x86 <x86@kernel.org>,
liviu.dudau@arm.com, sudeep.holla@arm.com,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [tip: timers/core] clocksource/drivers/timer-probe: Avoid creating dead devices
Date: Wed, 25 Mar 2020 22:47:25 +0100 [thread overview]
Message-ID: <87lfnoxg2a.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAGETcx80wvGnS0-MwJ9M9RR9Mny0jmmep+JfwaUJUOR2bfJYsQ@mail.gmail.com>
Saravana Kannan <saravanak@google.com> writes:
> On Tue, Mar 24, 2020 at 11:34 AM Saravana Kannan <saravanak@google.com> wrote:
> I took a closer look. So two different drivers [1] [2] are saying they
> know how to handle "arm,vexpress-sysreg" and are expecting to run at
> the same time. That seems a bit unusual to me. I wonder if this is a
> violation of the device-driver model because this expectation would
> never be allowed if these device drivers were actual drivers
> registered with driver-core. But that's a discussion for another time.
>
> To fix this issue you are facing, this patch should work:
> https://lore.kernel.org/lkml/20200324195302.203115-1-saravanak@google.com/T/#u
Sorry, that's not a fix. That's a crude hack.
As this is also causing trouble on tegra30-cardhu-a04 the only sane
solution is to revert it and start over with a proper solution for the
vexpress problem and a root cause analysis for the tegra.
Thanks,
tglx
next prev parent reply other threads:[~2020-03-25 21:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 5:21 [PATCH v1] clocksource: Avoid creating dead devices Saravana Kannan
2020-02-19 2:20 ` Saravana Kannan
2020-02-27 9:06 ` Daniel Lezcano
2020-02-27 21:22 ` Saravana Kannan
2020-03-04 19:30 ` Saravana Kannan
2020-03-04 19:56 ` Daniel Lezcano
2020-03-08 5:53 ` Saravana Kannan
2020-03-16 14:57 ` Daniel Lezcano
2020-03-16 17:49 ` Saravana Kannan
2020-03-16 18:07 ` Daniel Lezcano
2020-03-16 18:15 ` Saravana Kannan
[not found] ` <5e70b653.1c69fb81.b03d8.d2bbSMTPIN_ADDED_MISSING@mx.google.com>
2020-03-17 18:08 ` Saravana Kannan
2020-03-17 18:18 ` Daniel Lezcano
2020-03-19 8:47 ` [tip: timers/core] clocksource/drivers/timer-probe: " tip-bot2 for Saravana Kannan
2020-03-24 17:59 ` Ionela Voinescu
2020-03-24 18:34 ` Saravana Kannan
2020-03-24 19:56 ` Saravana Kannan
2020-03-25 21:47 ` Thomas Gleixner [this message]
2020-03-25 22:56 ` Saravana Kannan
2020-03-25 23:06 ` Saravana Kannan
2020-03-26 10:17 ` Daniel Lezcano
2020-03-26 17:35 ` Saravana Kannan
2020-03-26 10:33 ` Thomas Gleixner
2020-03-26 15:02 ` Rob Herring
2020-03-26 18:08 ` Saravana Kannan
2020-03-28 2:23 ` Rob Herring
2020-03-25 21:29 ` Jon Hunter
2020-03-26 1:21 ` Dmitry Osipenko
2020-03-28 10:30 ` [tip: timers/core] Revert "clocksource/drivers/timer-probe: Avoid creating dead devices" tip-bot2 for Thomas Gleixner
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=87lfnoxg2a.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=ionela.voinescu@arm.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=saravanak@google.com \
--cc=sudeep.holla@arm.com \
--cc=x86@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