From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/5] davinci: add clocks command
Date: Mon, 17 Oct 2011 12:20:45 +0200 [thread overview]
Message-ID: <4E9C017D.1080407@gmail.com> (raw)
In-Reply-To: <1318838504-9766-4-git-send-email-manjunath.hadli@ti.com>
Dear Manjunath Hadli,
Am 17.10.2011 10:01, schrieb manjunath.hadli at ti.com:
> From: Manjunath Hadli <manjunath.hadli@ti.com>
>
> add 'clocks' command to print various clock frequency info found
> in SOC such as ARM core frequency, DSP core frequency and DDR
> frequency.
Isn't that the job of command 'bdi'? Why introduce a new, proprietary
command instead of changing still available ones?
Well maybe is a 'clocks' command really useful, but then it should be
provided to all with a clear interface and not hidden in some
architecture specific directory.
Best regards
Andreas Bie?mann
next prev parent reply other threads:[~2011-10-17 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 8:01 [U-Boot] [PATCH v2 0/5] addition of clocks command for davinci manjunath.hadli at ti.com
2011-10-17 8:01 ` [U-Boot] [PATCH v2 1/5] davinci : move clock related functions to new file manjunath.hadli at ti.com
2011-10-17 8:01 ` [U-Boot] [PATCH v2 2/5] davinci: remove macro CONFIG_DISPLAY_CPUINFO manjunath.hadli at ti.com
2011-10-17 8:01 ` [U-Boot] [PATCH v2 3/5] davinci: add clocks command manjunath.hadli at ti.com
2011-10-17 10:20 ` Andreas Bießmann [this message]
2011-10-17 10:53 ` Wolfgang Denk
2011-10-17 8:01 ` [U-Boot] [PATCH v2 4/5] dm365: add support to print cpu clock information manjunath.hadli at ti.com
2011-10-17 8:01 ` [U-Boot] [PATCH v2 5/5] da8xx: print ARM and DDR frequency from u-boot manjunath.hadli at ti.com
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=4E9C017D.1080407@gmail.com \
--to=andreas.devel@googlemail.com \
--cc=u-boot@lists.denx.de \
/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.