From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [Intel-gfx] [PATCH 0/5] drm/i915/dsi: gpio refactors
Date: Wed, 1 Nov 2023 12:16:15 +0200 [thread overview]
Message-ID: <cover.1698833543.git.jani.nikula@intel.com> (raw)
This is something I've had laying around for more than a year I
think. Andy's series [1] reminded me of it. I don't think the two series
conflict, or if they do, it's trivial.
BR,
Jani.
[1] https://patchwork.freedesktop.org/series/125516/
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>
Jani Nikula (5):
drm/i915/dsi: assume BXT gpio works for non-native GPIO
drm/i915/dsi: switch mipi_exec_gpio() from dev_priv to i915
drm/i915/dsi: clarify GPIO exec sequence
drm/i915/dsi: rename platform specific *_exec_gpio() to
*_gpio_set_value()
drm/i915/dsi: bxt/icl GPIO set value do not need gpio source
drivers/gpu/drm/i915/display/intel_dsi_vbt.c | 73 +++++++++-----------
1 file changed, 34 insertions(+), 39 deletions(-)
--
2.39.2
next reply other threads:[~2023-11-01 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 10:16 Jani Nikula [this message]
2023-11-01 10:16 ` [Intel-gfx] [PATCH 1/5] drm/i915/dsi: assume BXT gpio works for non-native GPIO Jani Nikula
2023-11-01 10:16 ` [Intel-gfx] [PATCH 2/5] drm/i915/dsi: switch mipi_exec_gpio() from dev_priv to i915 Jani Nikula
2023-11-01 10:16 ` [Intel-gfx] [PATCH 3/5] drm/i915/dsi: clarify GPIO exec sequence Jani Nikula
2023-11-01 10:16 ` [Intel-gfx] [PATCH 4/5] drm/i915/dsi: rename platform specific *_exec_gpio() to *_gpio_set_value() Jani Nikula
2023-11-01 10:16 ` [Intel-gfx] [PATCH 5/5] drm/i915/dsi: bxt/icl GPIO set value do not need gpio source Jani Nikula
2023-11-02 13:40 ` Andy Shevchenko
2023-11-01 13:00 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dsi: gpio refactors Patchwork
2023-11-02 13:00 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=cover.1698833543.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.