All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Russell King <linux@armlinux.org.uk>,
	Kukjin Kim <kgene@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	kernel@collabora.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"linux-samsung-soc@vger.kernel.org" 
	<linux-samsung-soc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] ARM: exynos: clear L310_AUX_CTRL_NS_LOCKDOWN in default l2c_aux_val
Date: Tue, 1 Sep 2020 15:45:00 +0200	[thread overview]
Message-ID: <CAJKOXPczS_RpSFpjGygZ_1MCYxJ_cUDRjriZvrHd6+zhmq=c8Q@mail.gmail.com> (raw)
In-Reply-To: <c0509b5f-a064-2e73-7e04-51f41a56d222@collabora.com>

On Tue, 1 Sep 2020 at 15:34, Guillaume Tucker
<guillaume.tucker@collabora.com> wrote:
>
> Hi Krzysztof, Russell,
>
> On 10/08/2020 13:22, Guillaume Tucker wrote:
> > The L310_AUX_CTRL_NS_LOCKDOWN flag is set during the L2C enable
> > sequence.  There is no need to set it in the default register value,
> > this was done before support for it was implemented in the code.  It
> > is not set in the hardware initial value either.
> >
> > Clean this up by removing this flag from the default l2c_aux_val, and
> > add it to the l2c_aux_mask to print an alert message if it was already
> > set before the kernel initialisation.
> >
> > Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>
> > ---
> >
> > Notes:
> >     v2: fix flag name L310_AUX_CTRL_NS_LOCKDOWN
> >
> >  arch/arm/mach-exynos/exynos.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
>
> I believe this v2 series has addressed all previous comments and
> you were waiting for the 5.9 merge window to end.  The patches
> all still apply cleanly on v5.9-rc3.  Do you want me to resend
> the series anyway or is there anything else needed at this point?
>
> Maybe one thing that wasn't completely clear in v1 was whether
> patch 2/4 was the right approach.  I've explained the reason
> behind it but didn't get a final reply from Russell[1].

I am sorry, my bad. I already applied this one and 3/4 (dts).
Apparently I forgot to reply with confirmation and Patchwork did not
notify you for some reason.

Patch 2/4 does not look like one for me so I would need ack from
Russell to take. Did you submit it to the ARM patches queue?
Patch 4/4 will wait for v5.10-rc1 as it depends on 1/4 and it is DTS patch.

Best regards,
Krzysztof

WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: devicetree@vger.kernel.org,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Rob Herring <robh+dt@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Kukjin Kim <kgene@kernel.org>,
	kernel@collabora.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] ARM: exynos: clear L310_AUX_CTRL_NS_LOCKDOWN in default l2c_aux_val
Date: Tue, 1 Sep 2020 15:45:00 +0200	[thread overview]
Message-ID: <CAJKOXPczS_RpSFpjGygZ_1MCYxJ_cUDRjriZvrHd6+zhmq=c8Q@mail.gmail.com> (raw)
In-Reply-To: <c0509b5f-a064-2e73-7e04-51f41a56d222@collabora.com>

On Tue, 1 Sep 2020 at 15:34, Guillaume Tucker
<guillaume.tucker@collabora.com> wrote:
>
> Hi Krzysztof, Russell,
>
> On 10/08/2020 13:22, Guillaume Tucker wrote:
> > The L310_AUX_CTRL_NS_LOCKDOWN flag is set during the L2C enable
> > sequence.  There is no need to set it in the default register value,
> > this was done before support for it was implemented in the code.  It
> > is not set in the hardware initial value either.
> >
> > Clean this up by removing this flag from the default l2c_aux_val, and
> > add it to the l2c_aux_mask to print an alert message if it was already
> > set before the kernel initialisation.
> >
> > Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>
> > ---
> >
> > Notes:
> >     v2: fix flag name L310_AUX_CTRL_NS_LOCKDOWN
> >
> >  arch/arm/mach-exynos/exynos.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
>
> I believe this v2 series has addressed all previous comments and
> you were waiting for the 5.9 merge window to end.  The patches
> all still apply cleanly on v5.9-rc3.  Do you want me to resend
> the series anyway or is there anything else needed at this point?
>
> Maybe one thing that wasn't completely clear in v1 was whether
> patch 2/4 was the right approach.  I've explained the reason
> behind it but didn't get a final reply from Russell[1].

I am sorry, my bad. I already applied this one and 3/4 (dts).
Apparently I forgot to reply with confirmation and Patchwork did not
notify you for some reason.

Patch 2/4 does not look like one for me so I would need ack from
Russell to take. Did you submit it to the ARM patches queue?
Patch 4/4 will wait for v5.10-rc1 as it depends on 1/4 and it is DTS patch.

Best regards,
Krzysztof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-09-01 13:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 12:22 [PATCH v2 1/4] ARM: exynos: clear L310_AUX_CTRL_NS_LOCKDOWN in default l2c_aux_val Guillaume Tucker
2020-08-10 12:22 ` Guillaume Tucker
2020-08-10 12:22 ` [PATCH v2 2/4] ARM: l2c: fix prefetch bits init in L2X0_AUX_CTRL using DT values Guillaume Tucker
2020-08-10 12:22   ` Guillaume Tucker
2020-08-10 12:22 ` [PATCH v2 3/4] ARM: dts: exynos: add prefetch properties for L2C-310 cache Guillaume Tucker
2020-08-10 12:22   ` Guillaume Tucker
2020-08-10 12:22 ` [PATCH v2 4/4] ARM: exynos: clear prefetch bits in default l2c_aux_val Guillaume Tucker
2020-08-10 12:22   ` Guillaume Tucker
2020-10-31 11:49   ` Krzysztof Kozlowski
2020-10-31 11:49     ` Krzysztof Kozlowski
2020-09-01 13:34 ` [PATCH v2 1/4] ARM: exynos: clear L310_AUX_CTRL_NS_LOCKDOWN " Guillaume Tucker
2020-09-01 13:34   ` Guillaume Tucker
2020-09-01 13:45   ` Krzysztof Kozlowski [this message]
2020-09-01 13:45     ` Krzysztof Kozlowski
2020-09-01 13:51     ` Krzysztof Kozlowski
2020-09-01 13:51       ` Krzysztof Kozlowski
2020-09-01 14:42       ` Guillaume Tucker
2020-09-01 14:42         ` Guillaume Tucker
2020-09-01 15:25         ` Krzysztof Kozlowski
2020-09-01 15:25           ` Krzysztof Kozlowski
2020-09-01 17:00           ` Guillaume Tucker
2020-09-01 17:00             ` Guillaume Tucker

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='CAJKOXPczS_RpSFpjGygZ_1MCYxJ_cUDRjriZvrHd6+zhmq=c8Q@mail.gmail.com' \
    --to=krzk@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=guillaume.tucker@collabora.com \
    --cc=kernel@collabora.com \
    --cc=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.