From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Michael Anderson <mwwa919@gmail.com>,
Bartosz Golaszewski <brgl@kernel.org>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gfx@lists.freedesktop.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Hans de Goede <hansg@kernel.org>,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915/dsi: Use owned panel/backlight GPIOs in VLV MIPI sequences
Date: Mon, 19 Oct 2026 14:18:50 +0300 [thread overview]
Message-ID: <atX8mpg19_WkIa27@ashevche-desk.local> (raw)
In-Reply-To: <CAL-Wm=O-Gr3CuvCn8iSQceQMhu=LGFz0SPhmWeFL=RiVnoprdw@mail.gmail.com>
+Cc: Bart (as GPIOLIB maintainer and author of the reset-gpio rework).
On Mon, Oct 19, 2026 at 07:03:57AM -0400, Michael Anderson wrote:
> Thanks for looking at this. I'd like to make sure I understand before
> doing a v2.
>
> Here both users of pin 10 are i915 itself: intel_dsi_vbt_gpio_init()
> takes it as the "backlight" enable GPIO (soc_panel_gpio_table,
> PPS_BLC_SOC), and the VBT MIPI sequences on this tablet then toggle the
> same pin as the panel reset (low in ASSERT_RESET, high-low-high in
> DEASSERT_RESET). Do you mean describing pin 10 with a software-node
> "reset-gpios" reference and having both paths go through
> reset_control_*(), or something else?
>
> One concern: the VBT drives explicit pulses on the pin, and shared reset
> controls are refcounted, so a pulse from one path wouldn't reach the line
> while the other holds it deasserted. Would an exclusive reset obtained
> once by i915 and used by both paths work instead, or am I missing how
> reset-gpio handles this?
But then it sounds like the request-by-demand?
Bart, any ideas how to address this case?
> On Mon, Oct 19, 2026 at 5:58 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > On Sun, Oct 18, 2026 at 04:12:40PM -0400, Mike Anderson via B4 Relay wrote:
> >
> > > On VLV with PPS_BLC_SOC, intel_dsi_vbt_gpio_init() requests the
> > > backlight and panel enable GPIOs (INT33FC:01 pins 10 and 11) for i915
> > > itself. Since commit 8241b55f1ded ("drm/i915/dsi: Replace poking of VLV
> > > GPIOs behind the driver's back") the GPIO elements of the VBT MIPI
> > > sequences also request their pin through gpiolib, so when a sequence
> > > toggles one of these two pins the request fails and the toggle is
> > > dropped:
> > >
> > > i915 0000:00:02.0: [drm] *ERROR* GPIO index 10 request failed (-EBUSY)
> > >
> > > Before that commit the pad registers were written directly, so the
> > > sequences could still drive the pins i915 owned.
> > >
> > > The Toshiba Encore 2 WT8-B (Bay Trail, DSI panel) uses pin 10 as the
> > > panel reset line: MIPI_SEQ_ASSERT_RESET drives it low and
> > > MIPI_SEQ_DEASSERT_RESET pulses it high-low-high. With every toggle
> > > failing, the panel is never reset after i915 sends MIPI_SEQ_DISPLAY_OFF
> > > during takeover and stays black, even though the backlight PWM and both
> > > enable GPIOs read back as on. The tablet only has a usable display
> > > with nomodeset.
> > >
> > > When a VLV MIPI sequence targets pin 10 or 11 and i915 holds the
> > > corresponding descriptor, set it through that descriptor instead of
> > > requesting the pin a second time.
> >
> > Ah, nice, this should be solved via using reset-gpio, which is exactly fixed
> > for the reset shared lines case.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-10-19 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 20:12 Mike Anderson via B4 Relay
2026-10-19 9:58 ` Andy Shevchenko
2026-10-19 11:03 ` Michael Anderson
2026-10-19 11:18 ` Andy Shevchenko [this message]
2026-10-19 14:14 ` Bartosz Golaszewski
2026-10-19 12:39 ` Ville Syrjälä
2026-10-19 23:21 ` Michael Anderson
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=atX8mpg19_WkIa27@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=airlied@gmail.com \
--cc=brgl@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hansg@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mwwa919@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tursulin@ursulin.net \
/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
all inboxes | Powered by JetHome®