From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Magnus Damm <magnus.damm@gmail.com>, linux-clk@vger.kernel.org
Cc: kuninori.morimoto.gx@renesas.com, linux-sh@vger.kernel.org,
mturquette@baylibre.com, gaku.inami.xw@bp.renesas.com,
sboyd@codeaurora.org, horms@verge.net.au, geert@linux-m68k.org,
laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH v6 03/05] clk: shmobile: Make MSTP clock-output-names optional
Date: Wed, 02 Sep 2015 11:23:46 +0000 [thread overview]
Message-ID: <55E6DC42.6080201@cogentembedded.com> (raw)
In-Reply-To: <20150902071728.10870.32730.sendpatchset@little-apple>
Hello.
On 9/2/2015 10:17 AM, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> This patch updates the MSTP driver to make the "clock-output-names"
> DT property optional instead of mandatory. In case the DT property
> is omitted then the function clk_register_clkdev() is skipped.
>
> The default for new SoCs is to not use "clock-output-names".
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
>
> Changes since V5:
> - Simplified code using const char *allocated_name - thanks Geert!
>
> Changes since V4:
> - None
>
> Changes since V3:
> - Added support for multiple MSTP bits. =)
>
> drivers/clk/shmobile/clk-mstp.c | 24 +++++++++++++++---------
> 1 file changed, 15 insertions(+), 9 deletions(-)
>
> --- 0001/drivers/clk/shmobile/clk-mstp.c
> +++ work/drivers/clk/shmobile/clk-mstp.c 2015-09-02 11:52:02.182366518 +0900
> @@ -193,26 +193,26 @@ static void __init cpg_mstp_clocks_init(
[...]
> parent_name = of_clk_get_parent_name(np, i);
> ret = of_property_read_u32_index(np, idxname, i, &clkidx);
> if (parent_name = NULL || ret < 0)
> break;
>
> if (clkidx >= MSTP_MAX_CLOCKS) {
> - pr_err("%s: invalid clock %s %s index %u)\n",
> - __func__, np->name, name, clkidx);
> + pr_err("%s: invalid clock %s index %u)\n",
> + __func__, np->name, clkidx);
> continue;
> }
>
> + if (of_property_read_string_index(np, "clock-output-names",
> + i, &name) < 0)
> + allocated_name = name = kasprintf(GFP_KERNEL, "%s.%u",
> + np->name, clkidx);
There's too many spaces on this line, it's a bit over-indented.
[...]
MBR, Sergei
next prev parent reply other threads:[~2015-09-02 11:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 7:16 [PATCH v6 00/05] Renesas R-Car Gen3 CPG support V6 Magnus Damm
2015-09-02 7:17 ` [PATCH v6 01/05] clk: shmobile: Rework CONFIG_ARCH_SHMOBILE_MULTI Magnus Damm
2015-09-02 11:15 ` Sergei Shtylyov
2015-09-03 7:32 ` Magnus Damm
2015-09-02 7:17 ` [PATCH v6 02/05] clk: shmobile: Add r8a7795 SoC to MSTP bindings Magnus Damm
2015-09-02 7:17 ` [PATCH v6 03/05] clk: shmobile: Make MSTP clock-output-names optional Magnus Damm
2015-09-02 11:23 ` Sergei Shtylyov [this message]
2015-09-02 11:26 ` Sergei Shtylyov
2015-09-02 7:17 ` [PATCH v6 04/05] clk: shmobile: Add Renesas R-Car Gen3 CPG support Magnus Damm
2015-09-02 7:17 ` [PATCH v6 05/05] clk: shmobile: rcar-gen3: Add CPG/MSTP Clock Domain support Magnus Damm
2015-09-02 9:28 ` [PATCH v6 00/05] Renesas R-Car Gen3 CPG support V6 Geert Uytterhoeven
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=55E6DC42.6080201@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=gaku.inami.xw@bp.renesas.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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).