From: Rob Herring <robh@kernel.org>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-m68k@lists.linux-m68k.org, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 4/5] dt-bindings: serial: create binding for mcf-uart
Date: Tue, 27 Oct 2026 16:07:02 -0500 [thread overview]
Message-ID: <20261027210702.GA948124-robh@kernel.org> (raw)
In-Reply-To: <73a8df68-17da-4275-bb9d-8a6272b754e6@linux-m68k.org>
On Thu, Oct 15, 2026 at 11:14:26PM +1000, Greg Ungerer wrote:
> Hi Geert,
>
> On 15/10/26 19:19, Geert Uytterhoeven wrote:
> > On Wed, 14 Oct 2026 at 14:56, Greg Ungerer <gerg@linux-m68k.org> wrote:
> >> On 14/10/26 21:24, Krzysztof Kozlowski wrote:
> >>> On Tue, Oct 13, 2026 at 10:07:02PM +1000, Greg Ungerer wrote:
> >>>> Create documentation for a new binding to support the Freescale ColdFire
> >>>> UART hardware block. This is found on pretty much all variants of the
> >>>> M68K derived Freescale ColdFire family of System-on-Chip devices.
> >>>>
> >>>> It is not compatible with any other known UARTs.
> >>>
> >>> You never tested this, so limited review.
> >>
> >> It is tested. It is working and running on multiple ColdFire platforms.
> >>
> >>>> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
> >
> >>>> --- /dev/null
> >>>> +++ b/Documentation/devicetree/bindings/serial/fsl,mcf-uart.yaml
> >
> >>>> +properties:
> >>>> + compatible:
> >>>> + const: fsl,mcf-uart
> >>>
> >>> What is the SoC name? MCF? Compatibles must be specific (see writing
> >>> bindings doc).
> >>
> >> Yes. MCF = "Motorola ColdFire". It is the SoC prefix used for naming of all
> >> ColdFire parts (which is dozens of variants):
> >>
> >> MCF5206
> >> MCF5208
> >> MCF5307
> >> MCF54415
> >> etc
> >>
> >> Even when Motorola became Freescale they stuck with MCF on all ColdFire parts.
> >
> > I guess you want:
> >
> > items:
> > - enum:
> > - fsl,mcf5206
> > - fsl,mcf5208
> > - fsl,mcf5307
> > [...]
> > - const: fsl,mcf-uart
> >
> > As no new (possibly incompatible) Coldfire parts will appear, a generic
> > fallback looks reasonable to me.
>
> It will be a long list of variants - thanks Freescale. Quite a few of the SoC
> parts have sub-parts with different single digits, for example:
>
> mcf54410, mcf54415, mcf54416, mcf54417, mcf54118
I imagine all of those are just package or marketing differences.
Freescale did not have the money to tapeout 5 different parts. Just
using one compatible for all of them is fine.
> At a quick count I can see about 42 variants.
> I don't mind adding the full list if that is preferred.
Just add what you care about or know people use. I imagine that's a much
smaller subset.
Probably not many users today of the 5272 I worked on which was designed
for ISDN modems.
Rob
next prev parent reply other threads:[~2026-10-27 21:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 12:06 [PATCH 0/5] serial: mcf: add devicetree support Greg Ungerer
2026-10-13 12:06 ` [PATCH 1/5] serial: mcf: update author email address Greg Ungerer
2026-10-13 12:14 ` sashiko-bot
2026-10-13 12:07 ` [PATCH 2/5] serial: mcf: convert to use proper platform resources Greg Ungerer
2026-10-13 12:24 ` sashiko-bot
2026-10-13 12:07 ` [PATCH 3/5] serial: mcf: dynamically allocate memory Greg Ungerer
2026-10-13 12:38 ` sashiko-bot
2026-10-13 12:07 ` [PATCH 4/5] dt-bindings: serial: create binding for mcf-uart Greg Ungerer
2026-10-13 12:40 ` sashiko-bot
2026-10-14 11:24 ` Krzysztof Kozlowski
2026-10-14 12:48 ` Greg Ungerer
2026-10-15 8:56 ` Krzysztof Kozlowski
2026-10-15 12:44 ` Greg Ungerer
2026-10-15 13:06 ` Geert Uytterhoeven
2026-10-15 14:01 ` Greg Ungerer
2026-10-15 9:19 ` Geert Uytterhoeven
2026-10-15 9:58 ` Krzysztof Kozlowski
2026-10-15 13:14 ` Greg Ungerer
2026-10-27 21:07 ` Rob Herring [this message]
2026-10-15 22:39 ` Finn Thain
2026-10-13 12:07 ` [PATCH 5/5] serial: mcf: add devicetree support Greg Ungerer
2026-10-13 12:49 ` sashiko-bot
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=20261027210702.GA948124-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=krzk@kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-serial@vger.kernel.org \
/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