From: Thierry Reding <thierry.reding@gmail.com>
To: Yendapally Reddy Dhananjaya Reddy <yendapally.reddy@broadcom.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Jon Mason <jonmason@broadcom.com>,
Russell King <linux@arm.linux.org.uk>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] pwm: iproc: Add support for Broadcom iproc pwm controller
Date: Mon, 11 Jul 2016 12:31:06 +0200 [thread overview]
Message-ID: <20160711103106.GA5503@ulmo.ba.sec> (raw)
In-Reply-To: <CAL2FKYkH86zhPOrEZQ8Q=WeKUV=2KFfxfA-JTrxiqMnCceQ87g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
On Mon, Jul 11, 2016 at 12:22:38PM +0530, Yendapally Reddy Dhananjaya Reddy wrote:
> Hi Thierry,
>
> On Fri, Jul 8, 2016 at 8:46 PM, Thierry Reding <thierry.reding@gmail.com> wrote:
> > On Tue, Jul 05, 2016 at 02:00:25AM -0400, Yendapally Reddy Dhananjaya Reddy wrote:
> >> Add support for the PWM controller present in Broadcom's iProc
> >> family of SoCs.It has been tested on the Northstar+ bcm958625HR board.
> >>
> >> Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yendapally.reddy@broadcom.com>
> >> ---
> >> drivers/pwm/Kconfig | 10 ++
> >> drivers/pwm/Makefile | 1 +
> >> drivers/pwm/pwm-bcm-iproc.c | 268 ++++++++++++++++++++++++++++++++++++++++++++
> >> 3 files changed, 279 insertions(+)
> >> create mode 100644 drivers/pwm/pwm-bcm-iproc.c
> >
> > I've applied this, but I had to make a couple of changes for coding
> > style and to squash compiler warnings. Please check the PWM tree's
> > for-next branch to see if it still works for you.
> >
>
> Thanks. It is working fine for me. A small change is required here,
> NSEC_PER_SEC
> instead of USEC_PER_SEC in two places.
Ah yes, I had mixed those up when converting from literal to symbolic.
Should be fixed now.
Thanks,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/3] pwm: iproc: Add support for Broadcom iproc pwm controller
Date: Mon, 11 Jul 2016 12:31:06 +0200 [thread overview]
Message-ID: <20160711103106.GA5503@ulmo.ba.sec> (raw)
In-Reply-To: <CAL2FKYkH86zhPOrEZQ8Q=WeKUV=2KFfxfA-JTrxiqMnCceQ87g@mail.gmail.com>
On Mon, Jul 11, 2016 at 12:22:38PM +0530, Yendapally Reddy Dhananjaya Reddy wrote:
> Hi Thierry,
>
> On Fri, Jul 8, 2016 at 8:46 PM, Thierry Reding <thierry.reding@gmail.com> wrote:
> > On Tue, Jul 05, 2016 at 02:00:25AM -0400, Yendapally Reddy Dhananjaya Reddy wrote:
> >> Add support for the PWM controller present in Broadcom's iProc
> >> family of SoCs.It has been tested on the Northstar+ bcm958625HR board.
> >>
> >> Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yendapally.reddy@broadcom.com>
> >> ---
> >> drivers/pwm/Kconfig | 10 ++
> >> drivers/pwm/Makefile | 1 +
> >> drivers/pwm/pwm-bcm-iproc.c | 268 ++++++++++++++++++++++++++++++++++++++++++++
> >> 3 files changed, 279 insertions(+)
> >> create mode 100644 drivers/pwm/pwm-bcm-iproc.c
> >
> > I've applied this, but I had to make a couple of changes for coding
> > style and to squash compiler warnings. Please check the PWM tree's
> > for-next branch to see if it still works for you.
> >
>
> Thanks. It is working fine for me. A small change is required here,
> NSEC_PER_SEC
> instead of USEC_PER_SEC in two places.
Ah yes, I had mixed those up when converting from literal to symbolic.
Should be fixed now.
Thanks,
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160711/b1d1a522/attachment.sig>
next prev parent reply other threads:[~2016-07-11 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 6:52 [PATCH v5 2/3] pwm: iproc: Add support for Broadcom iproc pwm controller Yendapally Reddy Dhananjaya Reddy
2016-07-11 10:31 ` Thierry Reding [this message]
2016-07-11 10:31 ` Thierry Reding
-- strict thread matches above, loose matches on Subject: below --
2016-07-05 6:00 [PATCH v5 0/3] pwm support for Broadcom iProc SoC's Yendapally Reddy Dhananjaya Reddy
[not found] ` <1467698426-27600-1-git-send-email-yendapally.reddy-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-07-05 6:00 ` [PATCH v5 2/3] pwm: iproc: Add support for Broadcom iproc pwm controller Yendapally Reddy Dhananjaya Reddy
2016-07-05 6:00 ` Yendapally Reddy Dhananjaya Reddy
2016-07-05 6:00 ` Yendapally Reddy Dhananjaya Reddy
2016-07-08 15:16 ` Thierry Reding
2016-07-08 15:16 ` Thierry Reding
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=20160711103106.GA5503@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jonmason@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=yendapally.reddy@broadcom.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.