From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH/RFC] ARM: shmobile: r8a7794: Add Audio DMAC, PWM and Thermal clocks to device tree
Date: Mon, 05 Jan 2015 20:59:15 +0000 [thread overview]
Message-ID: <12485196.TRR13KWPuE@avalon> (raw)
In-Reply-To: <CAMuHMdXcVrSXd2YzKVQKBFyTwkrOhci0MGs8uA1yk+kX9LDQkg@mail.gmail.com>
Hi Geert,
On Monday 05 January 2015 09:52:37 Geert Uytterhoeven wrote:
> On Mon, Jan 5, 2015 at 9:30 AM, Laurent Pinchart wrote:
> > On Friday 19 December 2014 09:39:33 Simon Horman wrote:
> >> This is based on the MSTP5 clocks in the r8a7791 device tree.
> >> The main difference being that the r8a7794 does not have an Audio DMAC1
> >> clock.
> >>
> >> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> >>
> >> ---
> >> Based on the renesas-devel-20141217-v3.18 tag of my renesas tree.
> >>
> >> N.B: The R-Car Gen2 v1.8.0 BSP uses zs_clk whereas this patch uses hp_clk
> >> as the parent clock for the Audio DMAC clock.
> >>
> >> In that regard this patch follows the pattern used in mainline for
> >> the r8a7790 and r8a7791 SoCs.
> >>
> >> The BSP's parent clock is consistent for the r8a7790, r8a7791,
> >> r8a7793 and r8a7794 SoCs.
> >
> > Does this mean the BSP uses hp_clk for all Gen2 SoCs while mainline uses
> > zs_clk ?
>
> No, it's the other way around ;-)
Sorry, that's what I meant.
> > Can't we find out which one is correct ?
>
> Which clock is used doesn't seem to be documented.
> So either we have to check with the hardware guys, or measure the clock
> in some way, either by hardware or software (e.g. what's the maximum
> transfer rate that works?).
Given the parent clock frequencies (130 MHz and 260 MHz) and the audio rates,
I'm not sure any useful measurement could be performed.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2015-01-05 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 0:39 [PATCH/RFC] ARM: shmobile: r8a7794: Add Audio DMAC, PWM and Thermal clocks to device tree Simon Horman
2015-01-05 8:30 ` Laurent Pinchart
2015-01-05 8:52 ` Geert Uytterhoeven
2015-01-05 20:59 ` Laurent Pinchart [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=12485196.TRR13KWPuE@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.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).