From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ioana Ciornei <ioana.ciornei@nxp.com>,
lee@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, shawnguo@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, vladimir.oltean@nxp.com
Subject: Re: [PATCH v3 3/6] arm64: dts: lx2160a-qds: make the QIXIS CPLD use the simple-mfd-i2c.c driver
Date: Fri, 16 May 2025 21:40:08 +0200 [thread overview]
Message-ID: <59c5e3b8-09c9-486b-8e17-85fd455020a8@kernel.org> (raw)
In-Reply-To: <20250515155628.233007-4-ioana.ciornei@nxp.com>
On 15/05/2025 17:56, Ioana Ciornei wrote:
> The MDIO mux on the LX2160A-QDS never worked in mainline. This is
> because the on-board QIXIS FPGA does not have a driver that could probe
> it and register an I2C regmap for it which could, afterwards, be used by
> the child devices - such as the mux-controller.
>
> There is a downstream driver for the QIXIS CPLD:
>
> https://github.com/nxp-qoriq/linux/blob/lf-6.12.y/drivers/soc/fsl/qixis_ctrl.c
>
> That driver is very similar to the already existing drivers/mfd/simple-mfd-i2c.c,
> and the hardware works with the simple-mfd-i2c driver, so there isn't
> any reason to upstream the other one.
>
> Since we want the QIXIS CPLD to have child nodes with "reg" and the
> current format lacks that, change the compatible string so that we make
> it clear that by using the simple-mfd-i2c driver, and its
> fsl,lx2160a-qds-qixis-cpld compatible, we expect dt nodes children with
> the reg property.
We are repeating the same over and over and I am getting bored. I do not
see any reason to change the compatible. Whether you want to use
simple-mfd driver or not, is not relevant here. Does not matter. Whether
device was really working or not, is not relevant either.
There is a device with given compatible, explain why this compatible is
wrong. Without arguments for that, old compatible must stay.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-16 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 15:56 [PATCH v3 0/6] mfd: simple-mfd-i2c: add QIXIS CPLD support Ioana Ciornei
2025-05-15 15:56 ` [PATCH v3 1/6] dt-bindings: mfd: add bindings for QIXIS CPLD Ioana Ciornei
2025-05-16 19:38 ` Krzysztof Kozlowski
2025-05-15 15:56 ` [PATCH v3 2/6] mfd: simple-mfd-i2c: add compatible string for Layerscape " Ioana Ciornei
2025-05-15 15:56 ` [PATCH v3 3/6] arm64: dts: lx2160a-qds: make the QIXIS CPLD use the simple-mfd-i2c.c driver Ioana Ciornei
2025-05-16 19:40 ` Krzysztof Kozlowski [this message]
2025-05-15 15:56 ` [PATCH v3 4/6] arm64: dts: lx2162a-qds: " Ioana Ciornei
2025-05-15 15:56 ` [PATCH v3 5/6] arm64: dts: ls1028a-qds: " Ioana Ciornei
2025-05-15 15:56 ` [PATCH v3 6/6] arm64: dts: lx2160a-qds: add the two on-board RGMII PHYs Ioana Ciornei
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=59c5e3b8-09c9-486b-8e17-85fd455020a8@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).