[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <877ekhnwrg.fsf@vajain21.in.ibm.com>
Date: Thu, 23 Aug 2018 17:02:51 +0530
From: Vaibhav Jain <vaibhav@...ux.ibm.com>
To: Nicholas Piggin <npiggin@...il.com>,
Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>
Cc: "Gautham R . Shenoy" <ego@...ux.vnet.ibm.com>,
Michael Neuling <mikey@...ling.org>,
Stewart Smith <stewart@...ux.ibm.com>,
Linux-MIPS <linux-mips@...ux-mips.org>,
linux-arch <linux-arch@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>, James Hogan <jhogan@...nel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ralf Baechle <ralf@...ux-mips.org>
Subject: Re: [Skiboot] [PATCH] opal/hmi: Wakeup the cpu before reading core_fir
Thanks for reviewing this patch Nick
Nicholas Piggin <npiggin@...il.com> writes:
>
> Would it be feasible to enumerate the ranges of scoms that require
> special wakeup and check for those in xscom_read/write, and warn if
> spwkup was not set?
>
I think that might be racy (Vaidy please correct if I am wrong) as a
core can change its state when we read its sleep state and when we do
the actual xscom to read the core_fir.
--
Vaibhav Jain <vaibhav@...ux.vnet.ibm.com>
Linux Technology Center, IBM India Pvt. Ltd.
Powered by blists - more mailing lists