From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Szyprowski Subject: Re: [PATCH V2 0/2] Sound support for Exynos4412 Odroid X2, U3 board Date: Tue, 24 Jun 2014 11:02:01 +0200 Message-ID: <53A93E89.2030901@samsung.com> References: <1403108551-25058-1-git-send-email-s.nawrocki@samsung.com> <53A856AE.1030202@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-reply-to: Sender: linux-samsung-soc-owner@vger.kernel.org To: Daniel Drake , Sylwester Nawrocki Cc: devicetree@vger.kernel.org, Mark Brown , Mark Rutland , linux-samsung-soc , pawel.moll@arm.com, zhen1.chen@samsung.com, Kyungmin Park , Kumar Gala , alsa-devel@vger.kernel.org, linux-arm-kernel@lists.infradead.org List-Id: devicetree@vger.kernel.org Hello, On 2014-06-24 10:35, Daniel Drake wrote: > On Mon, Jun 23, 2014 at 5:32 PM, Sylwester Nawrocki > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-id: <53A93E89.2030901@samsung.com> Date: Tue, 24 Jun 2014 11:02:01 +0200 From: Marek Szyprowski MIME-version: 1.0 References: <1403108551-25058-1-git-send-email-s.nawrocki@samsung.com> <53A856AE.1030202@samsung.com> In-reply-to: Subject: Re: [alsa-devel] [PATCH V2 0/2] Sound support for Exynos4412 Odroid X2, U3 board List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: alsa-devel@alsa-project.org Cc: Mark Rutland , devicetree@vger.kernel.org, linux-samsung-soc , pawel.moll@arm.com, zhen1.chen@samsung.com, Kyungmin Park , Mark Brown , Kumar Gala , alsa-devel@vger.kernel.org, linux-arm-kernel@lists.infradead.org List-ID: Hello, On 2014-06-24 10:35, Daniel Drake wrote: > On Mon, Jun 23, 2014 at 5:32 PM, Sylwester Nawrocki > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: m.szyprowski@samsung.com (Marek Szyprowski) Date: Tue, 24 Jun 2014 11:02:01 +0200 Subject: [PATCH V2 0/2] Sound support for Exynos4412 Odroid X2, U3 board In-Reply-To: References: <1403108551-25058-1-git-send-email-s.nawrocki@samsung.com> <53A856AE.1030202@samsung.com> Message-ID: <53A93E89.2030901@samsung.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hello, On 2014-06-24 10:35, Daniel Drake wrote: > On Mon, Jun 23, 2014 at 5:32 PM, Sylwester Nawrocki > 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