From: Andreas Kemnade <andreas@kemnade•info>
To: Tony Lindgren <tony@atomide•com>
Cc: Ladislav Michl <ladis@linux-mips•org>,
"H . Nikolaus Schaller" <hns@goldelico•com>,
Daniel Lezcano <daniel.lezcano@linaro•org>,
linux-kernel@vger•kernel.org, Sebastian Reichel <sre@kernel•org>,
Tero Kristo <t-kristo@ti•com>,
Bartosz Golaszewski <bgolaszewski@baylibre•com>,
Andy Shevchenko <andy.shevchenko@gmail•com>,
Thierry Reding <thierry.reding@gmail•com>,
Pavel Machek <pavel@ucw•cz>, Keerthy <j-keerthy@ti•com>,
Thomas Gleixner <tglx@linutronix•de>,
linux-omap@vger•kernel.org, linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH 1/3] clocksource: timer-ti-dm: Fix pwm dmtimer usage of fck reparenting
Date: Sat, 26 Jan 2019 19:40:44 +0100 [thread overview]
Message-ID: <20190126194044.2fad4427@aktux> (raw)
In-Reply-To: <20190122175717.13428-2-tony@atomide.com>
[-- Attachment #1.1: Type: text/plain, Size: 842 bytes --]
On Tue, 22 Jan 2019 09:57:15 -0800
Tony Lindgren <tony@atomide•com> wrote:
> Commit 84badc5ec5fc ("ARM: dts: omap4: Move l4 child devices to probe
> them with ti-sysc") moved some omap4 timers to probe with ti-sysc
> interconnect target module. Turns out this broke pwm-omap-dmtimer
> where we now try to reparent the clock to itself with the following:
>
> omap_dm_timer_of_set_source: failed to set parent
>
> With ti-sysc, we can now configure the clock sources in the dts
> with assigned-clocks and assigned-clock-parents. So we should be able
> to remove omap_dm_timer_of_set_source with clean-up patches later on.
> But for now, let's just fix it first by checking if parent and fck
> are the same and bail out of so.
>
together with 2/3 it fixes things on pyra
Tested-By: Andreas Kemnade <andreas@kemnade•info>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 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:[~2019-01-26 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 17:57 [PATCH 0/3] pwm-omap-dmtimer regression fixes Tony Lindgren
2019-01-22 17:57 ` [PATCH 1/3] clocksource: timer-ti-dm: Fix pwm dmtimer usage of fck reparenting Tony Lindgren
2019-01-26 18:40 ` Andreas Kemnade [this message]
2019-01-26 19:30 ` H. Nikolaus Schaller
2019-02-12 9:08 ` Daniel Lezcano
2019-02-12 15:29 ` Tony Lindgren
2019-01-22 17:57 ` [PATCH 2/3] bus: ti-sysc: Fix timer handling with drop pm_runtime_irq_safe() Tony Lindgren
2019-01-26 18:41 ` Andreas Kemnade
2019-01-26 19:31 ` H. Nikolaus Schaller
2019-01-22 17:57 ` [PATCH 3/3] ARM: dts: Configure clock parent for pwm vibra 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=20190126194044.2fad4427@aktux \
--to=andreas@kemnade$(echo .)info \
--cc=andy.shevchenko@gmail$(echo .)com \
--cc=bgolaszewski@baylibre$(echo .)com \
--cc=daniel.lezcano@linaro$(echo .)org \
--cc=hns@goldelico$(echo .)com \
--cc=j-keerthy@ti$(echo .)com \
--cc=ladis@linux-mips$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=pavel@ucw$(echo .)cz \
--cc=sre@kernel$(echo .)org \
--cc=t-kristo@ti$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=thierry.reding@gmail$(echo .)com \
--cc=tony@atomide$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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