From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-sh@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org,
Mike Turquette <mturquette@linaro.org>
Subject: Re: [PATCH 3/3] clk: shmobile: Add R8A7790 clocks support
Date: Fri, 08 Nov 2013 02:00:46 +0100 [thread overview]
Message-ID: <2305074.dSYTpfKiqG@avalon> (raw)
In-Reply-To: <87li0zrc3m.wl%kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
On Thursday 07 November 2013 16:06:29 Kuninori Morimoto wrote:
> Hi Laurent
>
> > Sure, if the hardware is very similar, it makes sense to share code. I've
> > had a quick look at the M2 documentation, and it seems to be indeed
> > mostly identical to H2. Only a couple of clocks are missing, and a new
> > GPU clock register is documented. As the GPU clock is mentioned in the H2
> > documentation as being programmable I would assume that the GPU clock
> > register exists and is identical in H2 but has been forgotten in the
> > documentation.
> >
> > We should probably extend clock-r8a7790.c with M2 support and rename it to
> > clock-rcar-gen2.c before pushing it to mainline. Would you like to submit
> > a patch ? :-)
>
> Thank yor for your agreement.
> I don't want to send "rename patch",
> please consider it in your v2 patch if possible :P
We also need to take into account that the two SoCs will have a different
number of clocks. I'm thus inclined to replace the index-based switch
statement by a similar construct that will match on the clock name instead. Do
you have any opinion on that ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-11-08 1:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 14:55 [PATCH 0/3] Renesas R8A7790 Common Clock Framework support Laurent Pinchart
2013-10-29 14:55 ` [PATCH 1/3] clk: shmobile: Add DIV6 clock support Laurent Pinchart
2013-10-29 23:33 ` Kumar Gala
2013-10-29 23:54 ` Laurent Pinchart
2013-10-29 23:56 ` Kumar Gala
2013-10-29 14:55 ` [PATCH 2/3] clk: shmobile: Add MSTP " Laurent Pinchart
2013-10-29 23:36 ` Kumar Gala
2013-10-30 0:06 ` Laurent Pinchart
2013-10-30 0:19 ` Kumar Gala
2013-10-31 15:15 ` Laurent Pinchart
2013-11-06 2:09 ` Simon Horman
2013-11-06 12:22 ` Laurent Pinchart
2013-11-06 8:33 ` Magnus Damm
2013-11-06 12:13 ` Laurent Pinchart
2013-10-29 14:55 ` [PATCH 3/3] clk: shmobile: Add R8A7790 clocks support Laurent Pinchart
2013-10-29 23:56 ` Kumar Gala
2013-11-05 7:56 ` Magnus Damm
2013-11-05 23:47 ` Laurent Pinchart
2013-11-06 8:19 ` Magnus Damm
2013-11-06 12:45 ` Laurent Pinchart
2013-11-05 8:52 ` Kuninori Morimoto
2013-11-05 23:57 ` Laurent Pinchart
2013-11-06 0:54 ` Kuninori Morimoto
2013-11-06 1:00 ` Laurent Pinchart
2013-11-06 2:31 ` Kuninori Morimoto
[not found] ` <8738na1csg.wl%kuninori.morimoto.gx-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2013-11-06 12:41 ` Laurent Pinchart
2013-11-07 3:22 ` Kuninori Morimoto
2013-11-07 7:20 ` Kuninori Morimoto
2013-11-07 12:15 ` Laurent Pinchart
2013-11-08 0:06 ` Kuninori Morimoto
2013-11-08 1:00 ` Laurent Pinchart [this message]
2013-11-08 6:02 ` Kuninori Morimoto
2013-11-06 7:18 ` Simon Horman
2013-11-06 12:56 ` Laurent Pinchart
2013-11-08 6:34 ` Simon Horman
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=2305074.dSYTpfKiqG@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=mturquette@linaro.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).