[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <rnqlswgkn2gl4yprxu4h4a3fp3ajelf2ksinjjq72f73bqzxsl@icxg7v5ujzbs>
Date: Sat, 4 Jan 2025 11:14:58 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Shree Ramamoorthy <s-ramamoorthy@...com>
Cc: lgirdwood@...il.com, broonie@...nel.org, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, aaro.koskinen@....fi, andreas@...nade.info,
khilman@...libre.com, rogerq@...nel.org, tony@...mide.com, jerome.neanne@...libre.com,
linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
m-leonard@...com, praneeth@...com, christophe.jaillet@...adoo.fr
Subject: Re: [PATCH v2 5/7] regulator: tps65215: Update platform_device_id
table
On Fri, Jan 03, 2025 at 05:04:44PM -0600, Shree Ramamoorthy wrote:
> Add TI TPS65215 PMIC to the existing platform_device_id struct, so the
> regulator probe() can match which PMIC chip_data information.
Why is this a separate commit? Adding new device support is one commit -
so the tables, regulator definition and the quirks/ID table.
The next commit will be adding new entry to of_device_id?
Best regards,
Krzysztof
Powered by blists - more mailing lists