devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: florian.vaussard@epfl.ch, 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: Thu, 7 Feb 2013 08:58:36 +0100	[thread overview]
Message-ID: <51135EAC.7010406@ti.com> (raw)
In-Reply-To: <51125AFC.10704@ti.com>

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).

I'm also waiting for 3.9-rc1 so I can finish up some of the pending things
regarding to PWMs.

-- 
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-02-07  7:58 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
     [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:42       ` Florian Vaussard
2013-01-24 15:45         ` Peter Ujfalusi
2013-01-24 16:50           ` Florian Vaussard
2013-01-24 17:08             ` Peter Ujfalusi
     [not found]               ` <51016A84.20703-l0cyMroinI0@public.gmane.org>
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
2013-02-07  7:58       ` Peter Ujfalusi [this message]
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=51135EAC.7010406@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=florian.vaussard@epfl.ch \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --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 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).