Re: [PATCH 5/5] arm: boot: store ATAGs structure into DT "/chosen/linux,atags" entry

* Pali Rohár [151126 01:08]: > On Wednesday 25 November 2015 20:19:21 Frank Rowand wrote: > > > Or populate /proc/atags only for the ones that need it from machine > > > specific init_early? > > > > This is circling back to the first comment from Russell King where > > he

Re: [PATCH 5/5] arm: boot: store ATAGs structure into DT "/chosen/linux,atags" entry

On 26.11.2015 22:39, Tony Lindgren wrote: Just to explore options.. How about make a minimal device driver that just loads the atags blob from /lib/firmware and then shows it in /proc/atags? Of course some checking on the atags should be done by the driver.. What is the chance for such a

Re: [PATCH] ARM: dts: dra72-evm: Mark uart1 rxd as wakeup capable

On 11/26/2015 02:31 AM, Vignesh R wrote: > Uart1 rxd is wakeup capable on DRA72 EVM. Hence, mark rxd line as > wakeup capable. This is similar to commit 66b0436977e2c ("ARM: dts: > dra7-evm: Mark uart1 rxd as wakeup capable") for DRA74 EVM. > > Signed-off-by: Vignesh R > --- >

[PATCH] ARM: dts: dra72-evm: Mark uart1 rxd as wakeup capable

Uart1 rxd is wakeup capable on DRA72 EVM. Hence, mark rxd line as wakeup capable. This is similar to commit 66b0436977e2c ("ARM: dts: dra7-evm: Mark uart1 rxd as wakeup capable") for DRA74 EVM. Signed-off-by: Vignesh R --- arch/arm/boot/dts/dra72-evm.dts | 2 ++ 1 file

Re: [PATCH 5/5] arm: boot: store ATAGs structure into DT "/chosen/linux,atags" entry

On Wednesday 25 November 2015 20:19:21 Frank Rowand wrote: > > Or populate /proc/atags only for the ones that need it from machine > > specific init_early? > > This is circling back to the first comment from Russell King where > he suggested a legacy file for the N900 which calls save_atags(): >

Re: Clock usbhost_48m_fck didn't enable in 100000 tries and crash

Daniel, On 24/11/15 15:36, Daniel. wrote: > Hi Michael > > About this: > "Two bugs are fixed by this patch. First, OMAP hardware only supports > target CM_IDLEST register bits on ES2+ chips and beyond. ES1 chips > should not wait for these clocks to enable. So, split the appropriate >

Re: [PATCH] remoteproc/wkup_m3: Use MODULE_DEVICE_TABLE to export alias

On Wed, Sep 16, 2015 at 3:32 PM, Dave Gerlach wrote: > Use MODULE_DEVICE_TABLE with wkup_m3_rproc_of_match so the module alias > is exported and the wkup_m3_rproc driver can automatically probe. > > Signed-off-by: Dave Gerlach Applied to remoteproc-next,

Re: [PATCH] regulator: tps65218: add support for LS3 current regulator

On Wed, 25 Nov 2015, Nikita Kiryanov wrote: > Add support for TPS65218 LS3 current regulator, which is capable of 4 > current input limit modes: 100, 200, 500, and 1000 uA. > > Signed-off-by: Nikita Kiryanov > Cc: Tony Lindgren > Cc: Liam Girdwood

Re: [PATCH 06/14] ARM: am437x: cm-t43: dts: add dual emac support

On Tuesday 24 November 2015 06:49 PM, Nikita Kiryanov wrote: > CM-T43 comes with 2 ethernet ports connected to the cpsw subsystem, which > has 2 modes of operation: switch mode and dual emac mode. > Add the relevant muxing and set it up to work in dual emac mode by > default. > > Signed-off-by:

[PATCH v2] ARM: omap2+: enable REGULATOR_FIXED_VOLTAGE

Enable REGULATOR_FIXED_VOLTAGE for all OMAP2+ platforms otherwise system can't boot from SD-card when kernel is built for single SoC (for example, with CONFIG_SOC_DRA7XX=y only). It's also required for almost all TI SoC's platforms. Signed-off-by: Grygorii Strashko ---

Re: [PATCH] ARM: omap2plus_defconfig: enable REGULATOR_FIXED_VOLTAGE

On 11/25/2015 10:57 PM, Tony Lindgren wrote: * Grygorii Strashko [151125 12:26]: On 11/25/2015 08:25 PM, Tony Lindgren wrote: * Grygorii Strashko [151105 08:45]: Enable REGULATOR_FIXED_VOLTAGE otherwise system can't boot from SD-card when