From: Oleksij Rempel <ore@pengutronix.de>
To: Sam Ravnborg <sam@ravnborg.org>,
Oleksij Rempel <o.rempel@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v1] MIPS: add 74Kc info
Date: Thu, 27 Jul 2017 09:46:02 +0200 [thread overview]
Message-ID: <f14f2f29-9b28-cff3-e67b-7793b01238d2@pengutronix.de> (raw)
In-Reply-To: <20170727073906.GA12578@ravnborg.org>
Hi Sam,
i assumed, every one who maintains MIPS arch, knows it :)
ok. I'll keep it in mind.
On 27.07.2017 09:39, Sam Ravnborg wrote:
> Hi Oleksij.
>
> Nitpick...
> It would be nice to have the subject indicating this is a MIPS CPU.
> There may be a few people that do not recognize that 74Kc is
> a MIPS CPU (me at least).
>
> Sam
>
> On Thu, Jul 27, 2017 at 07:59:08AM +0200, Oleksij Rempel wrote:
>> This patch is preparation for SoC QCA AR9344
>>
>> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
>> ---
>> arch/mips/include/asm/cpu.h | 2 ++
>> arch/mips/lib/cpu-probe.c | 4 ++++
>> 2 files changed, 6 insertions(+)
>>
>> diff --git a/arch/mips/include/asm/cpu.h b/arch/mips/include/asm/cpu.h
>> index 572cabba34..e0bb78ea61 100644
>> --- a/arch/mips/include/asm/cpu.h
>> +++ b/arch/mips/include/asm/cpu.h
>> @@ -51,6 +51,7 @@
>>
>> #define PRID_IMP_24K 0x9300
>> #define PRID_IMP_24KE 0x9600
>> +#define PRID_IMP_74K 0x9700
>>
>> /*
>> * These are the PRID's for when 23:16 == PRID_COMP_BROADCOM
>> @@ -105,6 +106,7 @@ enum cpu_type_enum {
>> * MIPS32 class processors
>> */
>> CPU_24K,
>> + CPU_74K,
>> CPU_BMIPS3300,
>> CPU_JZRISC,
>> CPU_LOONGSON1,
>> diff --git a/arch/mips/lib/cpu-probe.c b/arch/mips/lib/cpu-probe.c
>> index 71dbaf6382..b5d63db189 100644
>> --- a/arch/mips/lib/cpu-probe.c
>> +++ b/arch/mips/lib/cpu-probe.c
>> @@ -106,6 +106,10 @@ static inline void cpu_probe_mips(struct cpuinfo_mips *c)
>> c->cputype = CPU_24K;
>> __cpu_name = "MIPS 24Kc";
>> break;
>> + case PRID_IMP_74K:
>> + c->cputype = CPU_74K;
>> + __cpu_name = "MIPS 74Kc";
>> + break;
>> }
>> }
>>
>> --
>> 2.11.0
>>
>>
>> _______________________________________________
>> barebox mailing list
>> barebox@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/barebox
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-07-27 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 5:59 Oleksij Rempel
2017-07-27 7:39 ` Sam Ravnborg
2017-07-27 7:46 ` Oleksij Rempel [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=f14f2f29-9b28-cff3-e67b-7793b01238d2@pengutronix.de \
--to=ore@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=o.rempel@pengutronix.de \
--cc=sam@ravnborg.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