> -----Original Message----- > From: Hiremath, Vaibhav > Sent: Tuesday, May 07, 2013 3:10 PM > To: linux-omap@xxxxxxxxxxxxxxx > Cc: tony@xxxxxxxxxxx; Cousson, Benoit; paul@xxxxxxxxx; linux-arm- > kernel@xxxxxxxxxxxxxxxxxxx; Hiremath, Vaibhav > Subject: [PATCH 0/2] ARM: OMAP AM33XX: clock data: Enable clkout2 > output on SoC pad > > 'clkout2' comes out on the device pad and is being used by various > external on-board peripherals like, Audio codecs, Wilink and stuff. > So enable the clkout2 by default during init sequence itself > along with right pinmux configuration clkout2 output. > > Also, add the missing entry of "clkout2_ck" to the AM33xx clock table. > > As far as enabling of clkout2 during init is concerned, > we can argue that it can be handled using DT property and enable > the clock only when specified; but not until OMAP clock-tree > migration to DT. > > Vaibhav Hiremath (2): > ARM: OMAP AM33XX: clock data: Enable clkout2 as part of init > ARM: dts: AM33XX: Set pinmux for clkout2 pad used for clock output > > arch/arm/boot/dts/am335x-bone.dts | 8 +++++++- > arch/arm/boot/dts/am335x-evm.dts | 8 +++++++- > arch/arm/boot/dts/am335x-evmsk.dts | 8 +++++++- > arch/arm/mach-omap2/cclock33xx_data.c | 2 ++ > 4 files changed, 23 insertions(+), 3 deletions(-) Tony, Paul and Benoit, Any update on this series? Thanks, Vaibhav -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
