From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Thierry Chatard <tchatard@gmail.com>
Cc: 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,
sakari.ailus@linux.intel.com, jacopo.mondi@ideasonboard.com,
nicholas@rothemail.net, v.vitovt@gmail.com
Subject: Re: [PATCH v8 3/6] platform/x86: int3472: tps68470: fix clock consumer registration for Dell Latitude 5285
Date: Thu, 27 Aug 2026 10:22:33 +0300 [thread overview]
Message-ID: <ao_luVlibcdvcfQT@ashevche-desk.local> (raw)
In-Reply-To: <20260826112452.13539-4-tchatard@gmail.com>
On Wed, Aug 26, 2026 at 01:24:48PM +0200, Thierry Chatard wrote:
> The BIOS on the Dell Latitude 5285 leaves GNVS field C0TP at zero.
> With C0TP=0 the ACPI _DEP method on INT3479 (OV5670, front camera)
> resolves to PCI0 instead of the INT3472 (TPS68470 PMIC) device.
>
> Because for_each_acpi_consumer_dev() walks the _DEP reverse-mapping,
> INT3479 is invisible to it: the clock consumer lookup entry for the
> front camera is never registered with the tps68470-clk driver, and the
> OV5670 sensor driver cannot acquire its MCLK.
>
> Add optional static clock consumer fields to the board data so probe can
> register the consumers directly, bypassing the broken _DEP traversal.
> Platforms that do not set these fields keep using the existing ACPI
> traversal path unchanged.
...
> struct mfd_cell *cells;
> struct regmap *regmap;
> int n_consumers;
> int device_type;
> - int ret;
> unsigned int i;
> + int ret;
Yep, this is leftover which needs to be folded into the previous patch.
...
> + board_data = int3472_tps68470_get_board_data(dev_name(&client->dev));
> + if (!board_data)
> + return dev_err_probe(&client->dev, -ENODEV,
> + "No board-data found for this model\n");
Define
struct device *dev = &client->dev;
at the top and make these lines better looking
board_data = int3472_tps68470_get_board_data(dev_name(dev));
if (!board_data)
return dev_err_probe(dev, -ENODATA, "No board-data found for this model\n");
(note that switching to -ENODATA helps to distinguish the case).
...
> + ret = devm_mfd_add_devices(&client->dev, PLATFORM_DEVID_NONE,
> + cells, TPS68470_WIN_MFD_CELL_COUNT,
> + NULL, 0, NULL);
> + kfree(cells);
Looks like we can switch to use __free() at some point.
> + if (ret) {
> + for (i = 0; i < board_data->n_gpiod_lookups; i++)
> + gpiod_remove_lookup_table(tables[i]);
> + }
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-08-27 7:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 11:24 [PATCH v8 0/6] Enable cameras on Dell Latitude 5285 2-in-1 Thierry Chatard
2026-08-26 11:24 ` [PATCH v8 1/6] platform/x86: intel_lpss: add resource conflict quirk for Dell Latitude 5285 Thierry Chatard
2026-08-27 7:13 ` Andy Shevchenko
2026-08-27 7:15 ` Andy Shevchenko
2026-08-26 11:24 ` [PATCH v8 2/6] platform/x86: int3472: tps68470: use unsigned int for GPIO lookup loop counters Thierry Chatard
2026-08-27 7:17 ` Andy Shevchenko
2026-08-26 11:24 ` [PATCH v8 3/6] platform/x86: int3472: tps68470: fix clock consumer registration for Dell Latitude 5285 Thierry Chatard
2026-08-27 7:22 ` Andy Shevchenko [this message]
2026-08-26 11:24 ` [PATCH v8 4/6] platform/x86: int3472: tps68470: add board data " Thierry Chatard
2026-08-26 11:24 ` [PATCH v8 5/6] media: ipu-bridge: add sensor configuration for OV8858 (INT3477) Thierry Chatard
2026-08-26 11:24 ` [PATCH v8 6/6] media: ov8858: add ACPI device ID INT3477 Thierry Chatard
2026-08-27 8:32 ` Andy Shevchenko
2026-08-27 12:49 ` [PATCH v8 0/6] Enable cameras on Dell Latitude 5285 2-in-1 Lee Jones
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=ao_luVlibcdvcfQT@ashevche-desk.local \
--to=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=sakari.ailus@linux.intel.com \
--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 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.