From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755964Ab2CUIjU (ORCPT ); Wed, 21 Mar 2012 04:39:20 -0400 Received: from moutng.kundenserver.de ([212.227.126.187]:57337 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755640Ab2CUIjN (ORCPT ); Wed, 21 Mar 2012 04:39:13 -0400 From: Arnd Bergmann To: Bernhard Walle Subject: Re: [PATCH] mfd: Add TWL4030 PWM driver Date: Wed, 21 Mar 2012 08:39:06 +0000 User-Agent: KMail/1.12.2 (Linux/3.3.0-rc1; KDE/4.3.2; x86_64; ; ) Cc: Bernhard Walle , sameo@linux.intel.com, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, Thierry Reding References: <1332262083-9375-1-git-send-email-walle@corscience.de> <201203202202.12060.arnd@arndb.de> <4F697201.1090206@bwalle.de> In-Reply-To: <4F697201.1090206@bwalle.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201203210839.06258.arnd@arndb.de> X-Provags-ID: V02:K0:zwAiJQnRMo3AyuGHZvQOCbLiEQUVrJLHOy3RvWpRUG0 SfwVW6CVQJWTf0+dDN19I/YCQ/1tSbabCutuqNjVQq2h7I3NiL ClvkXjTMIRfHO5bO3oy5Adv+l/OMN/UH8uIR26jeVWVo7hQ9AN kefltg0Rn0u3omeF4Dm1yADv2CtlDlArNe66wSUVH+X+h8UmVD HVNWhm7oAHPxFydwDR/zg6L0rFzDgpeCwPwxGWZVyN0Y2yQVMz o0uGMijneJ3i9QNVPfSbGtO3ow3LncV5meUlUqwW2u4bK5afa5 45bDQkm3kzdBDSwNtJy/9BYoQNWZnlYZMkeex2aIISv+0i8Z/O e1wEgFJaChiUk0UX06Vs= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 21 March 2012, Bernhard Walle wrote: > Am 20.03.12 23:02, schrieb Arnd Bergmann: > > On Tuesday 20 March 2012, Bernhard Walle wrote: > >> > >> This PWM driver uses the PWM of the TWL4030. The driver for the TWL6030 > >> PWM has been used as mode, but the PWM registers are different. > >> > >> The driver can be used and has been tested in conjunction with > >> pwm-backlight to control a backlight LED of a LCD touch screen. > >> > >> Signed-off-by: Bernhard Walle > > > > Since it's too late for v3.4 now and we will get a new pwm > > subsystem in v3.5, I suggest you change the driver to work > > register with that subsystem instead of just using the old > > header file. Note that drivers/mfd is not really the right > > place anyway, because this is not a multifunction driver but > > just one device driver that happens to be a slave of an mfd. > > Does that new subsystem already exist in some tree? Thierry Reding has been busily posting patches, so he probably has one that you can use, but I couldn't find it now. Arnd