From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: juno: Add APB registers and LEDs using syscon
Date: Mon, 09 Mar 2015 17:19:28 +0000 [thread overview]
Message-ID: <54FDD620.1010703@arm.com> (raw)
In-Reply-To: <1425917877.2657.12.camel@linaro.org>
On 09/03/15 16:17, Jon Medhurst (Tixy) wrote:
> On Mon, 2015-03-09 at 10:31 +0000, Sudeep Holla wrote:
>>
>> On 27/02/15 14:06, Liviu Dudau wrote:
>>> On Fri, Feb 27, 2015 at 01:07:42PM +0000, Linus Walleij wrote:
>>>> On Wed, Feb 25, 2015 at 4:11 PM, Liviu Dudau <Liviu.Dudau@arm.com> wrote:
>>
>> [...]
>>
>>> I'm mostly on your side, Linus, I was just looking for more use cases. Like I've said,
>>> most of our customers seem to keep the case closed (or at least that is what they tell
>>> us :) ) so I'm looking for explanations on how you use the LEDs (visual debugging for
>>> big-LITTLE was how Lorenzo was using them on TC2 for example).
>>>
>>
>> Just to clarify:
>>
>> IIUC all VExpress platforms has these LEDs on the motherboard. The one
>> you are referring is on the TC2 core-tile which are completely
>> controlled by the firmware. The main advantage of that was to know if
>> the OSPM request is accepted by the firmware.
>>
>> But the LEDs being referred here are under OS control and gives only the
>> OS view of the state which is good enough but not exactly what we had on
>> TC2.
>
> Well, when a TC2 CoreTile is plugged into the Versatile Express
> motherboard you get those LEDs as well and can see what the OS thinks is
> the state of the CPU's. I've found this useful in the past for debugging
> problems caused by a mismatch between the OS's and firmware's view of
> the world.
>
I agree, I just wanted to clarify that the LEDs that were more useful
while debugging PM on TC2 were those on the coretile rather than the one
on the motherboard and that there are managed by firmware.
Regards,
Sudeep
prev parent reply other threads:[~2015-03-09 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 12:16 [PATCH 1/2] arm64: juno: Add APB registers and LEDs using syscon Linus Walleij
2015-02-25 13:55 ` Will Deacon
2015-02-25 14:47 ` Liviu Dudau
2015-02-25 15:00 ` Will Deacon
2015-02-25 15:11 ` Liviu Dudau
2015-02-27 13:07 ` Linus Walleij
2015-02-27 14:06 ` Liviu Dudau
2015-03-07 22:24 ` Linus Walleij
2015-03-09 10:12 ` Liviu Dudau
2015-03-09 10:31 ` Sudeep Holla
2015-03-09 16:17 ` Jon Medhurst (Tixy)
2015-03-09 17:19 ` Sudeep Holla [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=54FDD620.1010703@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 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).