From: Liviu.Dudau@arm.com (Liviu Dudau)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: juno: Add APB registers and LEDs using syscon
Date: Wed, 25 Feb 2015 14:47:56 +0000 [thread overview]
Message-ID: <20150225144756.GA905@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <20150225135512.GE12377@arm.com>
On Wed, Feb 25, 2015 at 01:55:12PM +0000, Will Deacon wrote:
> On Wed, Feb 25, 2015 at 12:16:29PM +0000, Linus Walleij wrote:
> > This defines the Juno "APB system registers" as a syscon device,
> > and all the LEDs controlled by the APB system registers right
> > below it using the syscon LEDs driver on top of syscon. Define
> > LED0 for heartbeat, LED1 for MMC0 activity and the following
> > four LEDs indicating CPU activity using the Linux-specific
> > DT bindings for triggers.
> >
> > This is the pattern and same drivers as used on the legacy
> > platform device trees for the ARM Integrators and the RealView
> > PB1176.
>
> Stupid question, but where are these LEDs located on the platform? I tried
> enabling this, but all it seemed to do was make hackbench slightly slower :)
http://infocenter.arm.com/help/topic/com.arm.doc.ddi0524c/deb1353593789871.html
Section 1.3, look at the left hand side, above the user push buttons.
Best regards,
Liviu
>
> Will
>
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
?\_(?)_/?
next prev parent reply other threads:[~2015-02-25 14:47 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 [this message]
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
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=20150225144756.GA905@e106497-lin.cambridge.arm.com \
--to=liviu.dudau@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).