All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: linux-media@vger.kernel.org, linux-acpi@vger.kernel.org,
	rafael@kernel.org
Subject: Re: [PATCH 3/3] media: i2c: Use ACPI_PTR() for ACPI ID tables
Date: Fri, 28 Aug 2026 18:44:04 +0300	[thread overview]
Message-ID: <apGsxDddKkRsP-Un@kekkonen.localdomain> (raw)
In-Reply-To: <apGnw9HlXSfVGy4z@ashevche-desk.local>

On Fri, Aug 28, 2026 at 06:22:43PM +0300, Andy Shevchenko wrote:
> On Fri, Aug 28, 2026 at 06:10:55PM +0300, Sakari Ailus wrote:
> > On Fri, Aug 28, 2026 at 03:30:10PM +0200, Andy Shevchenko wrote:
> > > On Fri, Aug 28, 2026 at 11:43:28AM +0300, Sakari Ailus wrote:
> > > > Add ACPI_PTR() to the ACPI ID tables where missing. The patch has been
> > > > produced with the following command:
> > > > 
> > > > git grep -lP 'acpi_match_table.*=\s*(?!ACPI_PTR)' \
> > > > 	drivers/media/|while read i; do
> > > > 	perl -i -pe 's/\.acpi_match_table\s*=\s*\K(\w+),/ACPI_PTR($1),/' $i;
> > > > done
> > > 
> > > NAK.
> > > 
> > > It doesn't explain why we need that. This also inconsistent with OF type of
> > > IDs.
> > 
> > ACPI IDs are used on ACPI only while compatible strings are used on both
> > ACPI and OF. Thus the ACPI ID table is redundant if CONFIG_ACPI is
> > disabled.
> 
> They may be informative for the cases when on the working say OF system I can
> get the IDs for ACPI based platforms at run-time.

That's a bit far-fetched I think. Have you ever done that? :-)

Media drivers are probably one of the largest groups of drivers that are as
relevant for ACPI as they are for OF.

The of_match_ptr() that used to be present in nearly all media drivers has
been largely eliminated in the same context and the only reason for that is
that the table is also relevant for ACPI systems. The case is indeed the
opposite to the ACPI equivalent so I really don't see why we shouldn't just
drop it where it's, well, redundant.

> 
> Also you just save a couple of dozens of bytes. This is peanuts and unneeded
> churn. Again, here is my formal

I recall you often comment on struct field ordering to save, well,
typically less than dozens of bytes, too.

> 
> NAKed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> 
> In case you want to override that, please keep it in the commit message (among
> other tags). And yes, we have such a tag in the Git history of Linux kernel.

-- 
Sakari Ailus

      reply	other threads:[~2026-08-28 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28  8:43 [PATCH 0/3] Make ACPI_PTR() use PTR_IF() Sakari Ailus
2026-08-28  8:43 ` [PATCH 1/3] media: ipu-bridge: Drop redundant ACPI_PTR() usage Sakari Ailus
2026-08-28  9:58   ` Rafael J. Wysocki (Intel)
2026-08-28  8:43 ` [PATCH 2/3] ACPI: Use PTR_IF() for ACPI_PTR() Sakari Ailus
2026-08-28  9:56   ` Rafael J. Wysocki (Intel)
2026-08-28  8:43 ` [PATCH 3/3] media: i2c: Use ACPI_PTR() for ACPI ID tables Sakari Ailus
2026-08-28 13:30   ` Andy Shevchenko
2026-08-28 15:10     ` Sakari Ailus
2026-08-28 15:22       ` Andy Shevchenko
2026-08-28 15:44         ` Sakari Ailus [this message]

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=apGsxDddKkRsP-Un@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=rafael@kernel.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.