All of lore.kernel.org
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/8] ARM64: dts: Prepare configs for Amlogic Meson GXBaby
Date: Tue, 1 Mar 2016 16:19:37 +0000	[thread overview]
Message-ID: <56D5C119.8070609@arm.com> (raw)
In-Reply-To: <56D5B2D5.9010405@suse.de>



On 01/03/16 15:18, Andreas F?rber wrote:
> Am 01.03.2016 um 15:43 schrieb Sudeep Holla:
>> On 29/02/16 23:44, Andreas F?rber wrote:
>>> +    psci {
>>> +        compatible = "arm,psci";
>>
>> Any particular reason why PSCI v0.2 or above is not supported on this
>> platform. PSCI v0.1 is very old now and I assume this platform is
>> relatively new.
>
> I am not affiliated with Amlogic or Tronsmart, so I cannot answer why.
>

OK

>>> +        method = "smc";
>>> +        cpu_suspend = <0xc4000001>;
>>> +        cpu_off = <0x84000002>;
>>> +        cpu_on = <0xc4000003>;
>>> +        migrate = <0xc4000005>;
>>
>> Atleast the functions ids look like v0.2 or above. So check if it's
>> actually v0.2 or above
>
> If you let me know how! Just change the compatible string to -0.2 and
> wait for some big boom or watch out for any misbehavior in particular?

Not exactly. Just having -0.2 in compatible will issue PSCI_VERSION
which *should be* available in v0.2 and above. If you get error there,
then we can *assume* it's PSCI v0.1. Hopefully it be sanely return
error if that's not implemented.

Note that we can only assume, as it might be v0.2 but missed to
implement PSCI_VERSION which is mandatory though.

> Are there any memory locations to check the version or something visible
> in U-Boot source code indicating it?
>

Ah so, PSCI is implemented in U-Boot on this platform ? If so, and if
the source is available it should not be that hard to figure that out.

-- 
Regards,
Sudeep

WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>
To: "Andreas Färber" <afaerber-l3A5Bk7waGM@public.gmane.org>,
	linux-meson-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>,
	Carlo Caione <carlo-KA+7E9HrN00dnm+yROfE0A@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Matthias Brugger <mbrugger-IBi9RG/b67k@public.gmane.org>,
	Nicolas Saenz
	<nicolassaenzj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Ian Campbell
	<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
	Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
	Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
	devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 3/8] ARM64: dts: Prepare configs for Amlogic Meson GXBaby
Date: Tue, 1 Mar 2016 16:19:37 +0000	[thread overview]
Message-ID: <56D5C119.8070609@arm.com> (raw)
In-Reply-To: <56D5B2D5.9010405-l3A5Bk7waGM@public.gmane.org>



On 01/03/16 15:18, Andreas Färber wrote:
> Am 01.03.2016 um 15:43 schrieb Sudeep Holla:
>> On 29/02/16 23:44, Andreas Färber wrote:
>>> +    psci {
>>> +        compatible = "arm,psci";
>>
>> Any particular reason why PSCI v0.2 or above is not supported on this
>> platform. PSCI v0.1 is very old now and I assume this platform is
>> relatively new.
>
> I am not affiliated with Amlogic or Tronsmart, so I cannot answer why.
>

OK

>>> +        method = "smc";
>>> +        cpu_suspend = <0xc4000001>;
>>> +        cpu_off = <0x84000002>;
>>> +        cpu_on = <0xc4000003>;
>>> +        migrate = <0xc4000005>;
>>
>> Atleast the functions ids look like v0.2 or above. So check if it's
>> actually v0.2 or above
>
> If you let me know how! Just change the compatible string to -0.2 and
> wait for some big boom or watch out for any misbehavior in particular?

Not exactly. Just having -0.2 in compatible will issue PSCI_VERSION
which *should be* available in v0.2 and above. If you get error there,
then we can *assume* it's PSCI v0.1. Hopefully it be sanely return
error if that's not implemented.

Note that we can only assume, as it might be v0.2 but missed to
implement PSCI_VERSION which is mandatory though.

> Are there any memory locations to check the version or something visible
> in U-Boot source code indicating it?
>

Ah so, PSCI is implemented in U-Boot on this platform ? If so, and if
the source is available it should not be that hard to figure that out.

-- 
Regards,
Sudeep
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com>
To: "Andreas Färber" <afaerber@suse.de>, linux-meson@googlegroups.com
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Carlo Caione <carlo@caione.org>,
	linux-arm-kernel@lists.infradead.org,
	Matthias Brugger <mbrugger@suse.com>,
	Nicolas Saenz <nicolassaenzj@gmail.com>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	devicetree <devicetree@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/8] ARM64: dts: Prepare configs for Amlogic Meson GXBaby
Date: Tue, 1 Mar 2016 16:19:37 +0000	[thread overview]
Message-ID: <56D5C119.8070609@arm.com> (raw)
In-Reply-To: <56D5B2D5.9010405@suse.de>



On 01/03/16 15:18, Andreas Färber wrote:
> Am 01.03.2016 um 15:43 schrieb Sudeep Holla:
>> On 29/02/16 23:44, Andreas Färber wrote:
>>> +    psci {
>>> +        compatible = "arm,psci";
>>
>> Any particular reason why PSCI v0.2 or above is not supported on this
>> platform. PSCI v0.1 is very old now and I assume this platform is
>> relatively new.
>
> I am not affiliated with Amlogic or Tronsmart, so I cannot answer why.
>

OK

>>> +        method = "smc";
>>> +        cpu_suspend = <0xc4000001>;
>>> +        cpu_off = <0x84000002>;
>>> +        cpu_on = <0xc4000003>;
>>> +        migrate = <0xc4000005>;
>>
>> Atleast the functions ids look like v0.2 or above. So check if it's
>> actually v0.2 or above
>
> If you let me know how! Just change the compatible string to -0.2 and
> wait for some big boom or watch out for any misbehavior in particular?

Not exactly. Just having -0.2 in compatible will issue PSCI_VERSION
which *should be* available in v0.2 and above. If you get error there,
then we can *assume* it's PSCI v0.1. Hopefully it be sanely return
error if that's not implemented.

Note that we can only assume, as it might be v0.2 but missed to
implement PSCI_VERSION which is mandatory though.

> Are there any memory locations to check the version or something visible
> in U-Boot source code indicating it?
>

Ah so, PSCI is implemented in U-Boot on this platform ? If so, and if
the source is available it should not be that hard to figure that out.

-- 
Regards,
Sudeep

  reply	other threads:[~2016-03-01 16:19 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 23:44 [PATCH 0/8] ARM64: meson: GXBaby (S905) and Vega S95 enablement Andreas Färber
2016-02-29 23:44 ` Andreas Färber
2016-02-29 23:44 ` [PATCH 1/8] ARM64: Enable Amlogic Meson GXBaby platform Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-03-01 14:43   ` Sudeep Holla
2016-03-01 14:43     ` Sudeep Holla
2016-03-01 15:26     ` Andreas Färber
2016-03-01 15:26       ` Andreas Färber
2016-03-01 16:07       ` Sudeep Holla
2016-03-01 16:07         ` Sudeep Holla
2016-02-29 23:44 ` [PATCH 2/8] Documentation: devicetree: amlogic: Document Meson GXBaby Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-02-29 23:44 ` [PATCH 3/8] ARM64: dts: Prepare configs for Amlogic " Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-03-01 14:43   ` Sudeep Holla
2016-03-01 14:43     ` Sudeep Holla
2016-03-01 14:43     ` Sudeep Holla
2016-03-01 15:18     ` Andreas Färber
2016-03-01 15:18       ` Andreas Färber
2016-03-01 15:18       ` Andreas Färber
2016-03-01 16:19       ` Sudeep Holla [this message]
2016-03-01 16:19         ` Sudeep Holla
2016-03-01 16:19         ` Sudeep Holla
2016-02-29 23:44 ` [PATCH 4/8] Documentation: devicetree: Document Tronsmart vendor prefix Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-03-01 11:37   ` Matthias Brugger
2016-03-01 11:37     ` Matthias Brugger
2016-03-01 11:37     ` Matthias Brugger
2016-03-01 11:53     ` Andreas Färber
2016-03-01 11:53       ` Andreas Färber
2016-03-01 11:53       ` Andreas Färber
2016-03-01 13:29       ` Matthias Brugger
2016-03-01 13:29         ` Matthias Brugger
2016-03-01 13:29         ` Matthias Brugger
2016-03-01 19:23       ` Beniamino Galvani
2016-03-01 19:23         ` Beniamino Galvani
2016-03-01 19:23         ` Beniamino Galvani
2016-03-03 23:57   ` Rob Herring
2016-03-03 23:57     ` Rob Herring
2016-02-29 23:44 ` [PATCH 5/8] Documentation: devicetree: amlogic: Document Tronsmart Vega S95 boards Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-02-29 23:44 ` [PATCH 6/8] ARM64: dts: amlogic: Add Tronsmart Vega S95 configs Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-02-29 23:55   ` Andreas Färber
2016-02-29 23:55     ` Andreas Färber
2016-02-29 23:55     ` Andreas Färber
2016-02-29 23:44 ` [PATCH 7/8] ARM64: dts: amlogic: Extend GXBaby GIC node Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-03-01 11:01   ` Andre Przywara
2016-03-01 11:01     ` Andre Przywara
2016-03-01 11:01     ` Andre Przywara
2016-03-01 11:18     ` Andreas Färber
2016-03-01 11:18       ` Andreas Färber
2016-03-01 11:18       ` Andreas Färber
2016-03-01 11:42       ` Matthias Brugger
2016-03-01 11:42         ` Matthias Brugger
2016-03-01 11:42         ` Matthias Brugger
2016-03-01 12:43       ` Andre Przywara
2016-03-01 12:43         ` Andre Przywara
2016-03-01 12:43         ` Andre Przywara
2016-03-01 12:53         ` Carlo Caione
2016-03-01 12:53           ` Carlo Caione
2016-03-01 12:53           ` Carlo Caione
2016-03-01 14:16           ` Andre Przywara
2016-03-01 14:16             ` Andre Przywara
2016-03-01 14:16             ` Andre Przywara
2016-03-01 22:46         ` Andreas Färber
2016-03-01 22:46           ` Andreas Färber
2016-03-01 22:58           ` André Przywara
2016-03-01 22:58             ` André Przywara
2016-03-01 22:58             ` André Przywara
2016-03-01 23:31         ` Andreas Färber
2016-03-01 23:31           ` Andreas Färber
2016-03-01 23:31           ` Andreas Färber
2016-03-02  0:03           ` André Przywara
2016-03-02  0:03             ` André Przywara
2016-03-02  0:07             ` Andreas Färber
2016-03-02  0:07               ` Andreas Färber
2016-02-29 23:44 ` [PATCH 8/8] ARM64: dts: amlogic: Add arch timer node for Meson GXBaby Andreas Färber
2016-02-29 23:44   ` Andreas Färber
2016-02-29 23:44   ` Andreas Färber

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=56D5C119.8070609@arm.com \
    --to=sudeep.holla@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.