From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
krzk+dt@kernel.org, arinc.unal@arinc9.com
Subject: Re: [PATCH v2] dt-bindings: mips: add CPU bindings for MIPS architecture
Date: Sun, 18 Sep 2022 13:22:45 +0200 [thread overview]
Message-ID: <20220918112245.GA5555@alpha.franken.de> (raw)
In-Reply-To: <20220917041136.526446-1-sergio.paracuellos@gmail.com>
On Sat, Sep 17, 2022 at 06:11:36AM +0200, Sergio Paracuellos wrote:
> + compatible:
> + enum:
> + - brcm,bmips3300
> + - brcm,bmips4350
> + - brcm,bmips4380
> + - brcm,bmips5000
> + - brcm,bmips5200
> + - ingenic,xburst-mxu1.0
> + - ingenic,xburst-fpu1.0-mxu1.1
> + - ingenic,xburst-fpu2.0-mxu2.0
> + - loongson,gs264
> + - mips,mips1004Kc
> + - mips,m14Kc
> + - mips,mips24KEc
> + - mips,mips4KEc
could you add mips,mips4Kc ? I have a board, which I'm switching to
DT, which uses that core.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2022-09-18 11:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 4:11 [PATCH v2] dt-bindings: mips: add CPU bindings for MIPS architecture Sergio Paracuellos
2022-09-18 11:22 ` Thomas Bogendoerfer [this message]
2022-09-18 15:15 ` Sergio Paracuellos
2022-09-19 11:17 ` Krzysztof Kozlowski
2022-09-19 12:29 ` Sergio Paracuellos
2022-09-19 12:48 ` Krzysztof Kozlowski
2022-09-19 13:41 ` Sergio Paracuellos
2022-09-19 16:08 ` Krzysztof Kozlowski
2022-09-20 5:51 ` Sergio Paracuellos
2022-09-21 6:42 ` Krzysztof Kozlowski
2022-09-21 7:18 ` Sergio Paracuellos
2022-09-21 7:51 ` Krzysztof Kozlowski
2022-09-21 8:11 ` Sergio Paracuellos
2022-09-21 11:40 ` Sergio Paracuellos
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=20220918112245.GA5555@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@gmail.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