lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 27 May 2013 19:12:08 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	H Hartley Sweeten <hartleys@...ionengravers.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
	Ryan Mallon <rmallon@...il.com>,
	"mcrapet@...il.com" <mcrapet@...il.com>,
	Thierry Reding <thierry.reding@...onic-design.de>
Subject: Re: [PATCH 00/14] misc/ep93xx_pwm: cleanup driver for conversion to PWM framework

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ