[U-Boot] [PATCH 6/7] video_display: Add power_on function

[Simon Glass]

Hi Mario,

On 18 April 2018 at 02:30, Mario Six <mario.six at gdsys.cc> wrote:
> Hi Simon,
>
> On Thu, Apr 12, 2018 at 6:36 PM, Simon Glass <sjg at chromium.org> wrote:
>> Hi Mario,
>>
>> On 11 April 2018 at 00:35, Mario Six <mario.six at gdsys.cc> wrote:
>>> Hi Simon,
>>>
>>> On Fri, Mar 30, 2018 at 10:41 AM, Simon Glass <sjg at chromium.org> wrote:
>>>> Hi Mario,
>>>>
>>>> On 28 March 2018 at 20:40, Mario Six <mario.six at gdsys.cc> wrote:
>>>>> Add a power_on function to the display uclass to allow devices to be
>>>>> probed and powered-on separately.
>>>>
>>>> Is this different from the 'enable' method?
>>>>
>>>
>>> I was thinking that this is more low-level than the enable method,
which also
>>> sets display parameters. I could also use the enable method if it's
alright to
>>> disregard the panel_bpp and timing parameters.
>>
>> Yes it's fine to ignore those. I'm just trying to use existing API
>> calls where possible (without being silly about it!)
>>
>
> OK, I'll switch to that function then.
>
>>>
>>>> Also note that we have a panel uclass that might be useful.
>>>>
>>>
>>> The Logicore driver is probably more low-level than that, but I'll take
a look.
>>
>> OK. Conceptually a panel is just a display panel, so could be of any
>> type, I think.
>>
>
> Took another look: The panel uclass is still a bit thin, but the only
operation
> (enable_backlight) sounds more that it's supposed to contain drivers for
"real"
> panels (i.e. physical display devices). The Logicore TX really just
generates a
> DP signal and does not display it itself (the upcoming board has no
display
> capability at all, actually). So it probably better fits in the display
uclass.

OK I see. Please be sure to mention this info in your patches.

Regards,
Simon