From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: Tony Wu <tung7970@gmail.com>,
"ralf@linux-mips.org" <ralf@linux-mips.org>,
"macro@linux-mips.org" <macro@linux-mips.org>
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"Steven J. Hill" <Steven.Hill@imgtec.com>
Subject: Re: [PATCH] MIPS: 74K/1074K: Fix typo in erratum workaround.
Date: Tue, 6 Jan 2015 12:07:09 -0800 [thread overview]
Message-ID: <54AC406D.4030106@imgtec.com> (raw)
In-Reply-To: <20150106183732-tung7970@googlemail.com>
On 01/06/2015 02:39 AM, Tony Wu wrote:
> In commit 9213ad (MIPS: 74K/1074K: Correct erratum workaround.),
> MIPS_CACHE_VTAG should go to icache.flags.
>
> Signed-off-by: Tony Wu <tung7970@gmail.com>
> Cc: Maciej W. Rozycki <macro@linux-mips.org>
> Cc: Steven J. Hill <Steven.Hill@imgtec.com>
> Cc: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
>
> diff --git a/arch/mips/mm/c-r4k.c b/arch/mips/mm/c-r4k.c
> index dd261df..deebd0b 100644
> --- a/arch/mips/mm/c-r4k.c
> +++ b/arch/mips/mm/c-r4k.c
> @@ -902,13 +902,13 @@ static inline void alias_74k_erratum(struct cpuinfo_mips *c)
> switch (imp) {
> case PRID_IMP_74K:
> if (rev <= PRID_REV_ENCODE_332(2, 4, 0))
> - c->dcache.flags |= MIPS_CACHE_VTAG;
> + c->icache.flags |= MIPS_CACHE_VTAG;
> if (rev == PRID_REV_ENCODE_332(2, 4, 0))
> write_c0_config6(read_c0_config6() | MIPS_CONF6_SYND);
> break;
> case PRID_IMP_1074K:
> if (rev <= PRID_REV_ENCODE_332(1, 1, 0)) {
> - c->dcache.flags |= MIPS_CACHE_VTAG;
> + c->icache.flags |= MIPS_CACHE_VTAG;
> write_c0_config6(read_c0_config6() | MIPS_CONF6_SYND);
> }
> break;
It is not a typo, it is a special case and an original patch should
follow the patch
http://patchwork.linux-mips.org/patch/8459/
which has a use of 'cpu_has_vtag_dcache'
- Leonid.
prev parent reply other threads:[~2015-01-06 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 10:39 [PATCH] MIPS: 74K/1074K: Fix typo in erratum workaround Tony Wu
2015-01-06 20:07 ` Leonid Yegoshin [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=54AC406D.4030106@imgtec.com \
--to=leonid.yegoshin@imgtec.com \
--cc=Steven.Hill@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=tung7970@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