From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Huacai Chen <chenhc@lemote.com>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
Huacai Chen <chenhuacai@gmail.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH 1/2] MIPS: Loongson: Rename CPU device-tree binding
Date: Wed, 8 Jul 2020 11:33:30 +0200 [thread overview]
Message-ID: <20200708093330.GA9458@alpha.franken.de> (raw)
In-Reply-To: <1592201057-28151-1-git-send-email-chenhc@lemote.com>
On Mon, Jun 15, 2020 at 02:04:16PM +0800, Huacai Chen wrote:
> Loongson-3A R1/R2/R3 and Loongson-3B R1/R2 use the same package naming
> in dts, and Loongson-3A R4 will be different. In cpu.h the classic 64bit
> Loongson processors are called Loongson64C (C for classic, pre Loongson-
> 3A R4), and the new 64bit Loongson processors are called Loongson64G (G
> for generic, Loongson-3A R4+). To keep consistency and make extensible,
> we rename the classic "loongson3" prefix to "loongson64c", and the new
> prefix for Loongson-3A R4+ will be "loongson64g".
>
> Signed-off-by: Huacai Chen <chenhc@lemote.com>
> ---
> Documentation/devicetree/bindings/mips/loongson/devices.yaml | 8 ++++----
> arch/mips/boot/dts/loongson/Makefile | 2 +-
> .../loongson/{loongson3-package.dtsi => loongson64c-package.dtsi} | 0
> .../{loongson3_4core_rs780e.dts => loongson64c_4core_rs780e.dts} | 2 +-
> .../{loongson3_8core_rs780e.dts => loongson64c_8core_rs780e.dts} | 2 +-
> arch/mips/include/asm/mach-loongson64/builtin_dtbs.h | 4 ++--
> arch/mips/loongson64/env.c | 4 ++--
> 7 files changed, 11 insertions(+), 11 deletions(-)
> rename arch/mips/boot/dts/loongson/{loongson3-package.dtsi => loongson64c-package.dtsi} (100%)
> rename arch/mips/boot/dts/loongson/{loongson3_4core_rs780e.dts => loongson64c_4core_rs780e.dts} (93%)
> rename arch/mips/boot/dts/loongson/{loongson3_8core_rs780e.dts => loongson64c_8core_rs780e.dts} (93%)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-07-08 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 6:04 [PATCH 1/2] MIPS: Loongson: Rename CPU device-tree binding Huacai Chen
2020-06-15 6:04 ` [PATCH 2/2] dt-bindings: mips: Document two Loongson boards Huacai Chen
2020-07-08 9:33 ` Thomas Bogendoerfer
2020-07-08 9:33 ` Thomas Bogendoerfer [this message]
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=20200708093330.GA9458@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenhc@lemote.com \
--cc=chenhuacai@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).