From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: d.eppel@samsung.com
Cc: tglx@linutronix.de, kgene@kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, kyungmin.park@samsung.com,
k.kozlowski@samsung.com, m.jabrzyk@samsung.com,
stable@vger.kernel.org
Subject: Re: [PATCH v2] clocksource: exynos_mct: fix for sleeping in atomic ctx handling cpu hotplug notif.
Date: Wed, 27 May 2015 14:43:46 +0200 [thread overview]
Message-ID: <5565BC02.7010101@linaro.org> (raw)
In-Reply-To: <1432567470.13951.2.camel@AMDC1552.digital.local>
On 05/25/2015 05:24 PM, Damian Eppel wrote:
> On Mon, 2015-05-11 at 13:18 +0200, Daniel Lezcano wrote:
[ ... ]
>> The code sounds very complex for what it is supposed to do.
>>
>> Perhaps I am missing something but you have more or less the same
>> functionality than the smp_twd timers and these ones don't look so complex.
>>
>> Could you please look at the smp_twd.c implementation ?
>
> Hi Daniel,
>
> exynos_mct.c driver looks more complex as it supports two types of timer
> interrupts - private and shared peripheral interrupts (for exynos4412
> and exynos4210 accordingly). In smp_twd.c driver I can see only PPI type
> of irqs supported. SPI and PPI irqs differs slightly in setup - thus two
> different code paths appears in the driver in initialization and
> handling of CPU notifications. The fix is addressing issue that appears
> only for hardware using SPI irqs so it is hard to compare it to
> smp_twd.c.
> BTW, If we remove support for SPI irqs in exynos_mct.c it would look
> almost the same as smp_twd.c.
Ok, thanks.
I will have a deeper look this afternoon.
-- Daniel
--
<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
WARNING: multiple messages have this Message-ID (diff)
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] clocksource: exynos_mct: fix for sleeping in atomic ctx handling cpu hotplug notif.
Date: Wed, 27 May 2015 14:43:46 +0200 [thread overview]
Message-ID: <5565BC02.7010101@linaro.org> (raw)
In-Reply-To: <1432567470.13951.2.camel@AMDC1552.digital.local>
On 05/25/2015 05:24 PM, Damian Eppel wrote:
> On Mon, 2015-05-11 at 13:18 +0200, Daniel Lezcano wrote:
[ ... ]
>> The code sounds very complex for what it is supposed to do.
>>
>> Perhaps I am missing something but you have more or less the same
>> functionality than the smp_twd timers and these ones don't look so complex.
>>
>> Could you please look at the smp_twd.c implementation ?
>
> Hi Daniel,
>
> exynos_mct.c driver looks more complex as it supports two types of timer
> interrupts - private and shared peripheral interrupts (for exynos4412
> and exynos4210 accordingly). In smp_twd.c driver I can see only PPI type
> of irqs supported. SPI and PPI irqs differs slightly in setup - thus two
> different code paths appears in the driver in initialization and
> handling of CPU notifications. The fix is addressing issue that appears
> only for hardware using SPI irqs so it is hard to compare it to
> smp_twd.c.
> BTW, If we remove support for SPI irqs in exynos_mct.c it would look
> almost the same as smp_twd.c.
Ok, thanks.
I will have a deeper look this afternoon.
-- Daniel
--
<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:[~2015-05-27 12:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 9:11 [PATCH v2] clocksource: exynos_mct: fix for sleeping in atomic ctx handling cpu hotplug notif Damian Eppel
2015-03-12 9:11 ` Damian Eppel
2015-05-11 1:33 ` Krzysztof Kozlowski
2015-05-11 1:33 ` Krzysztof Kozlowski
2015-05-11 7:30 ` Daniel Lezcano
2015-05-11 7:30 ` Daniel Lezcano
2015-05-11 11:18 ` Daniel Lezcano
2015-05-11 11:18 ` Daniel Lezcano
2015-05-25 15:24 ` Damian Eppel
2015-05-25 15:24 ` Damian Eppel
2015-05-27 12:43 ` Daniel Lezcano [this message]
2015-05-27 12:43 ` Daniel Lezcano
2015-05-28 9:47 ` Marek Szyprowski
2015-05-28 9:47 ` Marek Szyprowski
2015-05-28 15:37 ` Damian Eppel
2015-05-28 15:37 ` Damian Eppel
2015-06-02 11:11 ` [PATCH v3] " Damian Eppel
2015-06-02 11:11 ` Damian Eppel
2015-06-26 13:23 ` [RESEND PATCH " Damian Eppel
2015-06-26 13:23 ` Damian Eppel
2015-06-26 19:54 ` [tip:timers/urgent] clocksource: exynos_mct: Avoid blocking calls in the cpu hotplug notifier tip-bot for Damian Eppel
2015-06-29 9:19 ` [RESEND PATCH v3] clocksource: exynos_mct: fix for sleeping in atomic ctx handling cpu hotplug notif Daniel Lezcano
2015-06-29 9:19 ` Daniel Lezcano
2015-06-29 9:24 ` Thomas Gleixner
2015-06-29 9:24 ` Thomas Gleixner
2015-06-29 10:14 ` Daniel Lezcano
2015-06-29 10:14 ` Daniel Lezcano
2015-06-29 11:50 ` Krzysztof Kozlowski
2015-06-29 11:50 ` Krzysztof Kozlowski
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=5565BC02.7010101@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=d.eppel@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.jabrzyk@samsung.com \
--cc=stable@vger.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.