All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@avionic-design.de>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Shiraz Hashim <shiraz.hashim@st.com>,
	linux-kernel@vger.kernel.org, spear-devel@list.st.com,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH V3] PWM: Add SPEAr PWM chip driver support
Date: Mon, 22 Oct 2012 10:30:49 +0200	[thread overview]
Message-ID: <20121022083049.GA29790@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <CAKohpokDscKxhpKjdkbU+Q95VQPF-bDviyL3LAcbgeaQWk6ERw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

On Mon, Oct 22, 2012 at 01:55:29PM +0530, Viresh Kumar wrote:
> On 22 October 2012 13:25, Thierry Reding
> <thierry.reding@avionic-design.de> wrote:
> > We could probably do that in the core. I've had some discussions about
> > this with Lars-Peter (Cc'ed) who also had doubts about how this is
> > currently handled.
> >
> > What you're proposing is different, however. If we put that code in the
> > core it will mean that once the module is unloaded, all PWM devices will
> > be disabled. There is currently code in the core that prevents the chip
> > from being removed if one or more PWM devices are busy. But as explained
> > above, with the current core code this return value isn't useful at all.
> 
> This is what many drivers in pwm framework are doing currently too..
> They disable
> pwm and its clock and then do chip remove.
> 
> Sorry, i didn't get the conclusion completely :(
> Should we keep code suggested by me in core or spear's driver?

I think for now we can keep it in the SPEAr driver. I'll make sure to
refactor it out into the core once I have a good plan on how to solve
this issue properly.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-10-22  8:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22  3:51 [PATCH V3] PWM: Add SPEAr PWM chip driver support Shiraz Hashim
2012-10-22  4:09 ` viresh kumar
2012-10-22  6:06   ` Shiraz Hashim
2012-10-22  6:21     ` Viresh Kumar
2012-10-22  7:55       ` Thierry Reding
2012-10-22  8:25         ` Viresh Kumar
2012-10-22  8:30           ` Thierry Reding [this message]
2012-10-22 12:20         ` Lars-Peter Clausen
2012-10-24  5:54           ` 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=20121022083049.GA29790@avionic-0098.mockup.avionic-design.de \
    --to=thierry.reding@avionic-design.de \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shiraz.hashim@st.com \
    --cc=spear-devel@list.st.com \
    --cc=viresh.kumar@linaro.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 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.