diff for duplicates of <20160610145449.GA7351@dell> diff --git a/a/1.txt b/N1/1.txt index f20ada9..ee16eb6 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -11,9 +11,9 @@ On Fri, 10 Jun 2016, Lothar Waßmann wrote: > > > > > where the value at index 0 may well be non-zero > > > > > (tegra30-apalis-eval.dts and tegra30-colibri-eval-v3.dts are real-life > > > > > examples). -> > > > > Thus brightness = 0 does not necessarily mean that the PWM output +> > > > > Thus brightness == 0 does not necessarily mean that the PWM output > > > > > will be inactive. -> > > > > Check for 'duty_cycle = 0' rather than 'brightness = 0' to decide +> > > > > Check for 'duty_cycle == 0' rather than 'brightness == 0' to decide > > > > > whether to disable the PWM. > > > > > > > > > > Signed-off-by: Lothar Waßmann <LW@KARO-electronics.de> @@ -79,8 +79,8 @@ On Fri, 10 Jun 2016, Lothar Waßmann wrote: > > someone is going to get screwed by this logic. > > > The backlight framework does not (and does not need to) know anything -> about PWM duty cycles. Its 'brightness' values are consistently 0 = -> dark, max = brightest in either case. +> about PWM duty cycles. Its 'brightness' values are consistently 0 == +> dark, max == brightest in either case. What I'm getting at is; by the look of the documentation, the brightest setting can either be a duty cycle of 0 or 255. So what diff --git a/a/content_digest b/N1/content_digest index 7225219..3fe1431 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,7 +5,7 @@ "ref\020160610123453.3a8ee14e@ipc1.ka-ro\0" "From\0Lee Jones <lee.jones@linaro.org>\0" "Subject\0Re: [PATCHv2] backlight: pwm_bl: disable PWM when 'duty_cycle' is zero\0" - "Date\0Fri, 10 Jun 2016 14:54:49 +0000\0" + "Date\0Fri, 10 Jun 2016 15:54:49 +0100\0" "To\0Lothar Wa\303\237mann <LW@karo-electronics.de>\0" "Cc\0Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>" Jingoo Han <jingoohan1@gmail.com> @@ -36,9 +36,9 @@ "> > > > > where the value at index 0 may well be non-zero\n" "> > > > > (tegra30-apalis-eval.dts and tegra30-colibri-eval-v3.dts are real-life\n" "> > > > > examples).\n" - "> > > > > Thus brightness = 0 does not necessarily mean that the PWM output\n" + "> > > > > Thus brightness == 0 does not necessarily mean that the PWM output\n" "> > > > > will be inactive.\n" - "> > > > > Check for 'duty_cycle = 0' rather than 'brightness = 0' to decide\n" + "> > > > > Check for 'duty_cycle == 0' rather than 'brightness == 0' to decide\n" "> > > > > whether to disable the PWM.\n" "> > > > > \n" "> > > > > Signed-off-by: Lothar Wa\303\237mann <LW@KARO-electronics.de>\n" @@ -104,8 +104,8 @@ "> > someone is going to get screwed by this logic.\n" "> > \n" "> The backlight framework does not (and does not need to) know anything\n" - "> about PWM duty cycles. Its 'brightness' values are consistently 0 =\n" - "> dark, max = brightest in either case.\n" + "> about PWM duty cycles. Its 'brightness' values are consistently 0 ==\n" + "> dark, max == brightest in either case.\n" "\n" "What I'm getting at is; by the look of the documentation, the\n" "brightest setting can either be a duty cycle of 0 or 255. So what\n" @@ -119,4 +119,4 @@ "Linaro.org \342\224\202 Open source software for ARM SoCs\n" Follow Linaro: Facebook | Twitter | Blog -fc86cc8b35ce5935cdeb9c86b541a232d7aff1e6b5a54ef774073884d90cb7b2 +d73038385072d45fbc2a28d25812245600cb5d761bea82103e62d07efb58887d
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.