From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
viresh kumar <viresh.kumar@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
David Brown <david.brown@linaro.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Viresh Kumar <vireshk@kernel.org>, Xu Wei <xuwei5@hisilicon.com>,
ext Tony Lindgren <tony@atomide.com>,
Chen-Yu Tsai <wens@csie.org>, Kukjin Kim <kgene@kernel.org>,
Andy Gross <andy.gross@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
linux-arm-msm@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Barry Song <baohua@kernel.org>,
Frank Rowand <frank.rowand@am.sony.com>,
Patrice CHOTARD <patrice.chotard@st.com>,
shiraz hashim <shiraz.linux.kernel@gmail.com>,
Andreas
Subject: Re: [PATCH 1/3] arm: Convert arm boot_lock to raw
Date: Thu, 13 Dec 2018 11:48:42 +0000 [thread overview]
Message-ID: <20181213114842.GJ9507@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20181211212930.kcap5kx6bff6bpuu@linutronix.de>
On Tue, Dec 11, 2018 at 10:29:30PM +0100, Sebastian Andrzej Siewior wrote:
> On 2018-12-11 19:19:32 [+0100], Linus Walleij wrote:
> > Can you please send one patch per mach-* plat-*?
> >
> > I can apply the plat-versatile patch and send upstream.
>
> I just resent the versatile hunk. Should I really split up and resend
> the other platforms? Russell was not very amused about it.
Just the Versatile bit, and no I don't see any point in fixing the
other SoCs - it's an incentive for them to fix up their code.
However, given that hardly any have responded, pointing out this
problem in email clearly hasn't worked by the resounding silence
from SoC maintainers.
Removing boot_lock from those platforms who just cargo-culted the
boot_lock including comments without the pen_release stuff is easy,
all the lock is doing there is providing a bit of unnecessary
synchronisation between the requesting CPU and the booting CPU.
Only a couple of SoCs fall into this case - OMAP4 and qcom.
The rest aren't something that could just be ripped out without
the involvement of the SoC maintainer to test the changes - so
I'm of the opinion that we should just send SoC maintainers
patches that remove the pen_release and boot_lock crap. If they
blindly accept the patches, so be it.
I'm preparing a series to attack some of this.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2018-12-13 11:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181207102749.15205-1-bigeasy@linutronix.de>
2018-12-07 10:27 ` [PATCH 1/3] arm: Convert arm boot_lock to raw Sebastian Andrzej Siewior
2018-12-07 12:49 ` Linus Walleij
2018-12-07 13:00 ` Russell King - ARM Linux
2018-12-08 23:15 ` Linus Walleij
2018-12-09 0:41 ` Russell King - ARM Linux
2018-12-10 14:37 ` Sebastian Andrzej Siewior
2018-12-11 18:19 ` Linus Walleij
2018-12-11 21:23 ` [PATCH 1/3 v2] arm: versatile: Convert " Sebastian Andrzej Siewior
2018-12-11 21:29 ` [PATCH 1/3] arm: Convert arm " Sebastian Andrzej Siewior
2018-12-13 11:48 ` Russell King - ARM Linux [this message]
2018-12-13 12:42 ` Sebastian Andrzej Siewior
2018-12-12 11:15 ` Russell King - ARM Linux
[not found] <20180711110037.12928-1-bigeasy@linutronix.de>
2018-07-11 11:00 ` Sebastian Andrzej Siewior
2018-07-11 15:29 ` Andreas Färber
2018-07-16 4:20 ` Viresh Kumar
2018-07-16 7:42 ` Patrice CHOTARD
2018-07-16 15:30 ` Wei Xu
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=20181213114842.GJ9507@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=baohua@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=david.brown@linaro.org \
--cc=frank.rowand@am.sony.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=maxime.ripard@bootlin.com \
--cc=patrice.chotard@st.com \
--cc=shiraz.linux.kernel@gmail.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.org \
--cc=wens@csie.org \
--cc=xuwei5@hisilicon.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;
as well as URLs for NNTP newsgroup(s).