From: Kevin Hickey <khickey@netlogicmicro.com>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>,
Manuel Lauss <manuel.lauss@gmail.com>
Subject: Re: [RFC PATCH 1/3] MIPS: Alchemy: extended DB1200 board support.
Date: Tue, 03 Nov 2009 09:47:03 -0600 [thread overview]
Message-ID: <1257263223.29642.12.camel@localhost> (raw)
In-Reply-To: <f861ec6f0911030744j13fa9487p857c49a68d43adfe@mail.gmail.com>
On Tue, 2009-11-03 at 16:44 +0100, Manuel Lauss wrote:
> On Tue, Nov 3, 2009 at 4:41 PM, Kevin Hickey <khickey@netlogicmicro.com> wrote:
> > On Mon, 2009-11-02 at 21:21 +0100, Manuel Lauss wrote:
> >> Create own directory for DB1200 code and update it with new features.
> >>
> >> - SPI support:
> >> - tmp121 temperature sensor
> >> - SPI flash on DB1200
> >> - I2C support
> >> - NE1619 sensor
> >> - AT24 eeprom
> >> - I2C/SPI can be selected at boot time via switch S6.8
> >> - Carddetect IRQs for SD cards.
> >> - gen_nand based NAND support.
> >> - hexleds count sleep/wake transitions.
> >>
> >> Signed-off-by: Manuel Lauss <manuel.lauss@gmail.com>
> >> ---
> >
> > The code in this patch all looks good to me. I don't understand how
> > much value is added by using the hex LEDs for counting sleep/wake
> > transitions. In our internal builds, we use the hex LEDs for displaying
> > the last interrupt serviced (useful on hangs/crashes and for getting a
> > general sense of what the hardware is working on), the dots blink on
> > timer ticks (often every 100 or 1000 depending on the clock) and the
> > Idle state is shown on LED0. I don't really have any strong attachment
> > to those usages, but they've served us well.
>
> I admit it has limited value.. I initially used it to find out how many wakeups
> per second are happening with and without high-speed usb devices attached.
> I left it in because I couldn't come up with any other uses. Please feel free
> to change it any time.
Fair enough. If I get some time down the line I'll look into that. In
the meantime this patch has a lot of value so it should probably just
stay as it is.
Again, if it's not too late:
Acked-by: Kevin Hickey <khickey@netlogicmicro.com>
=Kevin
prev parent reply other threads:[~2009-11-03 15:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 20:21 [RFC PATCH 1/3] MIPS: Alchemy: extended DB1200 board support Manuel Lauss
2009-11-02 20:21 ` [RFC PATCH 2/3] MIPS: Alchemy: DB1200 AC97+I2S audio support Manuel Lauss
2009-11-02 20:21 ` [PATCH 3/3] MIPS: Alchemy: db1200 defconfig update Manuel Lauss
2009-11-03 10:43 ` [RFC PATCH 2/3] MIPS: Alchemy: DB1200 AC97+I2S audio support Mark Brown
2009-11-03 10:43 ` Mark Brown
2009-11-03 11:00 ` Manuel Lauss
2009-11-03 11:00 ` Manuel Lauss
2009-11-03 11:13 ` Mark Brown
2009-11-03 11:13 ` [alsa-devel] " Mark Brown
2009-11-03 15:30 ` Ralf Baechle
2009-11-03 15:30 ` Ralf Baechle
2009-11-03 15:30 ` Manuel Lauss
2009-11-03 15:30 ` Manuel Lauss
2009-11-03 15:35 ` Ralf Baechle
2009-11-03 15:35 ` Ralf Baechle
2009-11-03 15:34 ` Manuel Lauss
2009-11-03 15:34 ` Manuel Lauss
2009-11-03 15:28 ` [RFC PATCH 1/3] MIPS: Alchemy: extended DB1200 board support Ralf Baechle
2009-11-03 15:41 ` Kevin Hickey
2009-11-03 15:44 ` Manuel Lauss
2009-11-03 15:47 ` Kevin Hickey [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=1257263223.29642.12.camel@localhost \
--to=khickey@netlogicmicro.com \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.com \
--cc=manuel.lauss@googlemail.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: 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.