dt-bindings: mfd: da9052: allow dlg,da9053-aa fallback to dlg,da9052
Subsystems (4)
PATCH 1/1 dt-bindings: mfd: da9052: allow dlg,da9053-aa fallback to dlg,da9052
From: Frank Li <[email protected]>
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
---
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.
--- Documentation/devicetree/bindings/mfd/dlg,da9052.yaml | 4 ++++ 1 file changed, 4 insertions(+)
Documentation/devicetree/bindings/mfd/dlg,da9052.yaml +4 -0
@@ -18,6 +18,10 @@ properties: - dlg,da9053-bb - dlg,da9053-bc - dlg,da9052 + - items: + - enum: + - dlg,da9053-aa + - const: dlg,da9052 reg: maxItems: 1
Signature · 1 line
2.43.0
[email protected]
AI reviewThank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider: - [Low] The patch introduces an inconsistency by explicitly allowing the legacy fallback compatible string…
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch introduces an inconsistency by explicitly allowing the legacy fallback compatible string dlg,da9053-aa with dlg,da9052, but omitting dlg,da9053 which uses the exact same pattern. --
commit abd213140dc2339cb1dfe32c3ccb7bfd92c4ba9b
Author: Frank Li <[email protected]>
dt-bindings: mfd: da9052: allow dlg,da9053-aa fallback to dlg,da9052
This patch adds a fallback compatible string schema allowing dlg,da9053-aa to fall back to dlg,da9052 in order to resolve a legacy platform check_dtbs warning.
Documentation/devicetree/bindings/mfd/dlg,da9052.yaml properties: · line 24
Quoted 12 lines
Documentation/devicetree/bindings/mfd/dlg,da9052.yaml +4
-0@@ -18,6 +18,10 @@ properties: - dlg,da9053-bb - dlg,da9053-bc - dlg,da9052 + - items: + - enum: + - dlg,da9053-aa + - const: dlg,da9052
[Severity: Low]
Does this fallback allowance also need to include the plain dlg,da9053 variant to completely fix the warnings?
Looking at arch/arm/boot/dts/nxp/imx/imx53-smd.dts, the pmic node still relies on the missing fallback pattern:
compatible = "dlg,da9053", "dlg,da9052";
Without including dlg,da9053 in the enum alongside dlg,da9053-aa, won't the legacy device tree node continue to generate a dtbs_check warning?
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=1
Quoted 12 lines · On Mon, Aug 31, 2026 at 04:15:21PM -0400, [email protected] wrote:
From: Frank Li <[email protected]>
Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
years)check_dtbswarnings:
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.yamlSigned-off-by Frank Li <[email protected]>---
Previous try drop dlg,da9052 at
https://lore.kernel.org/imx/20260404-thoughtful-placid-boobook-da26da@quoll/
Quoted 5 lines
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.
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.
Thanks,
Conor.
Quoted 22 lines
--- Documentation/devicetree/bindings/mfd/dlg,da9052.yaml | 4 ++++ 1 file changed, 4 insertions(+)Documentation/devicetree/bindings/mfd/dlg,da9052.yaml +4
-0@@ -18,6 +18,10 @@ properties: - dlg,da9053-bb - dlg,da9053-bc - dlg,da9052 + - items: + - enum: + - dlg,da9053-aa + - const: dlg,da9052 reg: maxItems: 1Signature · 1 line
2.43.0
Lee Jones
maintainerQuoted 27 lines · Conor Dooley
Quoted 12 lines · On Mon, Aug 31, 2026 at 04:15:21PM -0400, [email protected] wrote:
From: Frank Li <[email protected]>
Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
years)check_dtbswarnings:
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.yamlSigned-off-by Frank Li <[email protected]>---
Previous try drop dlg,da9052 at
https://lore.kernel.org/imx/20260404-thoughtful-placid-boobook-da26da@quoll/Quoted 5 lines
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 andda9053aa.
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 adtbs_checkproblem.
Quoted 1 line
Nacked-by Conor Dooley <[email protected]>
At first glance this looks like an Acked-by.
IMHO, this is going to cause issues - please rethink this.
Signature · 1 line
Lee Jones
Quoted 29 lines · Lee Jones
Quoted 27 lines · Conor Dooley
Quoted 12 lines · On Mon, Aug 31, 2026 at 04:15:21PM -0400, [email protected] wrote:
From: Frank Li <[email protected]>
Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
years)check_dtbswarnings:
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.yamlSigned-off-by Frank Li <[email protected]>---
Previous try drop dlg,da9052 at
https://lore.kernel.org/imx/20260404-thoughtful-placid-boobook-da26da@quoll/Quoted 5 lines
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 andda9053aa.
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 adtbs_checkproblem.
Quoted 5 lines
Quoted 1 line
Nacked-by Conor Dooley <[email protected]>At first glance this looks like an Acked-by.
IMHO, this is going to cause issues - please rethink this.
As in, use NAKed-by instead or just say NAK without the name/mail? Not entirely sure what you're getting at.
Cheers,
Conor.
Lee Jones
maintainerQuoted 30 lines · Conor Dooley
Quoted 29 lines · Lee Jones
Quoted 27 lines · Conor Dooley
Quoted 12 lines · On Mon, Aug 31, 2026 at 04:15:21PM -0400, [email protected] wrote:
From: Frank Li <[email protected]>
Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
years)check_dtbswarnings:
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.yamlSigned-off-by Frank Li <[email protected]>---
Previous try drop dlg,da9052 at
https://lore.kernel.org/imx/20260404-thoughtful-placid-boobook-da26da@quoll/Quoted 5 lines
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 andda9053aa.
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 adtbs_checkproblem.
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
Nacked-by Conor Dooley <[email protected]>At first glance this looks like an Acked-by.
IMHO, this is going to cause issues - please rethink this.
As in, use NAKed-by instead or just say NAK without the name/mail? Not entirely sure what you're getting at.
As in, don't make NACKs looks like acceptance trailers.
If you're going to "NACK", which I always felt was a bit harsh anyway, just say it without making it appear like an official sign-off. Please.
Signature · 1 line
Lee Jones
Quoted 38 lines · Lee Jones
Quoted 36 lines · Conor Dooley
Quoted 34 lines · Lee Jones
Quoted 27 lines · Conor Dooley
Quoted 12 lines · On Mon, Aug 31, 2026 at 04:15:21PM -0400, [email protected] wrote:
From: Frank Li <[email protected]>
Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
years)check_dtbswarnings:
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.yamlSigned-off-by Frank Li <[email protected]>---
Previous try drop dlg,da9052 at
https://lore.kernel.org/imx/20260404-thoughtful-placid-boobook-da26da@quoll/Quoted 5 lines
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 andda9053aa.
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 adtbs_checkproblem.Quoted 1 line
Nacked-by Conor Dooley <[email protected]>At first glance this looks like an Acked-by.
IMHO, this is going to cause issues - please rethink this.
Quoted 7 lines
Quoted 2 lines
As in, use NAKed-by instead or just say NAK without the name/mail? Not entirely sure what you're getting at.
As in, don't make NACKs looks like acceptance trailers.
If you're going to "NACK", which I always felt was a bit harsh anyway, just say it without making it appear like an official sign-off. Please.
Heh, tag is correct if maintainer, e.g. you in this case, would like to take such patch still. There were already such cases, I did it once as well to express that I do not agree with the approach taken by other maintainer and I want to be sure that a commit in git history will never be used in future discussions against my review (because this happens all the time "I found commit like this, so I can add here poor code").
Best regards,
Krzysztof
Lee Jones
maintainerQuoted 47 lines · Krzysztof Kozlowski
Quoted 38 lines · Lee Jones
Quoted 36 lines · Conor Dooley
Quoted 34 lines · Lee Jones
Quoted 27 lines · Conor Dooley
Quoted 12 lines · On Mon, Aug 31, 2026 at 04:15:21PM -0400, [email protected] wrote:
From: Frank Li <[email protected]>
Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
years)check_dtbswarnings:
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.yamlSigned-off-by Frank Li <[email protected]>---
Previous try drop dlg,da9052 at
https://lore.kernel.org/imx/20260404-thoughtful-placid-boobook-da26da@quoll/Quoted 5 lines
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 andda9053aa.
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 adtbs_checkproblem.Quoted 1 line
Nacked-by Conor Dooley <[email protected]>At first glance this looks like an Acked-by.
IMHO, this is going to cause issues - please rethink this.
Quoted 7 lines
Quoted 2 lines
As in, use NAKed-by instead or just say NAK without the name/mail? Not entirely sure what you're getting at.
As in, don't make NACKs looks like acceptance trailers.
If you're going to "NACK", which I always felt was a bit harsh anyway, just say it without making it appear like an official sign-off. Please.
Quoted 6 lines
Heh, tag is correct if maintainer, e.g. you in this case, would like to take such patch still. There were already such cases, I did it once as well to express that I do not agree with the approach taken by other maintainer and I want to be sure that a commit in git history will never be used in future discussions against my review (because this happens all the time "I found commit like this, so I can add here poor code").
I wouldn't take the patch if it was NACKed.
Signature · 1 line
Lee Jones
Quoted 15 lines · Conor Dooley
Quoted 14 lines · On Mon, Aug 31, 2026 at 04:15:21PM -0400, [email protected] wrote:
From: Frank Li <[email protected]>
Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
years)check_dtbswarnings:
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.yamlSigned-off-by Frank Li <[email protected]>---
Previous try drop dlg,da9052 at
https://lore.kernel.org/imx/20260404-thoughtful-placid-boobook-da26da@quoll/but Krzy have concern about compablity.
Quoted 8 lines
Quoted 3 lines
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 andda9053aa.
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.
Quoted 3 lines
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_checkproblem.
Well, yeah, I wanted an accurate reason with actual analysis, not necessarily making devices compatible if they are not.
Quoted 2 lines
Nacked-by Conor Dooley <[email protected]>
Best regards,
Krzysztof
Quoted 28 lines · Krzysztof Kozlowski
Quoted 15 lines · Conor Dooley
Quoted 14 lines · On Mon, Aug 31, 2026 at 04:15:21PM -0400, [email protected] wrote:
From: Frank Li <[email protected]>
Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
years)check_dtbswarnings:
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.yamlSigned-off-by Frank Li <[email protected]>---
Previous try drop dlg,da9052 at
https://lore.kernel.org/imx/20260404-thoughtful-placid-boobook-da26da@quoll/but Krzy have concern about compablity.
Quoted 8 lines
Quoted 3 lines
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 andda9053aa.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():
Quoted 8 lines
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.
If you look further afield, since this is an mfd, in the regulator driver there's a lot of conditions there that depend on the chip_id. E.g. current limits and voltage steps differ. There's also one in the battery driver.
Quoted 13 lines
Quoted 3 lines
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_checkproblem.Well, yeah, I wanted an accurate reason with actual analysis, not necessarily making devices compatible if they are not.
Quoted 2 lines
Nacked-by Conor Dooley <[email protected]>Best regards,
Krzysztof
Quoted 28 lines · Krzysztof Kozlowski
Quoted 15 lines · Conor Dooley
Quoted 14 lines · On Mon, Aug 31, 2026 at 04:15:21PM -0400, [email protected] wrote:
From: Frank Li <[email protected]>
Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
years)check_dtbswarnings:
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.yamlSigned-off-by Frank Li <[email protected]>---
Previous try drop dlg,da9052 at
https://lore.kernel.org/imx/20260404-thoughtful-placid-boobook-da26da@quoll/but Krzy have concern about compablity.
Quoted 8 lines
Quoted 3 lines
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 andda9053aa.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():
Quoted 8 lines
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
Quoted 14 lines
Quoted 4 lines
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_checkproblem.Well, yeah, I wanted an accurate reason with actual analysis, not necessarily making devices compatible if they are not.
Quoted 2 lines
Nacked-by Conor Dooley <[email protected]>Best regards,
Krzysztof
Quoted 26 lines · On Mon, Aug 31, 2026 at 04:15:21PM -0400, [email protected] wrote:
From: Frank Li <[email protected]>
Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
years)check_dtbswarnings:
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.yamlSigned-off-by Frank Li <[email protected]>---
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.
--- Documentation/devicetree/bindings/mfd/dlg,da9052.yaml | 4 ++++ 1 file changed, 4 insertions(+)Documentation/devicetree/bindings/mfd/dlg,da9052.yaml +0
-0
Documentation/devicetree/bindings/mfd/dlg,da9052.yaml properties: · line 24
Quoted 7 lines
Documentation/devicetree/bindings/mfd/dlg,da9052.yaml +4
-0@@ -18,6 +18,10 @@ properties: - dlg,da9053-bb - dlg,da9053-bc - dlg,da9052 + - items: + - enum: + - dlg,da9053-aa + - const: dlg,da9052
... and the dlg,da9053-aa alone from earlier enum should be removed and existing DTS corrected.
Best regards,
Krzysztof
Quoted 22 lines · Krzysztof Kozlowski
Quoted 21 lines · On Mon, Aug 31, 2026 at 04:15:21PM -0400, [email protected] wrote:
From: Frank Li <[email protected]>
Allow dlg,da9053-aa fallback to dlg,da9052 to fix legacy platform (> 10
years)check_dtbswarnings:
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.yamlSigned-off-by Frank Li <[email protected]>---
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.
--- Documentation/devicetree/bindings/mfd/dlg,da9052.yaml | 4 ++++ 1 file changed, 4 insertions(+)
Quoted 15 lines
Documentation/devicetree/bindings/mfd/dlg,da9052.yaml properties: · line 24
Quoted 12 lines
Documentation/devicetree/bindings/mfd/dlg,da9052.yaml +4
-0@@ -18,6 +18,10 @@ properties: - dlg,da9053-bb - dlg,da9053-bc - dlg,da9052 + - items: + - enum: + - dlg,da9053-aa + - const: dlg,da9052... and the dlg,da9053-aa alone from earlier enum should be removed and existing DTS corrected.
there are dlg,da9053-aa alone at arch/arm/boot/dts/nxp/imx/imx53-ppd.dts.
Mix use both because it is too old.
Frank
Quoted 4 lines
Best regards,
Krzysztof