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 v10 3/8] platform/x86: int3472: tps68470: move Windows MFD setup below the device-type switch
Date: Tue, 1 Sep 2026 13:55:35 +0300 [thread overview]
Message-ID: <apavJ8OOEIv6DC4T@ashevche-desk.local> (raw)
In-Reply-To: <20260831160754.9857-4-tchatard@gmail.com>
On Mon, Aug 31, 2026 at 06:07:49PM +0200, Thierry Chatard wrote:
> The Windows path looks up the board data, builds the tps68470-clk
> platform data and registers the MFD cells; none of this is needed for the
> ChromeOS path, which registers its own cells. Move that handling out of
> the switch and let the ChromeOS case return directly, so the Windows-only
> work is no longer done for ChromeOS and the function reads top to bottom.
>
> While moving the code, use a local struct device *dev to shorten the many
> &client->dev references, and return -ENODATA (rather than -ENODEV) when no
> board data matches this machine, to distinguish it from a missing device.
These all have to be split to the separate logical changes.
> No functional change for either path.
...
> static int skl_int3472_tps68470_probe(struct i2c_client *client)
> {
> - struct acpi_device *adev = ACPI_COMPANION(&client->dev);
> const struct int3472_tps68470_board_data *board_data;
> struct tps68470_clk_platform_data *clk_pdata;
> + struct acpi_device *adev;
> struct mfd_cell *cells;
> struct regmap *regmap;
> + struct device *dev;
> int n_consumers;
> int device_type;
> unsigned int i;
> int ret;
>
> + dev = &client->dev;
This one is not getting validated, hence it's fine to assign directly above
struct device *dev = &client->dev;
> + adev = ACPI_COMPANION(dev);
> if (!adev)
> return -ENODEV;
...
> regmap = devm_regmap_init_i2c(client, &tps68470_regmap_config);
> if (IS_ERR(regmap)) {
> - dev_err(&client->dev, "Failed to create regmap: %ld\n", PTR_ERR(regmap));
> + dev_err(dev, "Failed to create regmap: %ld\n", PTR_ERR(regmap));
> return PTR_ERR(regmap);
> }
This should be replaced with return dev_err_probe() in a separate change.
> i2c_set_clientdata(client, regmap);
>
> - ret = tps68470_chip_init(&client->dev, regmap);
> + ret = tps68470_chip_init(dev, regmap);
> if (ret < 0) {
> - dev_err(&client->dev, "TPS68470 init error %d\n", ret);
> + dev_err(dev, "TPS68470 init error %d\n", ret);
> return ret;
> }
This is as well. And replacing &client->dev by dev should be in a separate
patch.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-09-01 10:55 UTC|newest]
Thread overview: 26+ 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-09-08 16:16 ` [PATCH] mfd: intel-lpss: add Dell Latitude 7275 to the resource conflict quirk D. Manresa
2026-09-08 16:23 ` Hans de Goede
2026-09-09 4:46 ` Andy Shevchenko
2026-09-09 6:51 ` D. Manresa
2026-09-09 15:10 ` Lee Jones
2026-09-09 15:19 ` Sakari Ailus
2026-09-09 16:09 ` Andy Shevchenko
2026-09-10 9:47 ` Lee Jones
2026-09-10 15:17 ` Andy Shevchenko
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 [this message]
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
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=apavJ8OOEIv6DC4T@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.