drm/i915/vlv_dsi: Control panel and backlight enable GPIOs on BYT
Subsystems (7)
cover drm/i915/vlv_dsi: Control panel and backlight enable GPIOs on BYT
Hi All,
On Bay Trail devices the MIPI power on/off sequences for DSI LCD panels do not control the LCD panel- and backlight-enable GPIOs. So far, when the VBT indicates we should use the SoC for backlight control, 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 series contains 2 patches which together fix this.
To avoid new errors in the intel-gfx CI (assuming there is atleast 1 BYT device there with a DSI panel), we need both of these patches to be merged through the drm-intel tree.
Unfortunately there is some churn currently going on in the pinctrl-baytrail.c code, but not in the part of the file which this touches, so merging the pinctrl-baytrail.c changes through the drm-intel tree should not lead to conflicts later.
Andy, Mika, assuming you are happy with the changes, can I get your ack for merging the pinctrl-baytrail patch throught the drm-inteol tree?
Regards,
Hans
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH 1/2 pinctrl: baytrail: Add GPIO lookup and pinctrl-map for i915 DSI panel ctrl
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.
--- drivers/pinctrl/intel/pinctrl-baytrail.c | 44 ++++++++++++++++++++++++ 1 file changed, 44 insertions(+)
drivers/pinctrl/intel/pinctrl-baytrail.c +44 -0
@@ -9,6 +9,7 @@#include <linux/acpi.h> #include <linux/bitops.h> #include <linux/gpio/driver.h> +#include <linux/gpio/machine.h> #include <linux/init.h> #include <linux/interrupt.h> #include <linux/io.h>
@@ -1601,6 +1602,39 @@ static const struct acpi_device_id byt_gpio_acpi_match[] = { { } }; +/* +* On Bay Trail devices with a DSI LCD panel and using the SoC (LPSS) pwm for +* backlight control, the i915 driver needs to control the backlight and LCD +* enable GPIOs, which are always pin 10 and 11 on the NCORE. Without this +* the LCD panel will not light-up when the system is booted with a HDMI cable +* inserted and the video BIOS / GOP did not init the LCD because of this. +* +* Likewise in some cases when a HDMI cable is inserted the firmware does not +* even properly mux the PWM0 pin. We add a pinctrl-map for this so that the +* i915 driver can fix this. Note that the map is for the i915 device not for +* the PWM device. This is a bit weird, but the only thing telling us that +* the pin should definitely be muxed to the PWM controller is the VBT bit +* which tells the i915 driver to use the SoC's PWM for backlight control. +*/ + +static char score_name[32 ]; +static char ncore_name[32 ]; + +static const struct pinctrl_map byt_panel_pwm_pinctrl_map[] = { +PIN_MAP_MUX_GROUP ("0000:00:02.0" ,"soc_pwm0" , score_name, +"pwm0_grp" ,"pwm" ), +}; + +static struct gpiod_lookup_table byt_panel_gpio_table = { + .dev_id ="0000:00:02.0" , + .table = { +/* "soc_" prefix to distuingish these from those on the PMIC */ +GPIO_LOOKUP (ncore_name,10 ,"soc_backlight_enable" ,GPIO_ACTIVE_HIGH ), +GPIO_LOOKUP (ncore_name,11 ,"soc_panel_enable" ,GPIO_ACTIVE_HIGH ), + { }, + }, +}; +static int byt_pinctrl_probe (struct platform_device *pdev) {const struct intel_pinctrl_soc_data *soc_data =NULL ;
@@ -1651,6 +1685,16 @@ static int byt_pinctrl_probe(struct platform_device *pdev)if (ret)return ret; +if (soc_data == &byt_score_soc_data) { +strscpy (score_name,dev_name (&pdev->dev),sizeof (score_name)); + ret =pinctrl_register_mappings (byt_panel_pwm_pinctrl_map,1 ); +if (ret) +dev_err (&pdev->dev,"failed to register pinctrl-map\n" ); + }else if (soc_data == &byt_ncore_soc_data) { +strscpy (ncore_name,dev_name (&pdev->dev),sizeof (ncore_name)); +gpiod_add_lookup_table (&byt_panel_gpio_table); + } +platform_set_drvdata (pdev, vg);pm_runtime_enable (&pdev->dev);
Signature · 6 lines
2.23.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 1/2] pinctrl: baytrail: Add GPIO lookup and pinctrl-map for i915 DSI panel ctrl
Hi Hans!
Thanks for your patch!
Quoted 17 lines · Hans de Goede
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.
Quoted 7 lines
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 <[email protected]>
(...)
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
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 1/2] pinctrl: baytrail: Add GPIO lookup and pinctrl-map for i915 DSI panel ctrl
In reply to Hans de GoedeQuoted 17 lines · Hans de Goede
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.
Quoted 5 lines
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.
My concern here, as one of Linus', is a pollution the driver with board code. Aren't we able to split this to a separate file under PDx86 realm and do nasty quirks there?
Signature · 8 lines
With Best Regards, Andy Shevchenko _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/2 drm/i915/vlv_dsi: Control panel and backlight enable GPIOs on BYT
In reply to Hans de GoedeOn Bay Trail devices the MIPI power on/off sequences for DSI LCD panels do not control the LCD panel- and backlight-enable GPIOs. So far, when the VBT indicates we should use the SoC for backlight control, 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 makes the DSI code control the SoC GPIOs for panel- and backlight-enable on BYT, when the VBT indicates the SoC should be used for backlight control. It also ensures that the PWM0 pin is muxed to the PWM controller in this case.
This fixes the LCD panel not lighting up on various devices when booted with a HDMI monitor connected. This has been tested to fix this on the following devices:
Peaq C1010
Point of View MOBII TAB-P800W
Point of View MOBII TAB-P1005W
Terra Pad 1061
Yours Y8W81
--- drivers/gpu/drm/i915/display/intel_dsi.h | 3 +- drivers/gpu/drm/i915/display/vlv_dsi.c | 44 ++++++++++++++++++++++-- 2 files changed, 43 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/display/intel_dsi.h +2 -1
@@ -45,8 +45,9 @@ struct intel_dsi {struct intel_dsi_host *dsi_hosts[I915_MAX_PORTS ];intel_wakeref_t io_wakeref[I915_MAX_PORTS ]; -/* GPIO Desc for CRC based Panel control */ +/* GPIO Desc for panel and backlight control */ struct gpio_desc *gpio_panel; +struct gpio_desc *gpio_backlight;struct intel_connector *attached_connector;
drivers/gpu/drm/i915/display/vlv_dsi.c +41 -3
99 lines not on this page · raw message
Signature · 6 lines
2.23.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi Hans,
thank you for your patch!
drivers/gpu/drm/i915/display/intel_dsi.h struct intel_dsi { · line 50
Quoted 4 lines · Hans de Goede
drivers/gpu/drm/i915/display/intel_dsi.h +2
-1-/* GPIO Desc for CRC based Panel control */ +/* GPIO Desc for panel and backlight control */ struct gpio_desc *gpio_panel; +struct gpio_desc *gpio_backlight;
I think what happens here is that you reimplement drivers/video/backlight/gpio_backlight.c
The existing power control GPIO also reimplements drivers/regulator/fixed.c in a sense but I am under the impression that x86 in general and ACPI in particular has a problem with the regulator subsystem so I am uncertain about that one.
When I look at the code I get more confused because nominally panels should have their own drivers in drivers/gpu/drm/panel/* especially DSI panels, and the panels control their own GPIOs or regulators for power and backlight.
I was under the impression that Heikki's and Dmitry's recent additions to software nodes would make it possible to actually spawn devices like the GPIO backlight and/or fixed regulator and put references to them so that the drivers can pick them up from the respective frameworks and manage them?
Maybe I misunderstood things here though, I am a bit under the impression that elder DRM drivers are considered "elder gods" and do not need to use separate panel drivers, backlight abstraction etc, and in that case just go ahead, I guess.
But I suspect some separation
would help the day the i915 driver wants to reuse some really complex DSI panel from drivers/gpu/drm/panel/* though.
Yours,
Linus Walleij
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Jani Nikula
maintainerQuoted 39 lines · Linus Walleij
Hi Hans,
thank you for your patch!
drivers/gpu/drm/i915/display/intel_dsi.h struct intel_dsi { · line 50
Quoted 4 lines · Hans de Goede
drivers/gpu/drm/i915/display/intel_dsi.h +2
-1-/* GPIO Desc for CRC based Panel control */ +/* GPIO Desc for panel and backlight control */ struct gpio_desc *gpio_panel; +struct gpio_desc *gpio_backlight;I think what happens here is that you reimplement
drivers/video/backlight/gpio_backlight.cThe existing power control GPIO also reimplements
drivers/regulator/fixed.cin a sense but I am under the impression that x86 in general and ACPI in particular has a problem with the regulator subsystem so I am uncertain about that one.When I look at the code I get more confused because nominally panels should have their own drivers in
drivers/gpu/drm/panel/*especially DSI panels, and the panels control their own GPIOs or regulators for power and backlight.I was under the impression that Heikki's and Dmitry's recent additions to software nodes would make it possible to actually spawn devices like the GPIO backlight and/or fixed regulator and put references to them so that the drivers can pick them up from the respective frameworks and manage them?
Maybe I misunderstood things here though, I am a bit under the impression that elder DRM drivers are considered "elder gods" and do not need to use separate panel drivers, backlight abstraction etc, and in that case just go ahead, I guess.
Quoted 4 lines
But I suspect some separation
would help the day the i915 driver wants to reuse some really complex DSI panel fromdrivers/gpu/drm/panel/*though.
Sadly I don't think that's going to happen, though.
For i915 the panels are described by VBT, or Video BIOS Tables. We don't really know the make or model of the panels, we just get the timings and sequences etc. from there. There's no info to probe a separate panel driver. So we just have a "generic" DSI driver that's part of i915 which uses the data from the VBT to drive all the possible panels.
We do use some of the drm DSI framework as a library to abstract things a bit better, but that's about it.
The sequences should include details about GPIOs to toggle as well, so in that sense I feel like the gpio calls should be bolted there.
BR,
Jani.
Signature · 5 lines
Jani Nikula, Intel Open Source Graphics Center _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
HI,
Quoted 53 lines · Jani Nikula
Quoted 39 lines · Linus Walleij
Hi Hans,
thank you for your patch!
drivers/gpu/drm/i915/display/intel_dsi.h struct intel_dsi { · line 50
Quoted 4 lines · Hans de Goede
drivers/gpu/drm/i915/display/intel_dsi.h +2
-1-/* GPIO Desc for CRC based Panel control */ +/* GPIO Desc for panel and backlight control */ struct gpio_desc *gpio_panel; +struct gpio_desc *gpio_backlight;I think what happens here is that you reimplement
drivers/video/backlight/gpio_backlight.cThe existing power control GPIO also reimplements
drivers/regulator/fixed.cin a sense but I am under the impression that x86 in general and ACPI in particular has a problem with the regulator subsystem so I am uncertain about that one.When I look at the code I get more confused because nominally panels should have their own drivers in
drivers/gpu/drm/panel/*especially DSI panels, and the panels control their own GPIOs or regulators for power and backlight.I was under the impression that Heikki's and Dmitry's recent additions to software nodes would make it possible to actually spawn devices like the GPIO backlight and/or fixed regulator and put references to them so that the drivers can pick them up from the respective frameworks and manage them?
Maybe I misunderstood things here though, I am a bit under the impression that elder DRM drivers are considered "elder gods" and do not need to use separate panel drivers, backlight abstraction etc, and in that case just go ahead, I guess.
Quoted 4 lines
But I suspect some separation
would help the day the i915 driver wants to reuse some really complex DSI panel fromdrivers/gpu/drm/panel/*though.Sadly I don't think that's going to happen, though.
For i915 the panels are described by VBT, or Video BIOS Tables. We don't really know the make or model of the panels, we just get the timings and sequences etc. from there. There's no info to probe a separate panel driver. So we just have a "generic" DSI driver that's part of i915 which uses the data from the VBT to drive all the possible panels.
Quoted 5 lines
We do use some of the drm DSI framework as a library to abstract things a bit better, but that's about it.
The sequences should include details about GPIOs to toggle as well, so in that sense I feel like the gpio calls should be bolted there.
Hmm, yes that makes sense, the problem really is that the VBT sequences for DSI panels on BYT are incomplete (*) and the MIPI_SEQ_POWER_ON / _OFF and MIPI_SEQ_BACKLIGHT_ON / _OFF sequences do not containt the "instructions" to toggle the panel-enable, resp. backlight enable GPIOs as they do on CHT and newer devices.
So if we see all this of a shortcoming of the VBT tables, then it makes sense to move all special handling for this to intel_dsi_vbt.c, so we put the adding of the lookup table, the getting of the pins and the controlling of the pins all in there.
Jani, is that what you have in mind ?
This would also solve the problem of Linus and Andy not liking the polution of the pinctrl driver with the adding of the platform specific lookups; and then we could only add the lookups when the VBT says the SoC is used for backlight control, leaving things as is (not even adding the lookups) when the PMIC is used for backlight control.
There is only one problem, currently is is not possible to unregister a mapping added with pinctrl_register_mappings and the i915 driver is typically a module which can be unloaded and I believe actually is unloaded as part of the i915 CI.
pinctrl_register_mappings copies the passed in mapping, but it is a shallow copy, so it contains pointers to the modules const segment and we do not want to re-add another copy of the mapping when the module loads a second time.
Fixing this is easy though, there already is a pinctrl_unregister_map() function, we just need to export it so that the i915 driver can remove the mapping when it is unbound.
Linus would exporting this function be ok with you?
Linus, question what is the purpose of the "dupping" / shallow copying of the argument passed to pinctrl_register_map ? Since it is shallow the mem for any pointers contained within there need to be kept around by the caller, so why not let the caller keep the pinctrl_map struct itself around too?
If we are going to export pinctrl_unregister_map() we need to make it do the right thing for dupped maps too, we can just store the dup flag in struct pinctrl_maps. So this is easy, but I wonder if we cannot get rid of the dupping all together ?
Regards,
Hans
*) I suspect these are all version 2 VBT sequences (I guess I should check this) and according to the comment in vlv_dsi.c which documents the sequences, for v2 these sequences are not used, e.g. instead of executing the MIPIPanelPowerOn sequence the "panel-on" step is described simply as "power on". and the MIPIBacklightOn/Off sequences are described as being VBT v3+ only
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 10 lines · Hans de Goede
There is only one problem, currently is is not possible to unregister a mapping added with
pinctrl_register_mappingsand the i915 driver is typically a module which can be unloaded and I believe actually is unloaded as part of the i915 CI.
pinctrl_register_mappingscopies the passed in mapping, but it is a shallow copy, so it contains pointers to the modules const segment and we do not want to re-add another copy of the mapping when the module loads a second time.
Quoted 5 lines
Fixing this is easy though, there already is a
pinctrl_unregister_map()function, we just need to export it so that the i915 driver can remove the mapping when it is unbound.Linus would exporting this function be ok with you?
Yep!
Quoted 2 lines
Linus, question what is the purpose of the "dupping" / shallow copying of the argument passed to
pinctrl_register_map?
The initial commit contained this comment later removed:
+ /*
+ * Make a copy of the map array - string pointers will end up in the + * kernel const section anyway so these do not need to be deep copied. + */
The use was to free up memory for platforms using boardfiles with a gazillion variants and huge pin control tables, so these could be marked __initdata and discarded after boot. As the strings would anyway stay around we didn't need to deep copy.
See for example in arch/arm/mach-u300/core.c static struct pinctrl_map __initdata u300_pinmux_map[]
Quoted 4 lines
Since
it is shallow the mem for any pointers contained within there need to be kept around by the caller, so why not let the caller keep thepinctrl_mapstruct itself around too?
So the strings will be kept around because the kernel can't get rid of strings. (Yeah it is silly, should haven been fixed ages ago, but not by me, haha :)
Quoted 4 lines
If we are going to export
pinctrl_unregister_map()we need to make it do the right thing for dupped maps too, we can just store the dup flag in structpinctrl_maps. So this is easy, but I wonder if we cannot get rid of the dupping all together ?
Maybe ... I don't know. What do you think? I suppose you could make u300 crash if you do that.
Yours,
Linus Walleij
Hi,
Quoted 48 lines · Linus Walleij
Quoted 10 lines · Hans de Goede
There is only one problem, currently is is not possible to unregister a mapping added with
pinctrl_register_mappingsand the i915 driver is typically a module which can be unloaded and I believe actually is unloaded as part of the i915 CI.
pinctrl_register_mappingscopies the passed in mapping, but it is a shallow copy, so it contains pointers to the modules const segment and we do not want to re-add another copy of the mapping when the module loads a second time.Quoted 5 lines
Fixing this is easy though, there already is a
pinctrl_unregister_map()function, we just need to export it so that the i915 driver can remove the mapping when it is unbound.Linus would exporting this function be ok with you?
Yep!
Quoted 2 lines
Linus, question what is the purpose of the "dupping" / shallow copying of the argument passed to
pinctrl_register_map?The initial commit contained this comment later removed:
drivers/gpu/drm/i915/display/vlv_dsi.c +4
-0+/* +* Make a copy of the map array - string pointers will end up in the +* kernel const section anyway so these do not need to be deep copied. +*/ The use was to free up memory for platforms using boardfiles with a gazillion variants and huge pin control tables, so these could be marked
__initdataand discarded after boot. As the strings would anyway stay around we didn't need to deep copy.See for example in
arch/arm/mach-u300/core.cstatic structpinctrl_map__initdatau300_pinmux_map[]Quoted 4 lines
Since
it is shallow the mem for any pointers contained within there need to be kept around by the caller, so why not let the caller keep thepinctrl_mapstruct itself around too?So the strings will be kept around because the kernel can't get rid of strings. (Yeah it is silly, should haven been fixed ages ago, but not by me, haha :)
Quoted 7 lines
Quoted 4 lines
If we are going to export
pinctrl_unregister_map()we need to make it do the right thing for dupped maps too, we can just store the dup flag in structpinctrl_maps. So this is easy, but I wonder if we cannot get rid of the dupping all together ?Maybe ... I don't know. What do you think? I suppose you could make u300 crash if you do that.
I've prepared a patch which makes pinctrl_register_mappings remember if the mapping is dupped or not (store the dup value in struct pinctrl_maps); and which modifies pinctrl_unregister_map() to do the right thing depending on the stored dup value.
I still need to test the new series and then I will post it.
Regards,
Hans
Quoted 22 lines · Hans de Goede
Hi All,
On Bay Trail devices the MIPI power on/off sequences for DSI LCD panels do not control the LCD panel- and backlight-enable GPIOs. So far, when the VBT indicates we should use the SoC for backlight control, 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 series contains 2 patches which together fix this.
To avoid new errors in the intel-gfx CI (assuming there is atleast 1 BYT device there with a DSI panel), we need both of these patches to be merged through the drm-intel tree.
Quoted 7 lines
Unfortunately there is some churn currently going on in the
pinctrl-baytrail.ccode, but not in the part of the file which this touches, so merging thepinctrl-baytrail.cchanges through the drm-intel tree should not lead to conflicts later.Andy, Mika, assuming you are happy with the changes, can I get your ack for merging the pinctrl-baytrail patch throught the drm-inteol tree?
I'm not okay with this. I will tell more next week how I see this to be implemented in a better way.
Happy Black Friday! :-)
Signature · 8 lines
With Best Regards, Andy Shevchenko _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✓ Fi.CI.BAT: success for drm/i915/vlv_dsi: Control panel and backlight enable GPIOs on BYT
In reply to Hans de Goede== Series Details ==
== Series Details ==
Series: drm/i915/vlv_dsi: Control panel and backlight enable GPIOs on BYT
URL : https://patchwork.freedesktop.org/series/70223/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7447 -> Patchwork_15517
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/index.html
Known issues
------------
Here are the changes found in Patchwork_15517 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-hsw-4770: [PASS][1] -> [SKIP][2] ([fdo#109271]) +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/fi-hsw-4770/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/fi-hsw-4770/igt@[email protected]
* igt@i915_selftest@live_hangcheck:
- fi-icl-u3: [PASS][3] -> [INCOMPLETE][4] ([fdo#107713] / [fdo#108569])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/fi-icl-u3/igt@i915_selftest@live_hangcheck.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/fi-icl-u3/igt@i915_selftest@live_hangcheck.html
* igt@i915_selftest@live_sanitycheck:
- fi-skl-lmem: [PASS][5] -> [DMESG-WARN][6] ([fdo#112261])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/fi-skl-lmem/igt@i915_selftest@live_sanitycheck.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/fi-skl-lmem/igt@i915_selftest@live_sanitycheck.html
#### Warnings ####
* igt@gem_exec_suspend@basic-s4-devices:
- fi-kbl-x1275: [DMESG-WARN][7] ([fdo#103558] / [fdo#105602] / [fdo#107139]) -> [DMESG-WARN][8] ([fdo#103558] / [fdo#105602] / [fdo#105763] / [fdo#107139])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/fi-kbl-x1275/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/fi-kbl-x1275/igt@[email protected]
* igt@kms_busy@basic-flip-pipe-c:
- fi-kbl-x1275: [DMESG-WARN][9] ([fdo#103558] / [fdo#105602] / [fdo#105763]) -> [DMESG-WARN][10] ([fdo#103558] / [fdo#105602]) +3 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/fi-kbl-x1275/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/fi-kbl-x1275/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-kbl-x1275: [DMESG-WARN][11] ([fdo#103558] / [fdo#105602]) -> [DMESG-WARN][12] ([fdo#103558] / [fdo#105602] / [fdo#105763]) +7 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/fi-kbl-x1275/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/fi-kbl-x1275/igt@[email protected]
[fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558
[fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602
[fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763
[fdo#107139]: https://bugs.freedesktop.org/show_bug.cgi?id=107139
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#112261]: https://bugs.freedesktop.org/show_bug.cgi?id=112261
Participating hosts (51 -> 45)
------------------------------
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7447 -> Patchwork_15517
CI-20190529: 20190529
CI_DRM_7447: 8a02da6e5bea288945ed422bd40ad8c5a254e539 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5318: 26ae6584ac03ad862d82f986302275a68bcccb29 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15517: a653a8b459c1e9b73cdf6fb1d7b3a736bd1b1050 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
a653a8b459c1 drm/i915/vlv_dsi: Control panel and backlight enable GPIOs on BYT aa55f9a128e4 pinctrl: baytrail: Add GPIO lookup and pinctrl-map for i915 DSI panel ctrl
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.IGT: failure for drm/i915/vlv_dsi: Control panel and backlight enable GPIOs on BYT
In reply to Hans de Goede== Series Details ==
== Series Details ==
Series: drm/i915/vlv_dsi: Control panel and backlight enable GPIOs on BYT
URL : https://patchwork.freedesktop.org/series/70223/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7447_full -> Patchwork_15517_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_15517_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_15517_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_15517_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-pwrite:
- shard-tglb: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-tglb6/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-pwrite.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-tglb4/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-pwrite.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@gem_exec_schedule@pi-distinct-iova-bsd}:
- shard-tglb: NOTRUN -> [SKIP][3] +2 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-tglb4/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_15517_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_capture@capture-bsd:
- shard-iclb: [PASS][4] -> [SKIP][5] ([fdo#112146])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-iclb3/igt@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-iclb4/igt@[email protected]
* igt@gem_exec_schedule@preempt-queue-chain-vebox:
- shard-glk: [PASS][6] -> [INCOMPLETE][7] ([i915#58] / [k.org#198133])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-glk5/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-glk8/igt@[email protected]
* igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrash-inactive:
- shard-iclb: [PASS][8] -> [TIMEOUT][9] ([i915#530])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-iclb8/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrash-inactive.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-iclb5/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrash-inactive.html
* igt@gem_persistent_relocs@forked-interruptible-thrash-inactive:
- shard-hsw: [PASS][10] -> [FAIL][11] ([i915#520])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-hsw5/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-hsw6/igt@[email protected]
* igt@gem_ppgtt@flink-and-close-vma-leak:
- shard-glk: [PASS][12] -> [FAIL][13] ([i915#644])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-glk7/igt@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-glk2/igt@[email protected]
* igt@gem_softpin@noreloc-s3:
- shard-apl: [PASS][14] -> [DMESG-WARN][15] ([i915#180]) +1 similar issue
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-apl3/igt@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-apl1/igt@[email protected]
* igt@gem_userptr_blits@dmabuf-sync:
- shard-hsw: [PASS][16] -> [DMESG-WARN][17] ([fdo#111870])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-hsw4/igt@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-hsw6/igt@[email protected]
* igt@gem_userptr_blits@dmabuf-unsync:
- shard-snb: [PASS][18] -> [DMESG-WARN][19] ([fdo#111870])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-snb1/igt@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-snb5/igt@[email protected]
* igt@gem_workarounds@suspend-resume:
- shard-skl: [PASS][20] -> [INCOMPLETE][21] ([i915#69])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-skl5/igt@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-skl5/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-tglb: [PASS][22] -> [INCOMPLETE][23] ([i915#456] / [i915#460])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-tglb6/igt@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-tglb5/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-render:
- shard-iclb: [PASS][24] -> [FAIL][25] ([i915#49]) +1 similar issue
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-iclb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-render.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-iclb6/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-shrfb-draw-render.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-pwrite:
- shard-skl: [PASS][26] -> [FAIL][27] ([i915#49])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-skl7/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-pwrite.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-skl5/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-shrfb-pgflip-blt:
- shard-skl: [PASS][28] -> [INCOMPLETE][29] ([i915#123])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-skl9/igt@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-skl3/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-kbl: [PASS][30] -> [DMESG-WARN][31] ([i915#180]) +2 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-kbl1/igt@[email protected]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-kbl7/igt@[email protected]
* igt@kms_plane@pixel-format-pipe-a-planes:
- shard-skl: [PASS][32] -> [INCOMPLETE][33] ([fdo#112391])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-skl3/igt@[email protected]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-skl7/igt@[email protected]
* igt@kms_plane@pixel-format-pipe-b-planes:
- shard-kbl: [PASS][34] -> [INCOMPLETE][35] ([fdo#103665]) +1 similar issue
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-kbl7/igt@[email protected]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-kbl3/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
- shard-skl: [PASS][36] -> [FAIL][37] ([fdo#108145])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-skl7/igt@[email protected]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-skl5/igt@[email protected]
* igt@kms_psr@psr2_primary_render:
- shard-iclb: [PASS][38] -> [SKIP][39] ([fdo#109441])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-iclb2/igt@kms_psr@psr2_primary_render.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-iclb1/igt@kms_psr@psr2_primary_render.html
* igt@kms_vblank@pipe-a-wait-busy-hang:
- shard-snb: [PASS][40] -> [SKIP][41] ([fdo#109271]) +1 similar issue
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-snb6/igt@[email protected]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-snb6/igt@[email protected]
* igt@prime_vgem@fence-wait-bsd2:
- shard-iclb: [PASS][42] -> [SKIP][43] ([fdo#109276]) +1 similar issue
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-iclb4/igt@[email protected]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-iclb6/igt@[email protected]
#### Possible fixes ####
* igt@gem_ctx_isolation@bcs0-s3:
- shard-tglb: [INCOMPLETE][44] ([i915#456]) -> [PASS][45]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-tglb4/igt@[email protected]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-tglb6/igt@[email protected]
* igt@gem_ctx_isolation@rcs0-s3:
- shard-kbl: [DMESG-WARN][46] ([i915#180]) -> [PASS][47] +4 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-kbl7/igt@[email protected]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-kbl7/igt@[email protected]
* igt@gem_persistent_relocs@forked-faulting-reloc-thrashing:
- shard-snb: [INCOMPLETE][48] ([i915#530] / [i915#82]) -> [PASS][49]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-snb7/igt@[email protected]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-snb2/igt@[email protected]
* igt@gem_persistent_relocs@forked-interruptible-thrash-inactive:
- shard-iclb: [TIMEOUT][50] ([i915#530]) -> [PASS][51]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-iclb2/igt@[email protected]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-iclb1/igt@[email protected]
* igt@gem_userptr_blits@map-fixed-invalidate-busy:
- shard-hsw: [DMESG-WARN][52] ([fdo#111870]) -> [PASS][53]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-hsw6/igt@[email protected]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-hsw6/igt@[email protected]
* igt@gem_userptr_blits@sync-unmap-after-close:
- shard-snb: [DMESG-WARN][54] ([fdo#111870]) -> [PASS][55]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-snb7/igt@[email protected]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-snb1/igt@[email protected]
* igt@i915_suspend@debugfs-reader:
- shard-apl: [DMESG-WARN][56] ([i915#180]) -> [PASS][57] +1 similar issue
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-apl1/igt@[email protected]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-apl6/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-hsw: [DMESG-WARN][58] -> [PASS][59] +1 similar issue
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-hsw6/igt@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-hsw6/igt@[email protected]
* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy:
- shard-hsw: [FAIL][60] ([i915#96]) -> [PASS][61]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-hsw6/igt@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-hsw1/igt@[email protected]
* igt@kms_draw_crc@draw-method-xrgb8888-render-xtiled:
- shard-skl: [INCOMPLETE][62] ([fdo#112347] / [i915#646]) -> [PASS][63]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-skl8/igt@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-skl4/igt@[email protected]
* igt@kms_fbcon_fbt@psr-suspend:
- shard-tglb: [INCOMPLETE][64] ([i915#456] / [i915#460]) -> [PASS][65]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-tglb1/igt@[email protected]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-tglb6/igt@[email protected]
* igt@kms_flip@2x-flip-vs-expired-vblank:
- shard-glk: [FAIL][66] ([i915#46]) -> [PASS][67]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-glk5/igt@[email protected]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-glk1/igt@[email protected]
* igt@kms_flip@2x-flip-vs-modeset-interruptible:
- shard-hsw: [DMESG-WARN][68] ([i915#44]) -> [PASS][69]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-hsw5/igt@[email protected]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-hsw1/igt@[email protected]
* igt@kms_flip@plain-flip-ts-check:
- shard-kbl: [FAIL][70] ([i915#34]) -> [PASS][71]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-kbl1/igt@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-kbl1/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-blt:
- shard-iclb: [FAIL][72] ([i915#49]) -> [PASS][73]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-iclb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-blt.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-iclb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-gtt:
- shard-iclb: [INCOMPLETE][74] ([i915#123] / [i915#140]) -> [PASS][75]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-iclb6/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-gtt.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-iclb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-gtt.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-shrfb-plflip-blt:
- shard-skl: [INCOMPLETE][76] ([i915#123]) -> [PASS][77] +1 similar issue
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-skl5/igt@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-skl3/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen:
- shard-tglb: [INCOMPLETE][78] ([i915#435]) -> [PASS][79] +1 similar issue
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-tglb6/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-tglb7/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen.html
* igt@kms_plane@pixel-format-pipe-a-planes:
- shard-iclb: [INCOMPLETE][80] ([i915#140] / [i915#246]) -> [PASS][81]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-iclb5/igt@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-iclb5/igt@[email protected]
- shard-kbl: [INCOMPLETE][82] ([fdo#103665]) -> [PASS][83] +1 similar issue
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-kbl3/igt@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-kbl3/igt@[email protected]
* igt@kms_plane@pixel-format-pipe-b-planes:
- shard-skl: [INCOMPLETE][84] ([fdo#112347]) -> [PASS][85]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-skl10/igt@[email protected]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-skl10/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [FAIL][86] ([fdo#108145]) -> [PASS][87]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-skl3/igt@[email protected]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-skl7/igt@[email protected]
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-skl: [INCOMPLETE][88] ([i915#69]) -> [PASS][89]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-skl4/igt@[email protected]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-skl3/igt@[email protected]
* igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend:
- shard-iclb: [DMESG-WARN][90] ([fdo#111764]) -> [PASS][91]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-iclb6/igt@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-iclb6/igt@[email protected]
#### Warnings ####
* igt@gem_eio@kms:
- shard-snb: [DMESG-WARN][92] ([i915#444] / [i915#502]) -> [DMESG-WARN][93] ([i915#443] / [i915#444] / [i915#502] / [i915#503])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-snb4/igt@[email protected]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-snb1/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-suspend:
- shard-kbl: [DMESG-FAIL][94] ([i915#180] / [i915#54]) -> [FAIL][95] ([i915#54])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-kbl3/igt@[email protected]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-kbl1/igt@[email protected]
* igt@kms_plane@pixel-format-pipe-b-planes-source-clamping:
- shard-skl: [INCOMPLETE][96] -> [INCOMPLETE][97] ([fdo#112347] / [fdo#112391])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7447/shard-skl4/igt@[email protected]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/shard-skl1/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#111764]: https://bugs.freedesktop.org/show_bug.cgi?id=111764
[fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
[fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146
[fdo#112347]: https://bugs.freedesktop.org/show_bug.cgi?id=112347
[fdo#112391]: https://bugs.freedesktop.org/show_bug.cgi?id=112391
[i915#123]: https://gitlab.freedesktop.org/drm/intel/issues/123
[i915#140]: https://gitlab.freedesktop.org/drm/intel/issues/140
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#246]: https://gitlab.freedesktop.org/drm/intel/issues/246
[i915#34]: https://gitlab.freedesktop.org/drm/intel/issues/34
[i915#435]: https://gitlab.freedesktop.org/drm/intel/issues/435
[i915#44]: https://gitlab.freedesktop.org/drm/intel/issues/44
[i915#443]: https://gitlab.freedesktop.org/drm/intel/issues/443
[i915#444]: https://gitlab.freedesktop.org/drm/intel/issues/444
[i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456
[i915#46]: https://gitlab.freedesktop.org/drm/intel/issues/46
[i915#460]: https://gitlab.freedesktop.org/drm/intel/issues/460
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#502]: https://gitlab.freedesktop.org/drm/intel/issues/502
[i915#503]: https://gitlab.freedesktop.org/drm/intel/issues/503
[i915#520]: https://gitlab.freedesktop.org/drm/intel/issues/520
[i915#530]: https://gitlab.freedesktop.org/drm/intel/issues/530
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58
[i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644
[i915#646]: https://gitlab.freedesktop.org/drm/intel/issues/646
[i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69
[i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
[i915#96]: https://gitlab.freedesktop.org/drm/intel/issues/96
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7447 -> Patchwork_15517
CI-20190529: 20190529
CI_DRM_7447: 8a02da6e5bea288945ed422bd40ad8c5a254e539 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5318: 26ae6584ac03ad862d82f986302275a68bcccb29 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15517: a653a8b459c1e9b73cdf6fb1d7b3a736bd1b1050 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15517/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx