devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Xing Zheng <zhengxing@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org, keescook@google.com,
	leozwang@google.com, Rob Herring <robh+dt@kernel.org>,
	Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Russell King <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ARM: dts: rockchip: increase the mclk_fs to 512 for kylin board
Date: Tue, 02 Feb 2016 22:43:36 +0100	[thread overview]
Message-ID: <5872159.rO8vOly5eX@diego> (raw)
In-Reply-To: <1454057361-22923-1-git-send-email-zhengxing@rock-chips.com>

Am Freitag, 29. Januar 2016, 16:49:21 schrieb Xing Zheng:
> If we playback the 8KHz FS audio with the 256 mclk_fs, we need the
> mclk = 256 * 8000 = 2.048MHz, the frac div is 594 / 2.048 = 290,
> the frac div value 0x00809015 set to the CRU_CLKSEL7_CON will cause
> to hang.
> 
> We increase the mclk_fs to 512, will get the mclk = 512 * 8000 =
> 4.096MHz, use 0x01009015 instead of 0x00809015 to work around this
> issue. We will keep tracking it.
> 
> Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>

applied to my dts32 branch for 4.6


Thanks
Heiko

      reply	other threads:[~2016-02-02 21:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29  8:49 [RFC PATCH] ARM: dts: rockchip: increase the mclk_fs to 512 for kylin board Xing Zheng
2016-02-02 21:43 ` Heiko Stübner [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=5872159.rO8vOly5eX@diego \
    --to=heiko@sntech.de \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=keescook@google.com \
    --cc=leozwang@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=zhengxing@rock-chips.com \
    /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).