From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 1/2] common: Add new clk command
Date: Thu, 30 Jan 2014 10:29:13 +0100 [thread overview]
Message-ID: <52EA1B69.8060503@denx.de> (raw)
In-Reply-To: <52EA0180.80409@monstr.eu>
Hi Michal,
On 30/01/2014 08:38, Michal Simek wrote:
> On 01/23/2014 08:53 AM, Michal Simek wrote:
>> On 01/22/2014 08:44 PM, Gerhard Sittig wrote:
>>> On Wed, Jan 22, 2014 at 12:02 +0100, Michal Simek wrote:
>>>>
>>>> --- /dev/null +++ b/common/cmd_clk.c @@ -0,0 +1,51 @@ +/* +
>>>> * Copyright (C) 2013 Xilinx, Inc. + * + *
>>>> SPDX-License-Identifier: GPL-2.0+ + */ +#include <common.h>
>>>> +#include <command.h> +#include <clk.h> + +int __weak
>>>> soc_clk_dump(void) +{ + puts("Not implemented\n"); + return
>>>> 1; +} + +static int do_clk_dump(cmd_tbl_t *cmdtp, int flag,
>>>> int argc, + char *const argv[]) +{ + return
>>>> soc_clk_dump(); +}
>>>
>>> Is there a specific reason to not pass on the remaining (not
>>> yet consumed) command line arguments? Future implementations
>>> may want to take a clock item's name, or a clock group's name,
>>> or options related to the format or verbosity of the dump, et
>>> al.
>>
>> Only one reason is that I don't need it for my zynq
>> implementation. If this is necessary there is no problem to pass
>> them because it is internal API. Also I prefer to pass just
>> arguments which I need.
>>
>> I have looked at i.MXes cases and they do in general what my
>> zynq implementation. They can just include clk.h and change
>> do_mx6_showclocks to soc_clk_dump.
>
Agree.
> Stefano: Can you give me your ACK?
>
Sure, go on. !
Regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2014-01-30 9:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 11:02 [U-Boot] [RFC PATCH 1/2] common: Add new clk command Michal Simek
2014-01-22 11:02 ` [U-Boot] [RFC PATCH 2/2] zynq: Implement dump clock command Michal Simek
2014-01-22 12:46 ` [U-Boot] [RFC PATCH 1/2] common: Add new clk command Stefano Babic
2014-01-22 13:07 ` Michal Simek
2014-01-22 19:44 ` Gerhard Sittig
2014-01-23 7:53 ` Michal Simek
2014-01-30 7:38 ` Michal Simek
2014-01-30 9:29 ` Stefano Babic [this message]
2015-12-22 4:21 ` Simon Glass
2015-12-29 8:33 ` Michal Simek
2015-12-29 12:23 ` Simon Glass
2015-12-29 14:23 ` Wolfgang Denk
2016-01-05 0:57 ` Simon Glass
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=52EA1B69.8060503@denx.de \
--to=sbabic@denx.de \
--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.