public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: NSP: Add PWM Support to DT
Date: Wed, 02 Mar 2016 16:28:54 +0100	[thread overview]
Message-ID: <4015342.1TJkp5X8uB@wuerfel> (raw)
In-Reply-To: <CAL2FKYkoXFm_pG6inxJqwkRqEK-TsMT2ndy4fgvQG1wT6AZ03Q@mail.gmail.com>

On Wednesday 02 March 2016 20:22:01 Yendapally Reddy Dhananjaya Reddy wrote:
> On Wed, Mar 2, 2016 at 1:55 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Tuesday 01 March 2016 12:42:49 Yendapally Reddy Dhananjaya Reddy wrote:
> >>                 };
> >>
> >> +               pwm: pwm at 31000 {
> >> +                       compatible = "brcm,iproc-pwm";
> >> +                       reg = <0x31000 0x28>;
> >> +                       clocks = <&osc>;
> >> +                       #pwm-cells = >;
> >> +                       status = "disabled";
> >> +               };
> >>
> >
> > Should this also list "brcm,kona-pwm" as compatible? From patch
> > 1, it sounds like that was the original one.
> 
> Arnd,
> 
> The NSP is a iProc based SoC and the pwm controller register offsets are
> slightly differ with the kona pwm controller. The compatible will be either
> "brcm,kona-pwm" or "brcm,iproc-pwm".

Ok, got it, thanks for the explanation.

	Arnd

       reply	other threads:[~2016-03-02 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAL2FKYkoXFm_pG6inxJqwkRqEK-TsMT2ndy4fgvQG1wT6AZ03Q@mail.gmail.com>
2016-03-02 15:28 ` Arnd Bergmann [this message]
2016-03-01 17:42 [PATCH 0/3] pwm support for Broadcom iProc SoC's Yendapally Reddy Dhananjaya Reddy
2016-03-01 17:42 ` [PATCH 3/3] ARM: dts: NSP: Add PWM Support to DT Yendapally Reddy Dhananjaya Reddy
2016-03-01 20:25   ` Arnd Bergmann

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=4015342.1TJkp5X8uB@wuerfel \
    --to=arnd@arndb.de \
    --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