From: Marek Szyprowski <m.szyprowski@samsung.com>
To: alsa-devel@alsa-project.org
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
pawel.moll@arm.com, zhen1.chen@samsung.com,
Kyungmin Park <kyungmin.park@samsung.com>,
Mark Brown <broonie@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
alsa-devel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [alsa-devel] [PATCH V2 0/2] Sound support for Exynos4412 Odroid X2, U3 board
Date: Tue, 24 Jun 2014 11:02:01 +0200 [thread overview]
Message-ID: <53A93E89.2030901@samsung.com> (raw)
In-Reply-To: <CAD8Lp46gqbV9gDfrH2hbVnF7s6wK6ASBdsX7vn0L0CFAHXSemg@mail.gmail.com>
Hello,
On 2014-06-24 10:35, Daniel Drake wrote:
> On Mon, Jun 23, 2014 at 5:32 PM, Sylwester Nawrocki
> <s.nawrocki@samsung.com> wrote:
>> I could reproduce such behaviour on the U3 board, but only with u-boot
>> which sets the MPLL clock frequency (fout_mpll) to 880 MHz, rather
>> than 800 MHz, which was the case in my original environment.
>> All fout_mpll child clocks have then different frequency values
>> in both cases.
>> It's a bit strange though, because frequencies of all the audio
>> subsystem clocks seem to be same anyway:
> I'm using the standard uboot from hardkernel.
>
>> # cat /sys/kernel/debug/clk/clk_summary
> This command makes the kernel totally hang, weird.
This is known issue with clocks vs. ISP power domain. We should really
fix this in exynos4 clock driver.
> # speaker-test -c 2 -t wav -l 2 -p 1024
>
> This plays back fine.
>
> Could it be a problem with the samsung-i2s driver, not correctly
> flushing at the right times?
> Or do you think the problem is more likely to be clock-related?
Hard to say right now, but at least we need to test a bit more our
solutions with different initial clocks configuration.
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
--
To unsubscribe from this list: send the line "unsubscribe alsa-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
WARNING: multiple messages have this Message-ID (diff)
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Daniel Drake <drake@endlessm.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: devicetree@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
pawel.moll@arm.com, zhen1.chen@samsung.com,
Kyungmin Park <kyungmin.park@samsung.com>,
Kumar Gala <galak@codeaurora.org>,
alsa-devel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 0/2] Sound support for Exynos4412 Odroid X2, U3 board
Date: Tue, 24 Jun 2014 11:02:01 +0200 [thread overview]
Message-ID: <53A93E89.2030901@samsung.com> (raw)
In-Reply-To: <CAD8Lp46gqbV9gDfrH2hbVnF7s6wK6ASBdsX7vn0L0CFAHXSemg@mail.gmail.com>
Hello,
On 2014-06-24 10:35, Daniel Drake wrote:
> On Mon, Jun 23, 2014 at 5:32 PM, Sylwester Nawrocki
> <s.nawrocki@samsung.com> wrote:
>> I could reproduce such behaviour on the U3 board, but only with u-boot
>> which sets the MPLL clock frequency (fout_mpll) to 880 MHz, rather
>> than 800 MHz, which was the case in my original environment.
>> All fout_mpll child clocks have then different frequency values
>> in both cases.
>> It's a bit strange though, because frequencies of all the audio
>> subsystem clocks seem to be same anyway:
> I'm using the standard uboot from hardkernel.
>
>> # cat /sys/kernel/debug/clk/clk_summary
> This command makes the kernel totally hang, weird.
This is known issue with clocks vs. ISP power domain. We should really
fix this in exynos4 clock driver.
> # speaker-test -c 2 -t wav -l 2 -p 1024
>
> This plays back fine.
>
> Could it be a problem with the samsung-i2s driver, not correctly
> flushing at the right times?
> Or do you think the problem is more likely to be clock-related?
Hard to say right now, but at least we need to test a bit more our
solutions with different initial clocks configuration.
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
WARNING: multiple messages have this Message-ID (diff)
From: m.szyprowski@samsung.com (Marek Szyprowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/2] Sound support for Exynos4412 Odroid X2, U3 board
Date: Tue, 24 Jun 2014 11:02:01 +0200 [thread overview]
Message-ID: <53A93E89.2030901@samsung.com> (raw)
In-Reply-To: <CAD8Lp46gqbV9gDfrH2hbVnF7s6wK6ASBdsX7vn0L0CFAHXSemg@mail.gmail.com>
Hello,
On 2014-06-24 10:35, Daniel Drake wrote:
> On Mon, Jun 23, 2014 at 5:32 PM, Sylwester Nawrocki
> <s.nawrocki@samsung.com> wrote:
>> I could reproduce such behaviour on the U3 board, but only with u-boot
>> which sets the MPLL clock frequency (fout_mpll) to 880 MHz, rather
>> than 800 MHz, which was the case in my original environment.
>> All fout_mpll child clocks have then different frequency values
>> in both cases.
>> It's a bit strange though, because frequencies of all the audio
>> subsystem clocks seem to be same anyway:
> I'm using the standard uboot from hardkernel.
>
>> # cat /sys/kernel/debug/clk/clk_summary
> This command makes the kernel totally hang, weird.
This is known issue with clocks vs. ISP power domain. We should really
fix this in exynos4 clock driver.
> # speaker-test -c 2 -t wav -l 2 -p 1024
>
> This plays back fine.
>
> Could it be a problem with the samsung-i2s driver, not correctly
> flushing at the right times?
> Or do you think the problem is more likely to be clock-related?
Hard to say right now, but at least we need to test a bit more our
solutions with different initial clocks configuration.
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2014-06-24 9:02 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 16:22 [alsa-devel] [PATCH V2 0/2] Sound support for Exynos4412 Odroid X2, U3 board Sylwester Nawrocki
2014-06-18 16:22 ` Sylwester Nawrocki
2014-06-18 16:22 ` Sylwester Nawrocki
2014-06-18 16:22 ` [PATCH V2 1/2] ASoC: samsung: Add machine driver for Odroid X2/U3 Sylwester Nawrocki
2014-06-18 16:22 ` [alsa-devel] " Sylwester Nawrocki
2014-06-18 16:22 ` Sylwester Nawrocki
2014-06-18 16:22 ` Sylwester Nawrocki
2014-06-25 3:31 ` [alsa-devel] " Tushar Behera
2014-06-25 3:31 ` Tushar Behera
2014-06-26 8:47 ` Sylwester Nawrocki
2014-06-26 8:47 ` Sylwester Nawrocki
2014-06-30 18:46 ` Mark Brown
2014-06-30 18:46 ` [alsa-devel] " Mark Brown
2014-06-30 18:46 ` Mark Brown
2014-06-30 18:46 ` Mark Brown
2014-07-14 11:27 ` Sylwester Nawrocki
2014-07-14 11:27 ` [alsa-devel] " Sylwester Nawrocki
2014-07-14 11:27 ` Sylwester Nawrocki
2014-07-14 11:27 ` Sylwester Nawrocki
2014-07-14 11:31 ` [alsa-devel] " Mark Brown
2014-07-14 11:31 ` Mark Brown
2014-07-14 11:31 ` Mark Brown
2014-07-14 11:31 ` Mark Brown
2014-06-18 16:22 ` [PATCH V2 2/2] doc: dt bindings: Document Odroid X2/U3 audio subsystem bindings Sylwester Nawrocki
2014-06-18 16:22 ` [alsa-devel] " Sylwester Nawrocki
2014-06-18 16:22 ` Sylwester Nawrocki
2014-06-18 16:22 ` Sylwester Nawrocki
2014-06-23 9:40 ` [alsa-devel] [PATCH V2 0/2] Sound support for Exynos4412 Odroid X2, U3 board Daniel Drake
2014-06-23 9:40 ` Daniel Drake
2014-06-23 9:40 ` Daniel Drake
2014-06-23 16:32 ` [alsa-devel] " Sylwester Nawrocki
2014-06-23 16:32 ` Sylwester Nawrocki
2014-06-23 16:32 ` Sylwester Nawrocki
2014-06-23 16:53 ` [alsa-devel] " Sylwester Nawrocki
2014-06-23 16:53 ` Sylwester Nawrocki
2014-06-23 16:53 ` Sylwester Nawrocki
2014-06-23 16:53 ` Sylwester Nawrocki
2014-06-24 8:35 ` [alsa-devel] " Daniel Drake
2014-06-24 8:35 ` Daniel Drake
2014-06-24 8:35 ` Daniel Drake
2014-06-24 9:02 ` Marek Szyprowski [this message]
2014-06-24 9:02 ` Marek Szyprowski
2014-06-24 9:02 ` Marek Szyprowski
2014-06-24 9:02 ` Marek Szyprowski
2014-06-24 8:35 ` Daniel Drake
2014-06-23 16:32 ` Sylwester Nawrocki
2014-06-23 9:40 ` Daniel Drake
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=53A93E89.2030901@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-devel@vger.kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=zhen1.chen@samsung.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 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.