Hi Hans!
Thanks for your patch!
On Fri, Nov 29, 2019 at 7:58 PM Hans de Goede <hdegoede@xxxxxxxxxx> wrote:
> On Bay Trail devices the MIPI power on/off sequences for DSI LCD panels
> do not control the LCD panel and backlight GPIOs. So far we have been
> relying on these GPIOs being configured as output and driven high by
> the Video BIOS (GOP) when it initializes the panel.
>
> This does not work when the device is booted with a HDMI monitor connected
> as then the GOP will initialize the HDMI instead of the panel, leaving the
> panel black, even though the i915 driver tries to output an image to it.
>
> Likewise on some device-models when the GOP does not initialize the DSI
> panel it also leaves the mux of the PWM0 pin in generic GPIO mode instead
> of muxing it to the PWM controller.
>
> This commit adds GPIO lookups and a pinctrl-map which the i915 driver can
> use to get the panel- and backlight-enable GPIOs and to mux the PWM0 pin
> to the PWM controller.
>
> Note it may seem a bit weird to add a pinctrl-map for the i915 driver,
> so that it can set the PWM0 pinmux. Doing this from the LPSS PWM driver
> would be more logical. But the only thing telling us that the pin should
> definitely be muxed to the PWM controller is the VBT to which the PWM
> driver does not have access.
>
> Signed-off-by: Hans de Goede <hdegoede@xxxxxxxxxx>
(...)
The code setting up the pinctrl map and the GPIO machine
descriptor essentially looks good to me.
This looks a bit weird:
+ if (soc_data == &byt_score_soc_data) {
Can you do this with explicit platform ID string
comparison instead?
if (!strcmp(soc_data->uid, BYT_SCORE_ACPI_UID)) { ...
It seems more appropriate to me.
What is puzzling is the placement inside the pinctrl driver:
normally the thing that spawns the devices on the platform
such as the "byt_gpio" should register this table too.
However I see that the device comes from the ACPI match.
Two questions:
- Is this one of those cases where ACPI "should have
thought of this" (a common phrase) and we have to mop
up the mess in the kernel because ACPI didn't and now
we have to quirk around it?
- Can we in that case handle this with a "boardfile" of
quirks under say drivers/platform where we register
some extra stuff rather than inside the pinctrl driver?
It sort of connects to the other review comments where
I feel we should be spawning gpio backlight devices from
somewhere.
I understand those things may be a bit big, if the intel
pinctrl maintainers are fine with this solution I am fine
with it too, it's not like it is the biggest deal, I am just worried
that we might be stockpiling these quirks all over the place
while they should perhaps be centralized.
Yours,
Linus Walleij
