From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drivers: psci: Allow PSCI node to be disabled
Date: Thu, 20 Oct 2016 13:58:35 +0100 [thread overview]
Message-ID: <20161020125835.GB8731@red-moon> (raw)
In-Reply-To: <20161020123907.GF10234@leverpostej>
On Thu, Oct 20, 2016 at 01:39:07PM +0100, Mark Rutland wrote:
> On Mon, Oct 17, 2016 at 12:46:53PM +0200, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > Allow disabling PSCI support (mostly for testing purposes) by setting
> > the status property to "disabled". This makes the node behave in much
> > the same way as proper device nodes.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
>
> This looks sensible to me; FWIW:
>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
>
> Lorenzo, do we need to batch this up with other PSCI patches, or should
> this go direct to arm-soc?
I am aiming at getting the PSCI checker merged too so that we can send
both patches (and others that may turn up) in one go to arm-soc, I will
handle it.
Thanks !
Lorenzo
> Thanks,
> Mark.
>
> > ---
> > drivers/firmware/psci.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/firmware/psci.c b/drivers/firmware/psci.c
> > index 8263429e21b8..6c60a5087caf 100644
> > --- a/drivers/firmware/psci.c
> > +++ b/drivers/firmware/psci.c
> > @@ -630,7 +630,7 @@ int __init psci_dt_init(void)
> >
> > np = of_find_matching_node_and_match(NULL, psci_of_match, &matched_np);
> >
> > - if (!np)
> > + if (!np || !of_device_is_available(np))
> > return -ENODEV;
> >
> > init_fn = (psci_initcall_t)matched_np->data;
> > --
> > 2.10.0
> >
>
next prev parent reply other threads:[~2016-10-20 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 10:46 [PATCH] drivers: psci: Allow PSCI node to be disabled Thierry Reding
2016-10-20 12:39 ` Mark Rutland
2016-10-20 12:58 ` Lorenzo Pieralisi [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-07 13:56 Thierry Reding
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=20161020125835.GB8731@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.