mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@oss.nxp.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Conor Dooley <conor@kernel.org>,
	Support Opensource <support.opensource@diasemi.com>,
	Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
	"open list:MULTIFUNCTION DEVICES (MFD)" <mfd@lists.linux.dev>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: mfd: da9052: allow dlg,da9053-aa fallback to dlg,da9052
Date: Thu, 3 Sep 2026 14:15:37 -0500	[thread overview]
Message-ID: <apnHWWJ5a-gAGQUq@SMW015318> (raw)
In-Reply-To: <20260903-succinct-military-macaw-9e6e71@quoll>

On Thu, Sep 03, 2026 at 12:04:42PM +0200, Krzysztof Kozlowski wrote:
> On Tue, Sep 01, 2026 at 06:00:31PM +0100, Conor Dooley wrote:
> > On Mon, Aug 31, 2026 at 04:15:21PM -0400, Frank.Li@oss.nxp.com wrote:
> > > From: Frank Li <Frank.Li@nxp.com>
> > >
> > > Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
> > > years) check_dtbs warnings:
> > >   arch/arm/boot/dts/nxp/imx/imx53-voipac-bsb.dtb: dialog@48 (dlg,da9053-aa): compatible: ['dlg,da9053-aa', 'dlg,da9052'] is too long
> > >         from schema $id: http://devicetree.org/schemas/mfd/dlg,da9052.yaml
> > >
> > > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > > ---
> > > Previous try drop dlg,da9052 at
> > > https://lore.kernel.org/imx/20260404-thoughtful-placid-boobook-da26da@quoll/
> > >
> > > but Krzy have concern about compablity.
> > >
> > > https://lore.kernel.org/imx/20251107-matrimony-showdown-ba6ce6996b2f@spud/
> > >
> > > Conor prefer update old dts.
> >
> > I don't think these devices are actually compatible, so this fallback
> > would be wrong.
> > The data comes from the match data, be that spi or i2c, and there's
> > explicitly different behaviour for the da9052 and da9053aa.
>
> Maybe I looked at wrong driver, where is the difference? I made a very
> quick glance and I found the only difference in da9052_i2c_fix():
>
>  59         switch (da9052->chip_id) {
>  60         case DA9052:
>  61         case DA9053_AA:
>  62         case DA9053_BA:
>  63         case DA9053_BB:
>
> No differences in "da9052-core.c" and SPI, while looking for these
> device type enum values.

It is mfd, probe child device, like da9052-regulator.c

DA9052 vs DA9053-AA Differences (from da9052-regulator.c)
1. BUCK4 Voltage Range (only regulator table difference)
		DA9052 BUCK4	DA9053-AA BUCK4
Min voltage	1800 mV		950 mV
Max voltage	3600 mV		2525 mV
Step size	50 mV		25 mV

DA9052 BUCK4 also has a non-linear voltage mapping above 3V (step increases
to 100 mV for selector >= 24). DA9053-AA BUCK4 has no such special mapping.

2. BUCK Current Limits
Level	DA9052 (all BUCKs)	DA9053-AA BUCK1		DA9053-AA BUCK2/3/4
0	700 mA			1600 mA			800 mA
1	800 mA			2000 mA			1000 mA
2	1000 mA			2400 mA			1200 mA
3	1200 mA			3000 mA			1500 mA

DA9053-AA BUCK1 supports up to 3A (vs 1.2A on DA9052).

Frank

>
> > I doubt the legacy platform ever worked properly, and this is what should
> > have been explained in the PR that Krzysztof denied not just blindly
> > citing a dtbs_check problem.
>
> Well, yeah, I wanted an accurate reason with actual analysis, not
> necessarily making devices compatible if they are not.
>
> >
> > Nacked-by: Conor Dooley <conor.dooley@microchip.com>
>
> Best regards,
> Krzysztof
>

  parent reply	other threads:[~2026-09-03 19:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 20:15 Frank.Li
2026-09-01 17:00 ` Conor Dooley
2026-09-02 10:25   ` Lee Jones
2026-09-02 17:01     ` Conor Dooley
2026-09-03  9:06       ` Lee Jones
2026-09-03 10:06         ` Krzysztof Kozlowski
2026-09-03 11:36           ` Lee Jones
2026-09-03 10:04   ` Krzysztof Kozlowski
2026-09-03 15:34     ` Conor Dooley
2026-09-03 19:15     ` Frank Li [this message]
2026-09-03  9:58 ` Krzysztof Kozlowski
2026-09-03 19:22   ` Frank Li

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=apnHWWJ5a-gAGQUq@SMW015318 \
    --to=frank.li@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfd@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=support.opensource@diasemi.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

all inboxes | Powered by JetHome®