From: Hans de Goede <hdegoede@redhat.com>
To: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/4] drm/i915/vlv_dsi: Add quirks for x86 android tablets (v3)
Date: Sun, 8 Oct 2023 15:03:34 +0200 [thread overview]
Message-ID: <b308ab49-ceec-e1eb-cbf4-b272cea91e2e@redhat.com> (raw)
In-Reply-To: <20230920195613.304091-1-hdegoede@redhat.com>
Hi All,
Ping what is the status of this now? This v3 addresses all review
remarks from previous versions (specifically the request to file
+ link gitlab issues).
So AFAICT this is ready for merging ?
But I'm waiting for an ack for this before pushing it
do drm-intel-next myself ...
Regards,
Hans
On 9/20/23 21:56, Hans de Goede wrote:
> Hi All,
>
> Some vlv/chv tablets ship with Android as factory OS. The factory OS
> BSP style kernel on these tablets does not use the normal x86 hw
> autodetection instead it hardcodes a whole bunch of things including
> using panel drivers instead of relying on VBT MIPI sequences to
> turn the panel/backlight on/off.
>
> The normal i915 driver (which does not use panel drivers) mostly works
> since the VBT still needs to contain valid info for the GOP, but because
> of the Android kernel relying on panel drivers with various things
> hardcoded some DMI quirks are necessary to fix some issues on these
> devices.
>
> Some of these issues also are related to which I2C bus to use for
> MIPI sequence elements which do I2C transfers. This series also
> includes a patch adding some extra debugging to mipi_exec_i2c() to
> help with debugging similar issues in the future.
>
> These patches have been posted before but back then I did not get around
> to follow up on the series:
> https://lore.kernel.org/intel-gfx/20220225214934.383168-1-hdegoede@redhat.com/
>
> v2:
> - Drop the changes how the I2C bus number is found, instead just have
> the quirks set the right number directly where necessary. This should
> avoid any chances of causing regressions on devices where the quirks
> do not apply.
> - New quirk for backlight control issues on Lenovo Yoga Tab 3
> - Address Jani Nikula's remark about __func__ being redundant when using
> drm_dbg_kms()
>
> v3:
> - File 3 gitlab issues with drm.debug=0xe dmesg output, VBT dump for all
> 3 affected models. Add Closes: tags with links to gitlab issues
>
> Regards,
>
> Hans
>
>
> Hans de Goede (4):
> drm/i915/vlv_dsi: Add DMI quirk for wrong panel modeline in BIOS on
> Asus TF103C (v3)
> drm/i915/vlv_dsi: Add DMI quirk for wrong I2C bus and panel size on
> Lenovo Yoga Tablet 2 series (v3)
> drm/i915/vlv_dsi: Add DMI quirk for backlight control issues on Lenovo
> Yoga Tab 3 (v2)
> drm/i915/dsi: Add some debug logging to mipi_exec_i2c (v2)
>
> drivers/gpu/drm/i915/display/intel_dsi_vbt.c | 3 +
> drivers/gpu/drm/i915/display/vlv_dsi.c | 124 +++++++++++++++++++
> 2 files changed, 127 insertions(+)
>
next prev parent reply other threads:[~2023-10-08 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 19:56 [PATCH 0/4] drm/i915/vlv_dsi: Add quirks for x86 android tablets (v3) Hans de Goede
2023-09-20 19:56 ` [PATCH 1/4] drm/i915/vlv_dsi: Add DMI quirk for wrong panel modeline in BIOS on Asus TF103C (v3) Hans de Goede
2023-09-20 19:56 ` [PATCH 2/4] drm/i915/vlv_dsi: Add DMI quirk for wrong I2C bus and panel size on Lenovo Yoga Tablet 2 series (v3) Hans de Goede
2023-09-20 19:56 ` [PATCH 3/4] drm/i915/vlv_dsi: Add DMI quirk for backlight control issues on Lenovo Yoga Tab 3 (v2) Hans de Goede
2023-09-20 19:56 ` [PATCH 4/4] drm/i915/dsi: Add some debug logging to mipi_exec_i2c (v2) Hans de Goede
2023-10-08 13:03 ` Hans de Goede [this message]
2023-10-11 13:05 ` [PATCH 0/4] drm/i915/vlv_dsi: Add quirks for x86 android tablets (v3) Jani Nikula
2023-10-12 11:15 ` Hans de Goede
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=b308ab49-ceec-e1eb-cbf4-b272cea91e2e@redhat.com \
--to=hdegoede@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=ville.syrjala@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox