linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jlu@pengutronix.de (Jan Lübbe)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 3/4] ARM: l2x0: add arm,ecc-enable property for aurora
Date: Thu, 22 Jun 2017 16:46:30 +0200	[thread overview]
Message-ID: <1498142790.2533.80.camel@pengutronix.de> (raw)
In-Reply-To: <220533aeb8f64e829f483e38e209cdc8@svr-chch-ex1.atlnz.lc>

Chris,

On So, 2017-06-11 at 22:55 +0000, Chris Packham wrote:
> On 09/06/17 20:58, Jan L?bbe wrote:
> > On Do, 2017-06-08 at 16:11 +1200, Chris Packham wrote:
> >> +       if (of_property_read_bool(np, "arm,ecc-enable")) {
> >> +               mask |= L2C_AUX_CTRL_EVTMON_ENABLE;
> >> +               val |= L2C_AUX_CTRL_EVTMON_ENABLE;
> >> +       } else if (of_property_read_bool(np, "arm,ecc-disable")) {
> >> +               mask |= L2C_AUX_CTRL_EVTMON_ENABLE;
> >> +       }
> > 
> > Unless I misunderstand the code in __l2c_init(), the mask is used to
> > specify the bits to preserve:
> >          old_aux = aux = readl_relaxed(l2x0_base + L2X0_AUX_CTRL);
> >          aux &= aux_mask;
> >          aux |= aux_val;
> > 
> >          if (old_aux != aux)
> >                  pr_warn("L2C: DT/platform modifies aux control register: 0x%08x -> 0x%08x\n",
> >                          old_aux, aux);
> > 
> > So the arm,ecc-disable property will have no effect. This probably also
> > applies to patch 2/4. The existing property *-disable code removes the
> > corresponding bit from the mask.
> 
> Indeed the disable version should be mask &= ~L2C_AUX_CTRL_EVTMON_ENABLE 
> and I was probably a little lazy to have used the L2C EVTMON instead of 
> adding AURORA specific ones like you have in your series.
> 
> I'll rebase my series on top of yours and send it direct to you so you 
> can include it in the overall submission.

While picking up your arm,parity-enable and arm,ecc-enable patches for
my series, I noticed that the mask variable is inverted when merging the
local changes into aux_val/aux_mask at the end of aurora_of_parse. So I
now believe your code is correct. ;) I'd appreciate a close look,
nevertheless.

Regards,
Jan

  reply	other threads:[~2017-06-22 14:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08  4:11 [RFC PATCH 0/4] EDAC support for Marvell Armada SoCs Chris Packham
2017-06-08  4:11 ` [RFC PATCH 1/4] EDAC: mvebu: Add driver " Chris Packham
2017-06-09 10:39   ` Borislav Petkov
2017-06-09 13:14   ` Jan Lübbe
     [not found]     ` <1497016569.3536.84.camel@pengutronix.de>
2017-06-09 16:13       ` DMA-safety for edac_atomic_scrub on ARM Rob Herring
2017-06-11 22:37     ` [RFC PATCH 1/4] EDAC: mvebu: Add driver for Marvell Armada SoCs Chris Packham
2017-06-22 14:11     ` Jan Lübbe
2017-06-22 21:43       ` Chris Packham
2017-06-08  4:11 ` [RFC PATCH 2/4] ARM: l2x0: support parity-enable/disable on aurora Chris Packham
2017-06-08  4:11 ` [RFC PATCH 3/4] ARM: l2x0: add arm,ecc-enable property for aurora Chris Packham
2017-06-09  8:58   ` Jan Lübbe
2017-06-11 22:55     ` [RFC PATCH 3/4] ARM: l2x0: add arm, ecc-enable " Chris Packham
2017-06-22 14:46       ` Jan Lübbe [this message]
2017-06-22 21:50         ` Chris Packham
2017-06-09 16:29   ` Rob Herring
2017-06-08  4:11 ` [RFC PATCH 4/4] ARM: dts: enable l2c parity and ecc protection on 98dx3236 Chris Packham

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=1498142790.2533.80.camel@pengutronix.de \
    --to=jlu@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).