From mboxrd@z Thu Jan 1 00:00:00 1970 From: Miquel Raynal Subject: Re: [PATCH] gpio: pca953x: Add Maxim MAX7313 PWM support Date: Tue, 5 Nov 2019 10:01:57 +0100 Message-ID: <20191105100157.2b6eb22b@xps13> References: <20191014124803.13661-1-miquel.raynal@bootlin.com> <20191015163055.0d8f44e5@xps13> <20191104161103.64995b8a@xps13> <20191104203346.epdbzflnynh2gf3z@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Andy Shevchenko Cc: Uwe =?UTF-8?B?S2xlaW5lLUvDtm5pZw==?= , Bartosz Golaszewski , Linus Walleij , Thierry Reding , "open list:GPIO SUBSYSTEM" , linux-pwm@vger.kernel.org, Linux Kernel Mailing List , Thomas Petazzoni , Sascha Hauer List-Id: linux-pwm@vger.kernel.org Hi Uwe, Andy Shevchenko wrote on Tue, 5 Nov 2019 09:06:37 +0200: > On Mon, Nov 4, 2019 at 10:33 PM Uwe Kleine-König > wrote: > > On Mon, Nov 04, 2019 at 04:32:23PM +0100, Bartosz Golaszewski wrote: > > > pon., 4 lis 2019 o 16:11 Miquel Raynal napisał(a): > > > > Andy Shevchenko wrote on Tue, 15 Oct 2019 > > > > 17:55:33 +0300: > > > > > > > > > Or other way around. PWM registers GPIO (which actually I prefer since > > > > > we have PCA9685 case where PWM provides GPIO functionality, though via > > > > > different means) > > > While it's not nice to have a driver that provides two different devices > > (here: gpio controller and pwm controller) similar things are not > > unseen. And for example the splitting of watchdog > > (drivers/watchdog/stmp3xxx_rtc_wdt.c) and rtc > > (drivers/rtc/rtc-stmp3xxx.c) of the device in the mx28 is more trouble > > than worth. > > > > So I'd vote for putting it in a single file that lives where the > > bigger/more complex part fits to. So assuming that's the GPIO part (as > > the driver supports several variants and not all of them have a PWM > > function if I'm not mistaken) having it in drivers/gpio is fine for me. > > For me it sounds more likely that PWM is a *pin function* of a pin > controller and actually this GPIO driver should be a pin controller > with corresponding function(s). > Ok, thanks for the input, I will address Thierry's comments and re-submit as a single file (same shape as in v1). Kind regards, Miquèl