From: Geert Uytterhoeven <geert+renesas@glider.be> To: Mark Rutland <mark.rutland@arm.com>, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> Cc: linux-arm-kernel@lists.infradead.org, linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven <geert+renesas@glider.be> Subject: [PATCH 0/2] drivers: firmware: psci: Extract psci_is_available() helper Date: Wed, 11 Oct 2017 10:03:00 +0200 [thread overview] Message-ID: <1507708982-12336-1-git-send-email-geert+renesas@glider.be> (raw) Hi Mark, Lorenzo, PSCI support may be disabled at build time (by configuration) or at run-time (PSCI firmware not present). While CONFIG_ARM_PSCI_FW can be used to check for build time enablement, there is currently no simple way to check if PSCI is actually available and used. The first patch adds a helper function to check if PSCI is available. This is useful for e.g. drivers that are used on platforms with and without PSCI. Such drivers may need to take provisions for proper operation when PSCI is used, and/or to implement functionality that is usually provided by PSCI. The second patch makes the PSCI checker use the new helper. Thanks for your comments! Geert Uytterhoeven (2): drivers: firmware: psci: Add psci_is_available() drivers: psci: checker: Use psci_is_available() drivers/firmware/psci.c | 5 +++++ drivers/firmware/psci_checker.c | 2 +- include/linux/psci.h | 2 ++ 3 files changed, 8 insertions(+), 1 deletion(-) -- 2.7.4 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: geert+renesas@glider.be (Geert Uytterhoeven) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/2] drivers: firmware: psci: Extract psci_is_available() helper Date: Wed, 11 Oct 2017 10:03:00 +0200 [thread overview] Message-ID: <1507708982-12336-1-git-send-email-geert+renesas@glider.be> (raw) Hi Mark, Lorenzo, PSCI support may be disabled at build time (by configuration) or at run-time (PSCI firmware not present). While CONFIG_ARM_PSCI_FW can be used to check for build time enablement, there is currently no simple way to check if PSCI is actually available and used. The first patch adds a helper function to check if PSCI is available. This is useful for e.g. drivers that are used on platforms with and without PSCI. Such drivers may need to take provisions for proper operation when PSCI is used, and/or to implement functionality that is usually provided by PSCI. The second patch makes the PSCI checker use the new helper. Thanks for your comments! Geert Uytterhoeven (2): drivers: firmware: psci: Add psci_is_available() drivers: psci: checker: Use psci_is_available() drivers/firmware/psci.c | 5 +++++ drivers/firmware/psci_checker.c | 2 +- include/linux/psci.h | 2 ++ 3 files changed, 8 insertions(+), 1 deletion(-) -- 2.7.4 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
next reply other threads:[~2017-10-11 11:51 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-11 8:03 Geert Uytterhoeven [this message] 2017-10-11 8:03 ` [PATCH 0/2] drivers: firmware: psci: Extract psci_is_available() helper Geert Uytterhoeven 2017-10-11 8:03 ` [PATCH 1/2] drivers: firmware: psci: Add psci_is_available() Geert Uytterhoeven 2017-10-11 8:03 ` Geert Uytterhoeven 2017-10-12 2:58 ` Jisheng Zhang 2017-10-12 2:58 ` Jisheng Zhang 2017-10-12 6:58 ` Geert Uytterhoeven 2017-10-12 6:58 ` Geert Uytterhoeven 2017-10-12 6:58 ` Geert Uytterhoeven 2017-10-25 15:45 ` [1/2] " Lorenzo Pieralisi 2017-10-25 15:45 ` Lorenzo Pieralisi 2017-10-11 8:03 ` [PATCH 2/2] drivers: firmware: psci: checker: Use psci_is_available() Geert Uytterhoeven
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=1507708982-12336-1-git-send-email-geert+renesas@glider.be \ --to=geert+renesas@glider.be \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=mark.rutland@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: linkBe 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.