From: Tony Lindgren <tony@atomide.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-omap@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Jarkko Nikula" <jarkko.nikula@bitmer.com>
Subject: Re: [PATCH] ARM: dts: Fix timer regression for beagleboard revision c
Date: Mon, 29 Nov 2021 15:30:33 +0200 [thread overview]
Message-ID: <YaTV+UJjbD2HLnR9@atomide.com> (raw)
In-Reply-To: <6ce29c03-03ce-8e65-76e1-40fe2bf23caa@linaro.org>
Hi,
* Daniel Lezcano <daniel.lezcano@linaro.org> [211129 09:57]:
> On 25/11/2021 15:48, Tony Lindgren wrote:
> > .../devicetree/bindings/arm/omap/omap.txt | 3 ++
> > arch/arm/boot/dts/Makefile | 1 +
> > arch/arm/boot/dts/omap3-beagle-ab4.dts | 47 +++++++++++++++++++
> > arch/arm/boot/dts/omap3-beagle.dts | 33 -------------
> > drivers/clocksource/timer-ti-dm-systimer.c | 2 +-
> > 5 files changed, 52 insertions(+), 34 deletions(-)
> > create mode 100644 arch/arm/boot/dts/omap3-beagle-ab4.dts
>
> Usually, bindings DT and driver changes are separate patches
Not always for fixes :) In this case we need to patch both the dts for
timer quirks, and also update the related driver quirk. The driver quirk
I originally added to deal with possble older dtb files complicating the
fix unncessarily..
If you have better ideas for a fix please let me know.
Regards,
Tony
next prev parent reply other threads:[~2021-11-29 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 14:48 [PATCH] ARM: dts: Fix timer regression for beagleboard revision c Tony Lindgren
2021-11-28 18:43 ` Jarkko Nikula
2021-11-29 9:56 ` Daniel Lezcano
2021-11-29 13:30 ` Tony Lindgren [this message]
2021-12-11 15:30 ` Jarkko Nikula
2021-12-12 19:04 ` Jarkko Nikula
2021-12-13 5:43 ` Tony Lindgren
2021-12-17 12:17 ` Tony Lindgren
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=YaTV+UJjbD2HLnR9@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.