All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/2] Avoid unwanted lspcon init and probe warnings
Date: Fri, 22 Mar 2024 17:48:30 +0530	[thread overview]
Message-ID: <20240322121832.4170061-1-ankit.k.nautiyal@intel.com> (raw)

Currently we probe for lspcon, inside lspcon init.

If there is no lspcon connected, the probe expectedly fails and
results in error message. This inturn gets propogated to
lspcon init and we get again error message for lspcon init
failure.

Separate the probe function and avoid displaying error if probe fails.
If probe succeeds, only then start lspcon init and set the expected
LS/PCON mode as first step.

Ankit Nautiyal (2):
  drm/i915/lspcon: Separate function to set expected mode
  drm/i915/lspcon: Separate lspcon probe and lspcon init

 drivers/gpu/drm/i915/display/intel_dp.c     |  3 +
 drivers/gpu/drm/i915/display/intel_lspcon.c | 66 +++++++++++++--------
 drivers/gpu/drm/i915/display/intel_lspcon.h |  1 +
 3 files changed, 45 insertions(+), 25 deletions(-)

-- 
2.40.1


             reply	other threads:[~2024-03-22 12:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 12:18 Ankit Nautiyal [this message]
2024-03-22 12:18 ` [PATCH 1/2] drm/i915/lspcon: Separate function to set expected mode Ankit Nautiyal
2024-03-25 15:17   ` Jani Nikula
2024-03-26  4:12     ` Nautiyal, Ankit K
2024-03-22 12:18 ` [PATCH 2/2] drm/i915/lspcon: Separate lspcon probe and lspcon init Ankit Nautiyal
2024-03-25 15:18   ` Jani Nikula
2024-03-26  4:26     ` Nautiyal, Ankit K
2024-03-26  6:56       ` Jani Nikula
2024-03-26  8:29         ` Nautiyal, Ankit K
2024-03-22 20:10 ` ✓ Fi.CI.BAT: success for Avoid unwanted lspcon init and probe warnings Patchwork
2024-03-23 21:40 ` ✗ 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=20240322121832.4170061-1-ankit.k.nautiyal@intel.com \
    --to=ankit.k.nautiyal@intel.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.