linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/3] ARM: davinci: da850: add EHRPWM & ECAP DT node
Date: Tue, 9 Apr 2013 17:05:25 +0530	[thread overview]
Message-ID: <5163FCFD.6070606@ti.com> (raw)
In-Reply-To: <518397C60809E147AF5323E0420B992E3EAA9DA3@DBDE01.ent.ti.com>

On 4/9/2013 2:12 PM, Philip, Avinash wrote:
> On Mon, Apr 08, 2013 at 18:39:57, Nori, Sekhar wrote:
>>
>> On 4/8/2013 2:39 PM, Philip, Avinash wrote:
>>> On Tue, Apr 02, 2013 at 14:03:34, Nori, Sekhar wrote:
>>>> On 3/25/2013 1:19 PM, Philip Avinash wrote:
>>>>> Add da850 EHRPWM & ECAP DT node.
>>>>> Also adds OF_DEV_AUXDATA for EHRPWM & ECAP driver to use EHRPWM & ECAP
>>>>> clock.
>>>>
>>>> This looks fine to me but I will wait for the bindings to get accepted
>>>> before taking this one.
>>>
>>> Sekhar,
>>>
>>> Binding document got accepted in PWM tree [1].
>>> Can you accept this patch?
>>
>> Can you also add the pinmux definitions and resend just this patch?
>> Sorry I did not notice those were missing earlier.
> 
> According to latest schematics, ECAP instance 2 being used for PWM backlight
> control. Should I add pin-mux only for ECAP2 or for all PWM instances?

I meant add definitions in .dtsi. Since there is only one pin a given
functionality can be present on in DaVinci, it can be done in a board
independent manner. See examples for other peripherals in existing
da850.dtsi file.

Thanks,
Sekhar

  reply	other threads:[~2013-04-09 11:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  7:49 [PATCH v3 0/3] Platform support for EHRPWM & ECAP devices in DAVINCI Philip Avinash
2013-03-25  7:49 ` [PATCH v3 2/3] arm: davinci: clock node support for ECAP & EHRPWM Philip Avinash
2013-04-02  8:16   ` Sekhar Nori
2013-03-25  7:49 ` [PATCH v3 3/3] ARM: davinci: da850: add EHRPWM & ECAP DT node Philip Avinash
2013-04-02  8:33   ` Sekhar Nori
2013-04-08  9:09     ` Philip, Avinash
2013-04-08 13:09       ` Sekhar Nori
2013-04-09  8:42         ` Philip, Avinash
2013-04-09 11:35           ` Sekhar Nori [this message]
2013-04-10  5:30             ` Philip, Avinash
2013-04-10  5:55               ` Sekhar Nori
2013-04-10  6:07                 ` Philip, Avinash
2013-03-25  8:14 ` [PATCH v3 0/3] Platform support for EHRPWM & ECAP devices in DAVINCI Sekhar Nori
2013-03-25  8:30   ` Philip, Avinash
2013-03-25  9:37 ` [PATCH v3 1/3] ARM: davinci: clk framework support for enable/disable functionality Philip Avinash
2013-04-01 11:35   ` Sekhar Nori
2013-04-03  3:58     ` Philip, Avinash
2013-04-02  8:35 ` [PATCH v3 0/3] Platform support for EHRPWM & ECAP devices in DAVINCI Sekhar Nori
2013-04-04  4:39   ` Philip, Avinash
2013-04-04  5:49     ` Sekhar Nori
2013-04-04  6:38       ` Philip, Avinash
2013-04-04 10:10       ` Philip, Avinash

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=5163FCFD.6070606@ti.com \
    --to=nsekhar@ti.com \
    --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).