From: Kieran Bingham <kieran@bingham.xyz>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: linux-renesas-soc@vger.kernel.org
Subject: Re: R8A7795 FDP1 clock parentage
Date: Mon, 30 May 2016 10:58:53 +0100 [thread overview]
Message-ID: <574C0EDD.4050101@bingham.xyz> (raw)
In-Reply-To: <87y46s9i4i.wl%kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
On 30/05/16 07:32, Kuninori Morimoto wrote:
>>> Just to add to this request, could you ask the HW engineers to confirm
>>> the clock parents for the FCPF (0,1,2) as well please?
>>>
>>> They too are currently listed as R8A7795_CLK_S2D1, however now that I am
>>> trying to enable the FCPF and read registers from it - the VCR is
>>> returning as 0x00 (I expect 0x0101) and then I'm getting
>>> "Bad mode in Error handler detected, code 0xbf000002 -- SError"
>>>
>>> My suspicion is that my clock has not been enabled correctly :)
>>
>> About FCP, I had same request from Laurent, and its answer was this thread.
>>
>> http://thread.gmane.org/gmane.linux.kernel.renesas-soc/662/focus=1304
Thank you for that reference. It was helpful!
>> # I think this "parent clock" settings itself is not super critical
>> # (= it works anyway with wrong settings)
>> # it seems other issues ?
You were right :) - It was the power-domain. It's resolved now and
working. Thank you for your help.
> I got information from HW team.
> About H3 ES1 FDP1 parent clock is "S2D1"
Perfect, thanks for confirming this. Now the patch is unblocked from
submission.
--
Regards
Kieran Bingham
prev parent reply other threads:[~2016-05-30 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 8:41 R8A7795 FDP1 clock parentage Kieran Bingham
2016-05-25 8:49 ` Kuninori Morimoto
2016-05-25 17:10 ` Kieran Bingham
2016-05-26 0:01 ` Kuninori Morimoto
2016-05-30 6:32 ` Kuninori Morimoto
2016-05-30 9:58 ` Kieran Bingham [this message]
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=574C0EDD.4050101@bingham.xyz \
--to=kieran@bingham.xyz \
--cc=kuninori.morimoto.gx@renesas.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox