Re: [PATCH V2 0/4] clk: Samsung: audss: Add support for Exynos5420
Hi Mike, On Mon, Aug 19, 2013 at 2:18 PM, Padma Venkat padma@gmail.com wrote: Hi Mike, On Fri, Aug 16, 2013 at 1:19 PM, Padmavathi Venna padm...@samsung.com wrote: This patch set adds support for audio subsystem clks on Exynos5420. Exynos5420 audio subsystem has a gate bit for ADMA controller and the some of the parent clks for mout_i2s and sclk_pcm are different from Exynos5250. So this patch adds provision for supporting both the platforms by determining the parent clk names based on compatible string. Changes since V1: - parent clocks are determined by using the compatible string and not passed via device tree as done in V1 because the probing order of the clock providers can't be guaranteed. Andrew Bresticker (3): clk: exynos-audss: add support for Exynos 5420 clk: exynos-audss: set correct parent clocks Can you apply the above two patches into your tree? If there is no review comment on the above two can you please acknowledge them? The below patch is dependent on these two patches and Kukjin is waiting for these patches to be merged. [V2] ARM: dts: Add DMA controller node info on Exynos5420. https://patchwork.kernel.org/patch/2844436/ Thanks Padma -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH V2 0/4] clk: Samsung: audss: Add support for Exynos5420
Hi Mike, On Fri, Aug 16, 2013 at 1:19 PM, Padmavathi Venna padm...@samsung.com wrote: This patch set adds support for audio subsystem clks on Exynos5420. Exynos5420 audio subsystem has a gate bit for ADMA controller and the some of the parent clks for mout_i2s and sclk_pcm are different from Exynos5250. So this patch adds provision for supporting both the platforms by determining the parent clk names based on compatible string. Changes since V1: - parent clocks are determined by using the compatible string and not passed via device tree as done in V1 because the probing order of the clock providers can't be guaranteed. Andrew Bresticker (3): clk: exynos-audss: add support for Exynos 5420 clk: exynos-audss: set correct parent clocks Can you apply the above two patches into your tree? ARM: dts: exynos5420: add audio clock controller Padmavathi Venna (1): ARM: dts: Correct the /include entry on exynos5420 dtsi file .../devicetree/bindings/clock/clk-exynos-audss.txt |7 +-- arch/arm/boot/dts/exynos5420.dtsi | 11 ++- drivers/clk/samsung/clk-exynos-audss.c | 20 +++- include/dt-bindings/clk/exynos-audss-clk.h |3 ++- 4 files changed, 36 insertions(+), 5 deletions(-) -- 1.7.4.4 Thanks Padma -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH V2 0/4] clk: Samsung: audss: Add support for Exynos5420
This patch set adds support for audio subsystem clks on Exynos5420. Exynos5420 audio subsystem has a gate bit for ADMA controller and the some of the parent clks for mout_i2s and sclk_pcm are different from Exynos5250. So this patch adds provision for supporting both the platforms by determining the parent clk names based on compatible string. Changes since V1: - parent clocks are determined by using the compatible string and not passed via device tree as done in V1 because the probing order of the clock providers can't be guaranteed. Andrew Bresticker (3): clk: exynos-audss: add support for Exynos 5420 clk: exynos-audss: set correct parent clocks ARM: dts: exynos5420: add audio clock controller Padmavathi Venna (1): ARM: dts: Correct the /include entry on exynos5420 dtsi file .../devicetree/bindings/clock/clk-exynos-audss.txt |7 +-- arch/arm/boot/dts/exynos5420.dtsi | 11 ++- drivers/clk/samsung/clk-exynos-audss.c | 20 +++- include/dt-bindings/clk/exynos-audss-clk.h |3 ++- 4 files changed, 36 insertions(+), 5 deletions(-) -- 1.7.4.4 -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
