Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
	Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH v4 2/2] drm/i915/cx0_phy: Update HDMI TMDS C20 algorithm value
Date: Fri, 31 Jul 2026 14:56:40 +0300	[thread overview]
Message-ID: <5b06b71a00245d777f6e1f178be83b6a4d29cb2c@intel.com> (raw)
In-Reply-To: <20241217201301.3593054-3-dnyaneshwar.bhadane@intel.com>

On Wed, 18 Dec 2024, Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com> wrote:
> +/*
> + * Some ARLs SoCs have the same drm PCI IDs, so need a helper to differentiate based
> + * on the host bridge device ID to get the correct txx_mics value.
> + */
> +static bool is_arrowlake_s_by_host_bridge(void)
> +{
> +	struct pci_dev *pdev = NULL;
> +	u16 host_bridge_pci_dev_id;
> +
> +	while ((pdev = pci_get_class(PCI_CLASS_BRIDGE_HOST << 8, pdev)))
> +		host_bridge_pci_dev_id = pdev->device;
> +
> +	return pdev && IS_ARROWLAKE_S_BY_HOST_BRIDGE_ID(host_bridge_pci_dev_id);
> +}

I was just reading the code, and stumbled on this two years after it was
merged.

The function *always* returns false, because pdev is always NULL when
the while loop terminates.


BR,
Jani.


-- 
Jani Nikula, Intel

  parent reply	other threads:[~2026-07-31 11:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 20:12 [PATCH v4 0/2] drm/i915/cx0_phy: Update HDMI TMDS C20 algorithm value Dnyaneshwar Bhadane
2024-12-17 20:13 ` [PATCH v2 1/2] drm/i915/display: Add MTL subplatforms definition Dnyaneshwar Bhadane
2024-12-26  5:19   ` Kandpal, Suraj
2024-12-17 20:13 ` [PATCH v4 2/2] drm/i915/cx0_phy: Update HDMI TMDS C20 algorithm value Dnyaneshwar Bhadane
2024-12-26  5:19   ` Kandpal, Suraj
2026-07-31 11:56   ` Jani Nikula [this message]
2024-12-18  9:56 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/cx0_phy: Update HDMI TMDS C20 algorithm value (rev4) Patchwork
2024-12-18  9:56 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-12-18 10:09 ` ✗ i915.CI.BAT: failure " Patchwork
2025-01-08 22:44 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/cx0_phy: Update HDMI TMDS C20 algorithm value (rev5) Patchwork
2025-01-08 22:44 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-01-08 23:23 ` ✗ i915.CI.BAT: failure " Patchwork
2025-01-09 20:32   ` Matt Roper
2025-01-10  9:47     ` Ravali, JupallyX
2025-01-10  9:38 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-14 14:53 ` ✗ i915.CI.Full: failure " Patchwork
2025-01-16 23:31   ` Matt Roper

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=5b06b71a00245d777f6e1f178be83b6a4d29cb2c@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dnyaneshwar.bhadane@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=suraj.kandpal@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