From: philippe.retornaz@epfl.ch (Philippe Rétornaz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: dts: omap3-overo: Add pwm-leds and audio support
Date: Wed, 06 Feb 2013 15:26:43 +0100 [thread overview]
Message-ID: <51126823.6070605@epfl.ch> (raw)
In-Reply-To: <51125AFC.10704@ti.com>
Hi all !
Le 06/02/2013 14:30, Benoit Cousson a ?crit :
> Salut Florian,
>
> On 02/04/2013 10:14 AM, Florian Vaussard wrote:
>> Hello Benoit,
>>
>> On 01/24/2013 01:21 PM, Benoit Cousson wrote:
>>> + Peter who did the original PWM
>>>
>>> Hi Florian,
>>>
>>> On 01/23/2013 06:56 PM, Florian Vaussard wrote:
>>>> Hello Benoit,
>>>>
>>>> This patchset adds some new DT supports to the Overo products.
>>>> The first patch converts the PMIC LEDB output to use the
>>>> pwm-leds, newly merged in your branch for_3.9/dts. The second
>>>> patch adds the audio support.
>>>
>>> Excellent, that looks very good to me, but I'd like to get the
>>> feedback from Peter before merging it.
>>>
>>
>> So a patch is being merged to handle triggers in the case of pwm
>> leds [1]. When done, we will be able to add back the default
>> trigger. Do you want to wait on it to merge this series?
>
> What kind of dependency do we have between these two series? I mean
> what will happen if the DTS is merged before the pwm subsystem?
>
> If that does not generate any regression / crash, then it is OK, if
> not, we should take care of the order.
Florian is on holiday the next two weeks.
AFAIK if the PWM/leds subsystem patches are not merged before this one
then the kernel will panic if a trigger is used to change the led status.
Regards,
Philippe
next prev parent reply other threads:[~2013-02-06 14:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 17:56 [PATCH 0/2] ARM: dts: omap3-overo: Add pwm-leds and audio support Florian Vaussard
2013-01-23 17:56 ` [PATCH 1/2] ARM: dts: omap3-overo: Add support for pwm-leds Florian Vaussard
2013-01-24 15:19 ` Peter Ujfalusi
2013-01-24 15:42 ` Florian Vaussard
2013-01-24 15:45 ` Peter Ujfalusi
2013-01-24 16:50 ` Florian Vaussard
2013-01-24 17:08 ` Peter Ujfalusi
2013-01-24 21:14 ` Florian Vaussard
2013-01-25 8:29 ` Peter Ujfalusi
2013-01-25 12:07 ` Peter Ujfalusi
2013-01-25 12:21 ` Florian Vaussard
2013-01-25 12:30 ` Peter Ujfalusi
2013-01-23 17:56 ` [PATCH 2/2] ARM: dts: omap3-overo: Add audio support Florian Vaussard
2013-01-24 15:21 ` Peter Ujfalusi
2013-01-24 12:21 ` [PATCH 0/2] ARM: dts: omap3-overo: Add pwm-leds and " Benoit Cousson
2013-02-04 9:14 ` Florian Vaussard
2013-02-06 13:30 ` Benoit Cousson
2013-02-06 14:26 ` Philippe Rétornaz [this message]
2013-02-07 7:58 ` Peter Ujfalusi
2013-02-26 16:07 ` Florian Vaussard
2013-02-26 16:19 ` Benoit Cousson
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=51126823.6070605@epfl.ch \
--to=philippe.retornaz@epfl.ch \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).