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
| ||
|
Message-ID: <20140606124230.GQ24240@lee--X1> Date: Fri, 6 Jun 2014 13:42:30 +0100 From: Lee Jones <lee.jones@...aro.org> To: Lothar Waßmann <LW@...O-electronics.de> Cc: Bryan Wu <cooloney@...il.com>, Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>, Jingoo Han <jg1.han@...sung.com>, Thierry Reding <thierry.reding@...il.com>, Tomi Valkeinen <tomi.valkeinen@...com>, linux-fbdev@...r.kernel.org, linux-kernel@...r.kernel.org, linux-pwm@...r.kernel.org Subject: Re: [PATCH] pwm-backlight: On Fri, 06 Jun 2014, Lothar Waßmann wrote: > commit 257462dbf3ed pwm-backlight: switch to gpiod interface > introduced a regression leading to acquiring a bogus GPIO-0 when > configured from DT without an 'enable-gpios' property. > The driver will happily accept the 0 initialized 'enable_gpio' member > of the struct platform_pwm_backlight_data as valid gpio number, and > request this GPIO as enable pin. In case of multiple driver instances, > the second will fail to register with the error message: > pwm-backlight backlight1.23: failed to request GPIO#0: -16 > > Fix this by setting enable_gpio in the pdata struct to -EINVAL. > > Signed-off-by: Lothar Waßmann <LW@...O-electronics.de> > --- > drivers/video/backlight/pwm_bl.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c > index 38ca88b..3d265c4 100644 > --- a/drivers/video/backlight/pwm_bl.c > +++ b/drivers/video/backlight/pwm_bl.c > @@ -178,7 +178,7 @@ static int pwm_backlight_parse_dt(struct device *dev, > data->dft_brightness = value; > data->max_brightness--; > } > - > + data->enable_gpio = -EINVAL; > return 0; > } This patch doesn't look like it will apply. I suggest you pull v3.17-rc1 when it lands and rebase your patch. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- 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