All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Sui Jingfeng <sui.jingfeng@linux.dev>
Cc: David Airlie <airlied@gmail.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Daniel Vetter <daniel@ffwll.ch>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] drm/bridge: simple-bridge: Extend match support for non-DT based systems
Date: Wed, 20 Mar 2024 22:34:15 +0200	[thread overview]
Message-ID: <ZftIRz2gCiGcoPwj@smile.fi.intel.com> (raw)
In-Reply-To: <20240122163220.110788-3-sui.jingfeng@linux.dev>

On Tue, Jan 23, 2024 at 12:32:17AM +0800, Sui Jingfeng wrote:
> Which is intended to be used on non-DT environment, where the simple-bridge
> platform device is created by either the display controller driver side or
> platform firmware subsystem. To avoid duplication and to keep consistent,
> we choose to reuse the OF match tables. Because the potentional user may
> not has a of_node attached, nor a ACPI match id. If this is the case,
> a software node string property can be provide to fill the niche.

...

> -	sbridge->info = of_device_get_match_data(&pdev->dev);
> +	if (pdev->dev.of_node)
> +		sbridge->info = of_device_get_match_data(&pdev->dev);
> +	else
> +		sbridge->info = simple_bridge_get_match_data(&pdev->dev);

This is wrong. Just use device_get_match_data() instead of of_ counter part.
The rest, if required, has to be addressed elsewhere.

So, formal NAK for the changes like above.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2024-03-20 20:34 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 16:32 [PATCH 0/5] drm/bridge: Allow using fwnode API to get the next bridge Sui Jingfeng
2024-01-22 16:32 ` Sui Jingfeng
2024-01-22 16:32 ` [PATCH 1/5] drm/bridge: Add drm_bridge_find_by_fwnode() helper Sui Jingfeng
2024-01-22 16:32   ` Sui Jingfeng
2024-01-23  1:17   ` Laurent Pinchart
2024-01-23  1:17     ` Laurent Pinchart
2024-01-23  8:01     ` Sui Jingfeng
2024-01-23  8:01       ` Sui Jingfeng
2024-01-23 15:15       ` Laurent Pinchart
2024-01-23 15:15         ` Laurent Pinchart
2024-01-22 16:32 ` [PATCH 2/5] drm/bridge: simple-bridge: Extend match support for non-DT based systems Sui Jingfeng
2024-01-22 16:32   ` Sui Jingfeng
2024-01-23  1:21   ` Laurent Pinchart
2024-01-23  1:21     ` Laurent Pinchart
2024-01-23  8:20     ` Sui Jingfeng
2024-01-23  8:20       ` Sui Jingfeng
2024-01-23 15:16       ` Laurent Pinchart
2024-01-23 15:16         ` Laurent Pinchart
2024-01-23 12:31     ` Sui Jingfeng
2024-01-23 12:31       ` Sui Jingfeng
2024-03-20 20:34   ` Andy Shevchenko [this message]
2024-01-22 16:32 ` [PATCH 3/5] drm/bridge: simple-bridge: Allow acquiring the next bridge with fwnode API Sui Jingfeng
2024-01-22 16:32   ` Sui Jingfeng
2024-01-23  1:18   ` Laurent Pinchart
2024-01-23  1:18     ` Laurent Pinchart
2024-01-23 12:18     ` Sui Jingfeng
2024-01-23 12:18       ` Sui Jingfeng
2024-01-23 15:18       ` Laurent Pinchart
2024-01-23 15:18         ` Laurent Pinchart
2024-01-24 15:00       ` Maxime Ripard
2024-01-24 15:00         ` Maxime Ripard
2024-01-22 16:32 ` [PATCH 4/5] drm/bridge: display-connector: Extend match support for non-DT based systems Sui Jingfeng
2024-01-22 16:32   ` Sui Jingfeng
2024-01-22 16:32 ` [PATCH 5/5] drm-bridge: display-connector: Switch to use fwnode API Sui Jingfeng
2024-01-22 16:32   ` Sui Jingfeng
2024-01-23  1:20   ` Laurent Pinchart
2024-01-23  1:20     ` Laurent Pinchart
2024-01-23 12:35     ` Sui Jingfeng
2024-01-23 12:35       ` Sui Jingfeng
2024-03-20 20:32     ` Andy Shevchenko

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=ZftIRz2gCiGcoPwj@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=sui.jingfeng@linux.dev \
    --cc=tzimmermann@suse.de \
    /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.