public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jesse Taube" <mr.bossman075@gmail.com>,
	"NXP Linux Team" <linux-imx@nxp.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
	"Stephen Boyd" <sboyd@kernel.org>,
	"Shawn Guo" <shawnguo@kernel.org>,
	"Pengutronix Kernel Team" <kernel@pengutronix.de>,
	"Fabio Estevam" <festevam@gmail.com>,
	aisheng.dong@nxp.com, stefan@agner.ch,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Russell King" <linux@armlinux.org.uk>,
	abel.vesa@nxp.com, dev@lynxeye.de,
	"Marcel Ziswiler" <marcel.ziswiler@toradex.com>,
	tharvey@gateworks.com, leoyang.li@nxp.com, fugang.duan@nxp.com,
	"Giulio Benetti" <giulio.benetti@benettiengineering.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH v1 7/7] ARM: dts: imx: Update i.MXRT1050.dtsi compatibles
Date: Tue, 08 Nov 2022 12:07:33 +0100	[thread overview]
Message-ID: <d5f29c86-4bd8-4550-971e-4e941b1099f2@app.fastmail.com> (raw)
In-Reply-To: <ef5d4f48-71b9-2d5c-37f4-7a029a32a41b@gmail.com>

On Mon, Nov 7, 2022, at 16:09, Jesse Taube wrote:
> On 11/7/22 02:44, Arnd Bergmann wrote:
>> On Mon, Nov 7, 2022, at 08:15, Jesse Taube wrote:
>>> Remove unused compatibles from i.MXRT1050.dtsi.
>>> Change GPT clock-names to match documentation.
>>>
>>> Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>
>>> Signed-off-by: Jesse Taube <Mr.Bossman075@gmail.com>
>> 
>> Can you make sure your changelog texts explain why you do this?
> Yes, sorry I wasn't clear.
>
>> Are they fundamentally different from the devices you had
>> claimed to be compatible with that need a different driver,
>
> UART and SDHC had drivers added which are better fit.
> The GPT binds to imx6dl which is also the same as imx6sl.

Where are those drivers added? Looking at linux-6.1-rc2
and linux-next, I still see them use the same drivers as
the original ones, and listing both strings would be the
preferred method.

>> or are there drivers in the field that bind to the wrong
>> string first?
> I don't understand?

I mean if you had run into the case where you have
a driver that misbehaves when the fallback string is
present in addition to the most specific one.

     Arnd

  reply	other threads:[~2022-11-08 11:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  7:15 [PATCH v1 0/7] Clean-up and documentation for i.MXRT1050 Jesse Taube
2022-11-07  7:15 ` [PATCH v1 1/7] dt-bindings: arm: imx: Add i.MXRT compatible Documentation Jesse Taube
2022-11-07  7:15 ` [PATCH v1 2/7] dt-bindings: pinctrl: Fix file path for pinfunc include Jesse Taube
2022-11-07  7:15 ` [PATCH v1 3/7] dt-bindings: timer: gpt: Add i.MXRT compatible Documentation Jesse Taube
2022-11-07 12:16   ` Rob Herring
2022-11-07  7:15 ` [PATCH v1 4/7] dt-bindings: serial: fsl-lpuart: add i.MXRT1170 compatible Jesse Taube
2022-11-07  7:15 ` [PATCH v1 5/7] dt-bindings: mmc: fsl-imx-esdhc: " Jesse Taube
2022-11-07  7:15 ` [PATCH v1 6/7] pinctrl: freescale: Fix i.MXRT1050 pad names Jesse Taube
2022-11-07  7:15 ` [PATCH v1 7/7] ARM: dts: imx: Update i.MXRT1050.dtsi compatibles Jesse Taube
2022-11-07  7:44   ` Arnd Bergmann
2022-11-07 15:09     ` Jesse Taube
2022-11-08 11:07       ` Arnd Bergmann [this message]
2022-11-09  8:54   ` Linus Walleij
2022-11-09  8:52 ` [PATCH v1 0/7] Clean-up and documentation for i.MXRT1050 Linus Walleij

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=d5f29c86-4bd8-4550-971e-4e941b1099f2@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=abel.vesa@nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=dev@lynxeye.de \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=fugang.duan@nxp.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=leoyang.li@nxp.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=marcel.ziswiler@toradex.com \
    --cc=mr.bossman075@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    --cc=tharvey@gateworks.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