From: Oleksandr <olekstysh@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Julien Grall <julien.grall@arm.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Subject: Re: [RFC PATCH] ARM: mach-shmobile: Parse DT to get ARCH timer memory region
Date: Tue, 14 May 2019 16:58:48 +0300 [thread overview]
Message-ID: <3e786103-69a4-2867-fc04-ccb4512bf221@gmail.com> (raw)
In-Reply-To: <CAMuHMdWkEU7x_Lzk6NUCxEdZRx_xTBFzkETwShZ322aYL5=bLg@mail.gmail.com>
On 14.05.19 10:16, Geert Uytterhoeven wrote:
> Hi Oleksandr,
Hi Geert
>
> On Mon, May 13, 2019 at 6:00 PM Oleksandr <olekstysh@gmail.com> wrote:
>> On 13.05.19 18:13, Geert Uytterhoeven wrote:
>>>> So, if the DT bindings for the counter module is not an option (if I
>>>> correctly understood a discussion pointed by Geert in another letter),
>>>> we should probably prevent all timer code here from being executed if
>>>> PSCI is in use.
>>>> What I mean is to return to [2], but with the modification to use
>>>> psci_smp_available() helper as an indicator of PSCI usage.
>>>>
>>>> Julien, Geert, what do you think?
>>> Yes, that sounds good to me.
>>>
>>> Note that psci_smp_available() seems to return false if CONFIG_SMP=n,
>>> so checking for that is not sufficient to avoid crashes when running a
>>> uniprocessor kernel on a PSCI-enabled system.
>> Indeed, you are right.
>>
>>
>> Nothing than just check for psci_ops.cpu_on == NULL directly comes to
>> mind...
>>
>> Have already checked with CONFIG_SMP=n, it works.
>>
>> Sounds ok?
> Fine for me, thanks!
Great, I will send new version.
>
> Gr{oetje,eeting}s,
>
> Geert
>
--
Regards,
Oleksandr Tyshchenko
prev parent reply other threads:[~2019-05-14 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 16:22 [RFC PATCH] ARM: mach-shmobile: Parse DT to get ARCH timer memory region Oleksandr Tyshchenko
2019-05-13 9:19 ` Julien Grall
2019-05-13 9:56 ` Geert Uytterhoeven
2019-05-13 14:06 ` Oleksandr
2019-05-13 15:13 ` Geert Uytterhoeven
2019-05-13 16:00 ` Oleksandr
2019-05-14 7:16 ` Geert Uytterhoeven
2019-05-14 13:58 ` Oleksandr [this message]
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=3e786103-69a4-2867-fc04-ccb4512bf221@gmail.com \
--to=olekstysh@gmail.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=julien.grall@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=oleksandr_tyshchenko@epam.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).