From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Robin Murphy <robin.murphy@arm.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Jeffrey Hugo <jhugo@codeaurora.org>,
MSM <linux-arm-msm@vger.kernel.org>,
AngeloGioacchino Del Regno <kholk11@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64/io: Don't use WZR in writel
Date: Thu, 2 May 2019 18:50:29 +0200 [thread overview]
Message-ID: <5b83a4c2-1f0e-337f-a78d-f7d84fe01ab3@free.fr> (raw)
In-Reply-To: <3757fc2d-0587-be46-8f75-6d79906be8bd@arm.com>
On 02/05/2019 18:33, Robin Murphy wrote:
> Both Angelo's and your reports strongly imply that the previous
> constant-folding debate was a red herring and the trivial fix[1] should
> still be sufficient, but nobody's given me actual confirmation of
> whether it is or isn't :(
Are you saying that when writing to any of
gr0_base + ARM_SMMU_GR0_TLBIALLH
gr0_base + ARM_SMMU_GR0_TLBIALLNSNH
base + ARM_SMMU_GR0_sTLBGSYNC
the actual value written does not matter? Is it ignored by the HW?
We could write 0xdeadbeef?
Regards.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Robin Murphy <robin.murphy@arm.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
MSM <linux-arm-msm@vger.kernel.org>,
Jeffrey Hugo <jhugo@codeaurora.org>,
AngeloGioacchino Del Regno <kholk11@gmail.com>
Subject: Re: [PATCH] arm64/io: Don't use WZR in writel
Date: Thu, 2 May 2019 18:50:29 +0200 [thread overview]
Message-ID: <5b83a4c2-1f0e-337f-a78d-f7d84fe01ab3@free.fr> (raw)
Message-ID: <20190502165029.BtewAl7h9jojr_NBF5wDdJ5u1_eNG7Y14xVEjbkZ2Ps@z> (raw)
In-Reply-To: <3757fc2d-0587-be46-8f75-6d79906be8bd@arm.com>
On 02/05/2019 18:33, Robin Murphy wrote:
> Both Angelo's and your reports strongly imply that the previous
> constant-folding debate was a red herring and the trivial fix[1] should
> still be sufficient, but nobody's given me actual confirmation of
> whether it is or isn't :(
Are you saying that when writing to any of
gr0_base + ARM_SMMU_GR0_TLBIALLH
gr0_base + ARM_SMMU_GR0_TLBIALLNSNH
base + ARM_SMMU_GR0_sTLBGSYNC
the actual value written does not matter? Is it ignored by the HW?
We could write 0xdeadbeef?
Regards.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Robin Murphy <robin.murphy@arm.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Jeffrey Hugo <jhugo@codeaurora.org>,
MSM <linux-arm-msm@vger.kernel.org>,
AngeloGioacchino Del Regno <kholk11@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64/io: Don't use WZR in writel
Date: Thu, 2 May 2019 18:50:29 +0200 [thread overview]
Message-ID: <5b83a4c2-1f0e-337f-a78d-f7d84fe01ab3@free.fr> (raw)
In-Reply-To: <3757fc2d-0587-be46-8f75-6d79906be8bd@arm.com>
On 02/05/2019 18:33, Robin Murphy wrote:
> Both Angelo's and your reports strongly imply that the previous
> constant-folding debate was a red herring and the trivial fix[1] should
> still be sufficient, but nobody's given me actual confirmation of
> whether it is or isn't :(
Are you saying that when writing to any of
gr0_base + ARM_SMMU_GR0_TLBIALLH
gr0_base + ARM_SMMU_GR0_TLBIALLNSNH
base + ARM_SMMU_GR0_sTLBGSYNC
the actual value written does not matter? Is it ignored by the HW?
We could write 0xdeadbeef?
Regards.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-02 16:50 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 18:34 [PATCH] arm64/io: Don't use WZR in writel AngeloGioacchino Del Regno
2019-02-09 18:34 ` AngeloGioacchino Del Regno
2019-02-09 18:34 ` AngeloGioacchino Del Regno
2019-02-11 10:57 ` Will Deacon
2019-02-11 10:57 ` Will Deacon
2019-02-11 11:52 ` Marc Zyngier
2019-02-11 11:52 ` Marc Zyngier
2019-02-11 14:29 ` AngeloGioacchino Del Regno
2019-02-11 14:29 ` AngeloGioacchino Del Regno
2019-02-11 14:59 ` Marc Zyngier
2019-02-11 14:59 ` Marc Zyngier
2019-02-11 16:15 ` AngeloGioacchino Del Regno
2019-02-11 16:15 ` AngeloGioacchino Del Regno
2019-02-11 16:37 ` Robin Murphy
2019-02-11 16:37 ` Robin Murphy
2019-02-23 18:12 ` Bjorn Andersson
2019-02-23 18:12 ` Bjorn Andersson
2019-02-23 18:37 ` Marc Zyngier
2019-02-23 18:37 ` Marc Zyngier
2019-02-23 18:37 ` Marc Zyngier
2019-02-24 3:53 ` Bjorn Andersson
2019-02-24 3:53 ` Bjorn Andersson
2019-03-12 12:36 ` Marc Gonzalez
2019-03-12 12:36 ` Marc Gonzalez
2019-03-18 16:04 ` Robin Murphy
2019-03-18 16:04 ` Robin Murphy
2019-03-18 17:00 ` Russell King - ARM Linux admin
2019-03-18 17:00 ` Russell King - ARM Linux admin
2019-03-18 17:11 ` Ard Biesheuvel
2019-03-18 17:11 ` Ard Biesheuvel
2019-03-18 17:19 ` Robin Murphy
2019-03-18 17:19 ` Robin Murphy
2019-03-18 17:24 ` Robin Murphy
2019-03-18 17:24 ` Robin Murphy
2019-03-19 11:45 ` Robin Murphy
2019-03-19 11:45 ` Robin Murphy
2019-03-18 17:30 ` Marc Gonzalez
2019-03-18 17:30 ` Marc Gonzalez
2019-03-18 17:59 ` Robin Murphy
2019-03-18 17:59 ` Robin Murphy
2019-05-02 16:05 ` Marc Gonzalez
2019-05-02 16:05 ` Marc Gonzalez
2019-05-02 16:05 ` Marc Gonzalez
2019-05-02 16:33 ` Robin Murphy
2019-05-02 16:33 ` Robin Murphy
2019-05-02 16:33 ` Robin Murphy
2019-05-02 16:50 ` Marc Gonzalez [this message]
2019-05-02 16:50 ` Marc Gonzalez
2019-05-02 16:50 ` Marc Gonzalez
2019-05-03 11:36 ` Marc Gonzalez
2019-05-03 11:36 ` Marc Gonzalez
2019-05-03 11:36 ` Marc Gonzalez
2019-05-03 12:48 ` Robin Murphy
2019-05-03 12:48 ` Robin Murphy
2019-05-03 13:07 ` Marc Gonzalez
2019-05-03 13:07 ` Marc Gonzalez
2019-05-03 13:07 ` Marc Gonzalez
2019-05-04 13:35 ` AngeloGioacchino Del Regno
2019-05-04 13:35 ` AngeloGioacchino Del Regno
2019-05-04 13:35 ` AngeloGioacchino Del Regno
2019-05-05 18:05 ` AngeloGioacchino Del Regno
2019-05-05 18:05 ` AngeloGioacchino Del Regno
2019-05-05 18:05 ` AngeloGioacchino Del Regno
2019-05-20 15:05 ` Marc Gonzalez
2019-05-20 15:05 ` Marc Gonzalez
2019-05-02 17:27 ` Marc Gonzalez
2019-05-02 17:27 ` Marc Gonzalez
2019-05-02 17:27 ` Marc Gonzalez
2019-05-03 0:38 ` Bjorn Andersson
2019-05-03 0:38 ` Bjorn Andersson
2019-05-03 0:38 ` Bjorn Andersson
-- strict thread matches above, loose matches on Subject: below --
2019-02-09 18:30 AngeloGioacchino Del Regno
2019-02-09 18:30 ` AngeloGioacchino Del Regno
2019-02-09 18:30 ` AngeloGioacchino Del Regno
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=5b83a4c2-1f0e-337f-a78d-f7d84fe01ab3@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=jhugo@codeaurora.org \
--cc=kholk11@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.com \
--cc=will.deacon@arm.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 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.