From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Thierry Chatard <tchatard@gmail.com>,
linux-kernel@vger.kernel.org, hansg@kernel.org, lee@kernel.org,
platform-driver-x86@vger.kernel.org,
ilpo.jarvinen@linux.intel.com, djrscally@gmail.com,
linux-media@vger.kernel.org, mchehab@kernel.org,
jacopo.mondi@ideasonboard.com, nicholas@rothemail.net,
v.vitovt@gmail.com
Subject: Re: [PATCH v10 4/8] platform/x86: int3472: tps68470: add static clock consumer support
Date: Fri, 4 Sep 2026 10:06:49 +0300 [thread overview]
Message-ID: <appuCVrBGcwfTXeX@kekkonen.localdomain> (raw)
In-Reply-To: <apazFgPm4B5B_KdZ@ashevche-desk.local>
On Tue, Sep 01, 2026 at 02:12:22PM +0300, Andy Shevchenko wrote:
> On Mon, Aug 31, 2026 at 06:07:50PM +0200, Thierry Chatard wrote:
> > On some platforms a sensor's ACPI _DEP does not list the INT3472 device,
> > so for_each_acpi_consumer_dev() misses that sensor and never registers its
> > tps68470-clk consumer entry, leaving the sensor without its MCLK.
> >
> > Add optional n_clk_consumers/clk_consumers fields to the board data. When
> > set, probe builds the tps68470-clk platform data from that static list
> > instead of walking the ACPI consumers. Boards that leave the fields unset
> > keep using the existing ACPI traversal.
>
> ...
>
> > - n_consumers = skl_int3472_fill_clk_pdata(dev, &clk_pdata);
> > - if (n_consumers < 0)
> > - return n_consumers;
> > + if (board_data->n_clk_consumers) {
> > + clk_pdata = devm_kzalloc(dev,
> > + struct_size(clk_pdata, consumers,
> > + board_data->n_clk_consumers),
> > + GFP_KERNEL);
> > + if (!clk_pdata)
> > + return -ENOMEM;
> > + clk_pdata->n_consumers = board_data->n_clk_consumers;
> > + for (i = 0; i < board_data->n_clk_consumers; i++)
> > + clk_pdata->consumers[i] = board_data->clk_consumers[i];
> > + n_consumers = board_data->n_clk_consumers;
> > + } else {
> > + n_consumers = skl_int3472_fill_clk_pdata(dev, &clk_pdata);
> > + if (n_consumers < 0)
> > + return n_consumers;
> > + }
>
> Can it be done in a helper, so we will have here something like this:
Please don't; it's better as-is.
>
> if (board_data->n_clk_consumers)
> n_consumers = skl_int3472_fill_static_clk_pdata(dev, &clk_pdata);
> else
> n_consumers = skl_int3472_fill_clk_pdata(dev, &clk_pdata);
> if (n_consumers < 0)
> return n_consumers;
>
> ?
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
--
Sakari Ailus
next prev parent reply other threads:[~2026-09-04 7:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 16:07 [PATCH v10 0/8] Enable cameras on Dell Latitude 5285 2-in-1 Thierry Chatard
2026-08-31 16:07 ` [PATCH v10 1/8] mfd: intel-lpss: add resource conflict quirk for Dell Latitude 5285 Thierry Chatard
2026-08-31 16:07 ` [PATCH v10 2/8] platform/x86: int3472: tps68470: use unsigned int for GPIO lookup loop counters Thierry Chatard
2026-09-01 9:48 ` Andy Shevchenko
2026-08-31 16:07 ` [PATCH v10 3/8] platform/x86: int3472: tps68470: move Windows MFD setup below the device-type switch Thierry Chatard
2026-09-01 10:55 ` Andy Shevchenko
2026-08-31 16:07 ` [PATCH v10 4/8] platform/x86: int3472: tps68470: add static clock consumer support Thierry Chatard
2026-09-01 11:12 ` Andy Shevchenko
2026-09-04 7:06 ` Sakari Ailus [this message]
2026-08-31 16:07 ` [PATCH v10 5/8] platform/x86: int3472: tps68470: use a common always-on VIO regulator init_data Thierry Chatard
2026-09-01 11:13 ` Andy Shevchenko
2026-08-31 16:07 ` [PATCH v10 6/8] platform/x86: int3472: tps68470: add board data for Dell Latitude 5285 Thierry Chatard
2026-09-01 11:15 ` Andy Shevchenko
2026-08-31 16:07 ` [PATCH v10 7/8] media: ipu-bridge: add sensor configuration for OV8858 (INT3477) Thierry Chatard
2026-09-01 9:48 ` Andy Shevchenko
2026-08-31 16:07 ` [PATCH v10 8/8] media: ov8858: add ACPI device ID INT3477 Thierry Chatard
2026-09-01 10:56 ` 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=appuCVrBGcwfTXeX@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=djrscally@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicholas@rothemail.net \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tchatard@gmail.com \
--cc=v.vitovt@gmail.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