From: Dirk Behme <dirk.behme@de.bosch.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: clk: renesas: rcar-gen3: Status of Z* clocks?
Date: Tue, 29 Aug 2017 12:36:50 +0200 [thread overview]
Message-ID: <6cad207c-8f9e-3ed9-36e7-16963a6a3892@de.bosch.com> (raw)
In-Reply-To: <CAMuHMdXzuUzGnUkMfMdMcV5fCcsLn5uP4XQUkh9tfzAsfo0_ww@mail.gmail.com>
On 29.08.2017 11:44, Geert Uytterhoeven wrote:
> Hi Dirk,
>
> On Tue, Aug 29, 2017 at 11:15 AM, Dirk Behme <dirk.behme@de.bosch.com> wrote:
>> But ZG and with this module clock #112 is still missing, no?
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/commit/?h=v4.9/rcar-3.5.8&id=aa7b99b06d280e4151e
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/commit/?h=v4.9/rcar-3.5.8&id=a03bfd8abc9572800fb5043
>
> The ZG bits in the FRQCRB register are documented to exist on R-Car D3
> only.
... what contradicts
https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/commit/?h=v4.9/rcar-3.5.8&id=a03bfd8abc9572800fb5043
and the 3DGE module clock in e.g. MSTPSR1 which is documented for H3 and
M3-W, too, and Table 8.1a List of Clocks [R-Car H3] ZG -> 3DGE etc.
Best regards
Dirk
next prev parent reply other threads:[~2017-08-29 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 7:51 clk: renesas: rcar-gen3: Status of Z* clocks? Dirk Behme
2017-08-29 8:01 ` Geert Uytterhoeven
2017-08-29 9:15 ` Dirk Behme
2017-08-29 9:44 ` Geert Uytterhoeven
2017-08-29 10:36 ` Dirk Behme [this message]
2017-08-30 6:48 ` Simon Horman
2017-08-30 6:56 ` Dirk Behme
2017-08-30 9:09 ` Geert Uytterhoeven
2017-08-30 9:27 ` 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=6cad207c-8f9e-3ed9-36e7-16963a6a3892@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.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 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.