Patches for next

Patches for next

[Uwe Kleine-König]

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

Hello Thierry,

[I already sent this mail before, but failed to also send it to the
linux-pwm list. So here is a resend. Please ignore the first
submission.]

I saw you applied a few patches to your for-next branch. IMHO there are
some more that are ready for prime time:

 - [v2] pwm: Drop irrelevant error path from pwmchip_remove() 
   in (implicit) v1 you only had some concerns about the commit log.
   This is the same patch with an improved commit log.

 - [v2] pwm: Ensure for legacy drivers that pwm->state stays consistent
   this is a rework that improves behaviour for legacy drivers: It
   ensures that pwm->state is consistent even if a callback fails, it
   fixes a glitch when disabling and it adds tracing support en passant.

 - several cleanup series that improve individual drivers.
   (naming cleanup, conversion to .apply, stop checking the return code
   of pwmchip_remove()). There are series for
	- tiecap
	- berlin
	- pxa
	- stm32-lp
	- sprd
	- imx1

 - devm_pwmchip_add
   You had some doubts to my initial patch set that only converted one
   driver. In the meantime I identified and patched several drivers that
   can benefit from this function and simplified accordingly. This
   affects the following patches:

	- pwm: Add a devm managed function to add pwm_chips 
	- pwm: lpss: Simplify using devm_pwmchip_add 
	- [v2] pwm: meson: Simplify using devm_pwmchip_add 
	- pwm: clps711x: Simplify using devm_pwmchip_add() 
	- pwm: imx1: Simplify using devm_pwmchip_add() 
	- pwm: crc: Simplify using devm_pwmchip_add() 

It would be great if you would still consider these for the next merge
window or reply to these patches with your concerns.

Thanks
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]