From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
Shawn Guo <shawn.guo@linaro.org>,
Sascha Hauer <kernel@pengutronix.de>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCHv3 1/3] pwm: make the PWM_POLARITY flag in DTB optional
Date: Tue, 8 Apr 2014 07:02:59 +0200 [thread overview]
Message-ID: <20140408070259.68923987@ipc1.ka-ro> (raw)
In-Reply-To: <20140407113652.GE26985@ulmo>
Hi,
Thierry Reding wrote:
> On Wed, Apr 02, 2014 at 07:53:50AM +0200, Sascha Hauer wrote:
> > On Fri, Mar 28, 2014 at 09:48:58AM +0100, Lothar Waßmann wrote:
> [...]
> > > @@ -183,8 +173,11 @@ static void of_pwmchip_add(struct pwm_chip *chip)
> > > return;
> > >
> > > if (!chip->of_xlate) {
> > > - chip->of_xlate = of_pwm_simple_xlate;
> > > - chip->of_pwm_n_cells = 2;
> > > + chip->of_xlate = of_pwm_xlate;
> > > + if (chip->ops->set_polarity)
> > > + chip->of_pwm_n_cells = 3;
> > > + else
> > > + chip->of_pwm_n_cells = 2;
> >
> > I think the presence of the set_polarity callback shouldn't influence
> > the number of cells the parser expects. As commented on 2/2 this doesn't
> > actually mean the device actually support polarity inversion.
>
> How so? A driver should only implement .set_polarity() if it supports
> changing the polarity.
>
> That said, I agree that the presence of .set_polarity() shouldn't
> determine the number of cells. You could have any number of other flags
> set via the third cell.
>
> > Also, polarity inversion could still be done in software for hardware
> > that doesn't support it.
>
> No. You cannot emulate polarity inversion in software.
>
Why not?
duty_ns = period_ns - duty_ns;
Lothar Waßmann
--
___________________________________________________________
Ka-Ro electronics GmbH | Pascalstraße 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Geschäftsführer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996
www.karo-electronics.de | info@karo-electronics.de
___________________________________________________________
next prev parent reply other threads:[~2014-04-08 5:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 13:22 pwm: imx: support output polarity inversion Lothar Waßmann
2014-03-19 13:22 ` [PATCHv3 1/3] pwm: make the PWM_POLARITY flag in DTB optional Lothar Waßmann
2014-03-19 13:22 ` [PATCHv3 2/3] pwm: imx: indentation cleanup Lothar Waßmann
2014-03-19 13:22 ` [PATCHv3 3/3] pwm: imx: support output polarity inversion Lothar Waßmann
2014-03-28 8:48 ` [PATCHv3 0/3] " Lothar Waßmann
2014-03-28 8:48 ` [PATCHv3 1/3] pwm: make the PWM_POLARITY flag in DTB optional Lothar Waßmann
2014-04-02 5:53 ` Sascha Hauer
2014-04-07 11:36 ` Thierry Reding
2014-04-08 5:02 ` Lothar Waßmann [this message]
2014-04-08 20:43 ` Tim Kryger
2014-04-09 6:12 ` Sascha Hauer
2014-04-09 7:22 ` Thierry Reding
2014-04-10 5:55 ` Sascha Hauer
[not found] ` <CAAYSxhpL_0FJvuvGODMTZDm7DtK3eBTVYdhf1Ot7PW94gSM8iw@mail.gmail.com>
2014-04-09 6:04 ` Lothar Waßmann
2014-04-09 7:16 ` Thierry Reding
2014-03-28 8:48 ` [PATCHv3 2/3] pwm: imx: indentation cleanup Lothar Waßmann
2014-03-28 8:49 ` [PATCHv3 3/3] pwm: imx: support output polarity inversion Lothar Waßmann
2014-04-02 5:45 ` Sascha Hauer
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=20140408070259.68923987@ipc1.ka-ro \
--to=lw@karo-electronics.de \
--cc=arnd@arndb.de \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®