All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Vaussard <florian.vaussard@epfl.ch>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Benoit Cousson <b-cousson@ti.com>,
	Tony Lindgren <tony@atomide.com>,
	linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: dts: omap3-overo: Add pwm-leds and audio support
Date: Tue, 26 Feb 2013 17:07:36 +0100	[thread overview]
Message-ID: <512CDDC8.6030307@epfl.ch> (raw)
In-Reply-To: <51135EAC.7010406@ti.com>

Hi,

On 02/07/2013 08:58 AM, Peter Ujfalusi wrote:
> Hi,
>
> On 02/06/2013 02:30 PM, Benoit Cousson wrote:
>>> 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.
>
> In this series the 'linux,default-trigger' property is not added to the
> pwm-leds node, so it is safe to take this series.
> I'm sure Florian will send the update to add this flag back for 3.10 or for
> 3.9-rc (the needed patches for PWM and leds-pwm will be in 3.9).
>

Yes, it is safe to take this series. I will provide a patch to add back
the trigger when it is safe to.

Regards,

Florian

WARNING: multiple messages have this Message-ID (diff)
From: florian.vaussard@epfl.ch (Florian Vaussard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: dts: omap3-overo: Add pwm-leds and audio support
Date: Tue, 26 Feb 2013 17:07:36 +0100	[thread overview]
Message-ID: <512CDDC8.6030307@epfl.ch> (raw)
In-Reply-To: <51135EAC.7010406@ti.com>

Hi,

On 02/07/2013 08:58 AM, Peter Ujfalusi wrote:
> Hi,
>
> On 02/06/2013 02:30 PM, Benoit Cousson wrote:
>>> 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.
>
> In this series the 'linux,default-trigger' property is not added to the
> pwm-leds node, so it is safe to take this series.
> I'm sure Florian will send the update to add this flag back for 3.10 or for
> 3.9-rc (the needed patches for PWM and leds-pwm will be in 3.9).
>

Yes, it is safe to take this series. I will provide a patch to add back
the trigger when it is safe to.

Regards,

Florian

  reply	other threads:[~2013-02-26 16:07 UTC|newest]

Thread overview: 42+ 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 ` Florian Vaussard
2013-01-23 17:56 ` [PATCH 1/2] ARM: dts: omap3-overo: Add support for pwm-leds Florian Vaussard
2013-01-23 17:56   ` Florian Vaussard
     [not found]   ` <1358963812-19947-2-git-send-email-florian.vaussard-p8DiymsW2f8@public.gmane.org>
2013-01-24 15:19     ` Peter Ujfalusi
2013-01-24 15:19       ` Peter Ujfalusi
2013-01-24 15:42       ` Florian Vaussard
2013-01-24 15:42         ` Florian Vaussard
2013-01-24 15:45         ` Peter Ujfalusi
2013-01-24 15:45           ` Peter Ujfalusi
2013-01-24 16:50           ` Florian Vaussard
2013-01-24 16:50             ` Florian Vaussard
2013-01-24 17:08             ` Peter Ujfalusi
2013-01-24 17:08               ` Peter Ujfalusi
     [not found]               ` <51016A84.20703-l0cyMroinI0@public.gmane.org>
2013-01-24 21:14                 ` Florian Vaussard
2013-01-24 21:14                   ` Florian Vaussard
2013-01-25  8:29                   ` Peter Ujfalusi
2013-01-25  8:29                     ` Peter Ujfalusi
2013-01-25 12:07                     ` Peter Ujfalusi
2013-01-25 12:07                       ` Peter Ujfalusi
2013-01-25 12:21                       ` Florian Vaussard
2013-01-25 12:21                         ` Florian Vaussard
2013-01-25 12:30                         ` Peter Ujfalusi
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-23 17:56   ` Florian Vaussard
2013-01-24 15:21   ` Peter Ujfalusi
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-01-24 12:21   ` Benoit Cousson
2013-02-04  9:14   ` Florian Vaussard
2013-02-04  9:14     ` Florian Vaussard
2013-02-06 13:30     ` Benoit Cousson
2013-02-06 13:30       ` Benoit Cousson
2013-02-06 14:26       ` Philippe Rétornaz
2013-02-06 14:26         ` Philippe Rétornaz
2013-02-07  7:58       ` Peter Ujfalusi
2013-02-07  7:58         ` Peter Ujfalusi
2013-02-26 16:07         ` Florian Vaussard [this message]
2013-02-26 16:07           ` Florian Vaussard
2013-02-26 16:19           ` Benoit Cousson
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=512CDDC8.6030307@epfl.ch \
    --to=florian.vaussard@epfl.ch \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@ti.com \
    --cc=tony@atomide.com \
    /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.