cc'ing Mark Brown.
On Tue, Nov 6, 2012 at 10:18 AM, Padmavathi Venna <padma.v@xxxxxxxxxxx> wrote:
> I2S controller has an internal mux for RCLK source clks. The list
> of source clk names were passed through platform data in non-dt case.
> The variable holding the list of RCLK source clk names is not
> required, as the list of clks need to be registered with clkdev
> using generic connection id. This is required as part of adding DT
> support for I2S controller driver.
>
> Signed-off-by: Padmavathi Venna <padma.v@xxxxxxxxxxx>
> ---
> arch/arm/mach-s5pv210/dev-audio.c | 16 ----------------
> 1 files changed, 0 insertions(+), 16 deletions(-)
>
> diff --git a/arch/arm/mach-s5pv210/dev-audio.c b/arch/arm/mach-s5pv210/dev-audio.c
> index 0a5480b..addfb16 100644
> --- a/arch/arm/mach-s5pv210/dev-audio.c
> +++ b/arch/arm/mach-s5pv210/dev-audio.c
> @@ -20,11 +20,6 @@
> #include <mach/irqs.h>
> #include <mach/regs-audss.h>
>
> -static const char *rclksrc[] = {
> - [0] = "busclk",
> - [1] = "i2sclk",
> -};
> -
> static int s5pv210_cfg_i2s(struct platform_device *pdev)
> {
> /* configure GPIO for i2s port */
> @@ -52,7 +47,6 @@ static struct s3c_audio_pdata i2sv5_pdata = {
> .i2s = {
> .quirks = QUIRK_PRI_6CHAN | QUIRK_SEC_DAI
> | QUIRK_NEED_RSTCLR,
> - .src_clk = rclksrc,
> .idma_addr = S5PV210_AUDSS_INT_MEM,
> },
> },
> @@ -75,18 +69,8 @@ struct platform_device s5pv210_device_iis0 = {
> },
> };
>
> -static const char *rclksrc_v3[] = {
> - [0] = "iis",
> - [1] = "audio-bus",
> -};
> -
> static struct s3c_audio_pdata i2sv3_pdata = {
> .cfg_gpio = s5pv210_cfg_i2s,
> - .type = {
> - .i2s = {
> - .src_clk = rclksrc_v3,
> - },
> - },
> };
>
> static struct resource s5pv210_iis1_resource[] = {
> --
> 1.7.4.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
