From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-fbdev@vger.kernel.org, linux-pwm@vger.kernel.org,
Jingoo Han <jg1.han@samsung.com>, Bryan Wu <cooloney@gmail.com>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH 1/2] backlight: pwm: don't call legacy pwm request for device defined in dt
Date: Mon, 01 Dec 2014 14:47:38 +0000 [thread overview]
Message-ID: <547C7F8A.40707@mentor.com> (raw)
In-Reply-To: <545CDDF5.70905@mentor.com>
Hello Thierry,
On 07.11.2014 16:57, Vladimir Zapolskiy wrote:
> Thierry,
>
> On 07.11.2014 16:19, Vladimir Zapolskiy wrote:
>> Hi Thierry,
>>
>> On 07.11.2014 15:48, Thierry Reding wrote:
>>> On Sat, Oct 11, 2014 at 04:46:25PM +0300, Vladimir Zapolskiy wrote:
>>>> Platform PWM backlight data provided by board's device tree should be
>>>> complete enough to successfully request a pwm device using pwm_get() API.
>>>>
>>>> Based on initial implementation done by Dmitry Eremin-Solenikov.
>>>>
>>>> Reported-by: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com>
>>>> Signed-off-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
>>>> Cc: Thierry Reding <thierry.reding@gmail.com>
>>>> Cc: Jingoo Han <jg1.han@samsung.com>
>>>> Cc: Bryan Wu <cooloney@gmail.com>
>>>> Cc: Lee Jones <lee.jones@linaro.org>
>>>> ---
>>>> drivers/video/backlight/pwm_bl.c | 14 +++++++-------
>>>> 1 file changed, 7 insertions(+), 7 deletions(-)
>>>
>>> I don't really understand what this is supposed to do. The commit
>>> message doesn't make a very good job of explaining it either.
>>>
>>> Can you describe in more detail what problem this fixes and why it
>>> should be merged?
>>
>> thank you for review.
>>
>> As it is shown by the code this particular change rejects fallback to
>> legacy PWM device request (which itself in turn is fixed in the next
>> commit) for boards with supplied DTS, "pwm-backlight" compatible node
>> and unregistered corresponding PWM device in that node.
>>
>> I don't know if there is a good enough reason to register PWM backlight
>> device connected to some quite arbitrary PWM device, if no PWM device
>> information is given in the "pwm-backlight" compatible node, so I think
>> it makes sense to change the default policy.
>>
>
> also please note that
> Documentation/devicetree/bindings/video/backlight/pwm-backlight.txt
> quite fairly describes "pwms" as a required property, but right now this
> statement from the documentation is wrong, it is possible to register
> pwm-backlight device driver (using notorious pwm_request() legacy API)
> connected to some unspecified pwm device.
>
> I don't think that the current registration policy is correct, that's
> why I propose to fix the logic instead of making a documentation update.
>
have you had a chance to check the rationale of the change?
If you accept it, should I make the commit message more verbose?
--
With best wishes,
Vladimir
WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-fbdev@vger.kernel.org, linux-pwm@vger.kernel.org,
Jingoo Han <jg1.han@samsung.com>, Bryan Wu <cooloney@gmail.com>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH 1/2] backlight: pwm: don't call legacy pwm request for device defined in dt
Date: Mon, 1 Dec 2014 16:47:38 +0200 [thread overview]
Message-ID: <547C7F8A.40707@mentor.com> (raw)
In-Reply-To: <545CDDF5.70905@mentor.com>
Hello Thierry,
On 07.11.2014 16:57, Vladimir Zapolskiy wrote:
> Thierry,
>
> On 07.11.2014 16:19, Vladimir Zapolskiy wrote:
>> Hi Thierry,
>>
>> On 07.11.2014 15:48, Thierry Reding wrote:
>>> On Sat, Oct 11, 2014 at 04:46:25PM +0300, Vladimir Zapolskiy wrote:
>>>> Platform PWM backlight data provided by board's device tree should be
>>>> complete enough to successfully request a pwm device using pwm_get() API.
>>>>
>>>> Based on initial implementation done by Dmitry Eremin-Solenikov.
>>>>
>>>> Reported-by: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com>
>>>> Signed-off-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
>>>> Cc: Thierry Reding <thierry.reding@gmail.com>
>>>> Cc: Jingoo Han <jg1.han@samsung.com>
>>>> Cc: Bryan Wu <cooloney@gmail.com>
>>>> Cc: Lee Jones <lee.jones@linaro.org>
>>>> ---
>>>> drivers/video/backlight/pwm_bl.c | 14 +++++++-------
>>>> 1 file changed, 7 insertions(+), 7 deletions(-)
>>>
>>> I don't really understand what this is supposed to do. The commit
>>> message doesn't make a very good job of explaining it either.
>>>
>>> Can you describe in more detail what problem this fixes and why it
>>> should be merged?
>>
>> thank you for review.
>>
>> As it is shown by the code this particular change rejects fallback to
>> legacy PWM device request (which itself in turn is fixed in the next
>> commit) for boards with supplied DTS, "pwm-backlight" compatible node
>> and unregistered corresponding PWM device in that node.
>>
>> I don't know if there is a good enough reason to register PWM backlight
>> device connected to some quite arbitrary PWM device, if no PWM device
>> information is given in the "pwm-backlight" compatible node, so I think
>> it makes sense to change the default policy.
>>
>
> also please note that
> Documentation/devicetree/bindings/video/backlight/pwm-backlight.txt
> quite fairly describes "pwms" as a required property, but right now this
> statement from the documentation is wrong, it is possible to register
> pwm-backlight device driver (using notorious pwm_request() legacy API)
> connected to some unspecified pwm device.
>
> I don't think that the current registration policy is correct, that's
> why I propose to fix the logic instead of making a documentation update.
>
have you had a chance to check the rationale of the change?
If you accept it, should I make the commit message more verbose?
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2014-12-01 14:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 13:46 [PATCH 0/2] backlight: pwm: fix oops on accessing removed legacy pwm device Vladimir Zapolskiy
2014-10-11 13:46 ` Vladimir Zapolskiy
2014-10-11 13:46 ` [PATCH 1/2] backlight: pwm: don't call legacy pwm request for device defined in dt Vladimir Zapolskiy
2014-10-11 13:46 ` Vladimir Zapolskiy
2014-10-11 14:21 ` Greg KH
2014-10-11 14:21 ` Greg KH
2014-11-07 13:48 ` Thierry Reding
2014-11-07 13:48 ` Thierry Reding
2014-11-07 14:19 ` Vladimir Zapolskiy
2014-11-07 14:19 ` Vladimir Zapolskiy
2014-11-07 14:57 ` Vladimir Zapolskiy
2014-11-07 14:57 ` Vladimir Zapolskiy
2014-12-01 14:47 ` Vladimir Zapolskiy [this message]
2014-12-01 14:47 ` Vladimir Zapolskiy
2015-01-21 13:18 ` Vladimir Zapolskiy
2015-01-21 13:18 ` Vladimir Zapolskiy
2015-06-12 11:31 ` Thierry Reding
2015-06-12 11:31 ` Thierry Reding
2015-06-12 12:57 ` Vladimir Zapolskiy
2015-06-12 12:57 ` Vladimir Zapolskiy
2015-06-12 12:57 ` Vladimir Zapolskiy
2015-06-12 13:19 ` Thierry Reding
2015-06-12 13:19 ` Thierry Reding
2014-10-11 13:46 ` [PATCH 2/2] backlight: pwm: clean up pwm requested using legacy API Vladimir Zapolskiy
2014-10-11 13:46 ` Vladimir Zapolskiy
2014-10-11 14:21 ` Greg KH
2014-10-11 14:21 ` Greg KH
2014-11-06 22:10 ` Vladimir Zapolskiy
2014-11-06 22:10 ` Vladimir Zapolskiy
2014-11-06 22:54 ` Greg KH
2014-11-06 22:54 ` Greg KH
2014-11-07 11:50 ` Lee Jones
2014-11-07 11:50 ` Lee Jones
2014-11-07 13:47 ` Thierry Reding
2014-11-07 13:47 ` Thierry Reding
2014-11-10 10:01 ` Lee Jones
2014-11-10 10:01 ` Lee Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=547C7F8A.40707@mentor.com \
--to=vladimir_zapolskiy@mentor.com \
--cc=cooloney@gmail.com \
--cc=jg1.han@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.