public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	Ryan Mallon <rmallon@gmail.com>,
	"mcrapet@gmail.com" <mcrapet@gmail.com>,
	Thierry Reding <thierry.reding@avionic-design.de>
Subject: Re: [PATCH 00/14] misc/ep93xx_pwm: cleanup driver for conversion to PWM framework
Date: Mon, 27 May 2013 19:12:08 +0200	[thread overview]
Message-ID: <201305271912.08882.arnd@arndb.de> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F0021DA666D43D@AUSP01VMBX24.collaborationhost.net>

On Monday 27 May 2013, H Hartley Sweeten wrote:
> Ryan Mallon has also provided a Reviewed-by for this series.
> 
> Will you be the one that merges this? I would like it to be in linux-next
> before I convert it to the PWM framework.

While Greg and I are both maintainers for drivers/misc, he is the one who
actually has a git tree for it, so he would merge it.

However, I think it would be better to just merge it all through the pwm
tree. Your current series is good, and with my Ack I see no problem to
just do the conversion to pwm on top and send a pull request for all of
it to Thierry.

> Also, I have a question about the conversion.
> 
> If I strip the sysfs support out of this driver the conversion is quite simple.
> But, my use for this driver requires user space control of the PWM.
> 
> Should I:
> 1) convert the driver to the PWM framework and leave the sysfs stuff in it
> 2) work out a generic sysfs support for the PWM framework and then
>     convert the driver
> 3) other...
>
> I've been looking at 2) by doing something like how gpiolib does it. Do
> you think that would be acceptable?

That would be for Thierry to decide. It does sound better to me than the 1)
and I don't have a better idea for 3).

I wonder how the arbitration between in-kernel and user-space consumers
of the pwm lines would work though.

	Arnd

  reply	other threads:[~2013-05-27 17:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 23:19 [PATCH 00/14] misc/ep93xx_pwm: cleanup driver for conversion to PWM framework H Hartley Sweeten
2013-05-26 23:32 ` Ryan Mallon
2013-05-27 15:20 ` Arnd Bergmann
2013-05-27 16:27   ` H Hartley Sweeten
2013-05-27 17:12     ` Arnd Bergmann [this message]
2013-05-28 11:00       ` Thierry Reding
2013-05-28 11:42         ` Lars Poeschel
2013-05-29 21:33           ` H Hartley Sweeten
2013-05-30 11:41             ` 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=201305271912.08882.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hartleys@visionengravers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcrapet@gmail.com \
    --cc=rmallon@gmail.com \
    --cc=thierry.reding@avionic-design.de \
    /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