On Tue, 24 Feb 2015 12:40:32 +0200 Tomi Valkeinen tomi.valkei...@ti.com
wrote:
Hi,
On 24/02/15 11:37, NeilBrown wrote:
commit 303e4697e762dc92a40405f4e4b8aac02cd0d70b
OMAPDSS: rename display-sysfs 'name' entry
broke the xorg X server on my device as it couldn't find the
* NeilBrown ne...@suse.de [150223 19:45]:
Hi,
the following 4 patches make some improvements to the twl4030
phy. Together with some other patches I have for twl4030_charger,
they allow for better automatic control of charging.
In particular, the status of the ID pin is assessed and the
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/fixes-v4.0-rc1
for you to fetch changes up to
'max_current' sysfs attributes are created which allow the
max to be set.
Whenever a current source changes, the default is restored.
This will be followed by a uevent, so user-space can decide to
update again.
Signed-off-by: NeilBrown ne...@suse.de
---
drivers/power/twl4030_charger.c | 76
If it cannot, we will stop pulling more current when voltage drops.
Signed-off-by: NeilBrown ne...@suse.de
---
drivers/power/twl4030_charger.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/power/twl4030_charger.c b/drivers/power/twl4030_charger.c
index
The USB Battery Charging spec (BC1.2) suggests a dedicated
charging port can deliver from 0.5 to 5.0A at between 4.75 and 5.25
volts.
To choose the correct current voltage setting requires a trial
and error approach: try to draw current and see if the voltage drops
too low.
Even with a configure
DTS output was formatted to require additional work when copy-pasting into DTS.
Nano-second timings were removed, because they were not a confidence interval
nor
an indication what timing values would result in the same #ticks
Signed-off-by: Robert ABEL ra...@cit-ec.uni-bielefeld.de
---
On Tue, Feb 24, 2015 at 9:05 PM, Robert ABEL
ra...@cit-ec.uni-bielefeld.de wrote:
These are the changes I proposed in two separate patchsets
#([1], [2]) rebased to 3.19 as well as new changes for little bugs
I noticed while preparing this patchset.
It seems my m4d s3d sk177z failed me.
If the phy has been told what current it can draw, it tells us
and now we use that number.
Note that 'vbus_draw' is in mA, while usb_cur is in uA.
Signed-off-by: NeilBrown ne...@suse.de
---
drivers/power/twl4030_charger.c |5 +
1 file changed, 5 insertions(+)
diff --git
'off' or 'auto' to
/sys/class/power/twl4030_usb/mode
will now enable or disable charging from USB port. Normally this is
enabled on 'plug' and disabled on 'unplug'.
Unplug will still disable charging. 'plug' will only enable it if
'auto' if selected.
Signed-off-by: NeilBrown ne...@suse.de
Add a 'continuous' option for usb charging which enabled
the linear charging mode of the twl4030.
Linear charging does a good job with not so reliable power sources, since
several voltage controlling is then often too intelligent.
It was used with a bike hub dynamo since a year or so. In that
This allows AC charging to be turned off, much like usb charging.
continuous (aka linear) mode maps to the CVENAC (constant voltage)
feature of the twl4030.
Signed-off-by: NeilBrown ne...@suse.de
---
drivers/power/twl4030_charger.c | 40 +--
1 file changed,
On 2/23/2015 9:44 AM, Marc Zyngier wrote:
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others (understatement of the year...), I've decided
to split it per sub-arch, and get it moving, at
These are the changes I proposed in two separate patchsets
#([1], [2]) rebased to 3.19 as well as new changes for little bugs
I noticed while preparing this patchset.
1. DEBUG was undefined in source code -- remove offending lines
2. add capability to have busses as children of the GPMC and
* NeilBrown ne...@suse.de [150223 19:45]:
A construct like:
if (pm_runtime_suspended(twl-dev))
pm_runtime_get_sync(twl-dev);
is against the spirit of the runtime_pm interface as it
makes the internal refcounting useless.
In this case it is also racy, particularly
The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
even though the access is defined as asynchronous, and no GPMC_CLK clock
is provided to the external device. Still, GPMCFCLKDIVIDER is used as a divider
for the GPMC clock, so it must be programmed to define the
correct
GPMC_CONFIG1_i parameters CLKACTIVATIONTIME and WAITMONITORINGTIME
have reserved values.
Raise an error if calculated timings try to program reserved values.
GPMC_CONFIG1_i ATTCHEDDEVICEPAGELENGTH and DEVICESIZE were already checked
when parsing the DT.
Explicitly comment invalid values on
OMAP2+ GPMC driver undefines DEBUG, which makes it unnecessarily
hard to turn DEBUG on. Remove the offending lines.
Signed-off-by: Robert ABEL ra...@cit-ec.uni-bielefeld.de
---
drivers/memory/omap-gpmc.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/memory/omap-gpmc.c
GPMC debug output is aligned to 10 characters for field names.
However, some fields have bigger names, screwing up the alignment.
Consequently, alignment was changed to longest field name (17 chars) for now.
Signed-off-by: Robert ABEL ra...@cit-ec.uni-bielefeld.de
---
drivers/memory/omap-gpmc.c
The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
even though the access is defined as asynchronous, and no GPMC_CLK clock
is provided to the external device. Still, GPMCFCLKDIVIDER is used as a divider
for the GPMC clock, so it must be programmed to define the
correct
The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
even though the access is defined as asynchronous, and no GPMC_CLK clock
is provided to the external device. Still, GPMCFCLKDIVIDER is used as a divider
for the GPMC clock, so it must be programmed to define the
correct
This patch adds support for spawning busses as children of the GPMC.
Signed-off-by: Robert ABEL ra...@cit-ec.uni-bielefeld.de
---
drivers/memory/omap-gpmc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
index
* NeilBrown ne...@suse.de [150224 12:35]:
On Tue, 24 Feb 2015 12:40:32 +0200 Tomi Valkeinen tomi.valkei...@ti.com
wrote:
Hi,
On 24/02/15 11:37, NeilBrown wrote:
commit 303e4697e762dc92a40405f4e4b8aac02cd0d70b
OMAPDSS: rename display-sysfs 'name' entry
broke the
On 23/02/15 23:02, Tony Lindgren wrote:
* Marc Zyngier marc.zyng...@arm.com [150223 09:48]:
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others (understatement of the year...), I've decided
On 24/02/15 03:45, Subramaniam Chanderashekarapuram wrote:
Tested this on DRA7 for smp_affinity. Needs these minor fixes attached.
Note: I do not have a OMAP4/5 with me now. Hope to test that tomorrow.
Log for DRA7 are here:
http://pastebin.ubuntu.com/10382176/
Looks good to me. I've
commit 303e4697e762dc92a40405f4e4b8aac02cd0d70b
OMAPDSS: rename display-sysfs 'name' entry
broke the xorg X server on my device as it couldn't find the display
any more. It needs the 'name' file and now there isn't one.
That commit claims that 'name' is not compatible with i2c or spi.
i2c
Hi,
On 24/02/15 11:37, NeilBrown wrote:
commit 303e4697e762dc92a40405f4e4b8aac02cd0d70b
OMAPDSS: rename display-sysfs 'name' entry
broke the xorg X server on my device as it couldn't find the display
any more. It needs the 'name' file and now there isn't one.
That commit claims
In commit 87517d26d888 (ARM: dts: dra7-evm: Add extcon nodes for USB)
we enabled Extcon USB gpio to tackle the USB ID pin and get
peripheral mode to work.
But the extcon-gpio-usb driver [1] didn't make it into v4.0
and this makes the USB driver defer probe indefinitely breaking
USB Host
On 23/02/15 23:38, Robert Abel wrote:
On Tue, Feb 17, 2015 at 3:25 PM, Roger Quadros rog...@ti.com wrote:
one more thing to note is that just specifying sync-clk-ps in DT is not
enough for
asynchronous devices.
The driver doesn't set gpmc_t-sync_clk if gpmc,sync-read or
gpmc,sync-write
On 23/02/15 20:39, Nishanth Menon wrote:
On 02/23/2015 02:32 PM, Nishanth Menon wrote:
On 17:44-20150223, Marc Zyngier wrote:
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others
* Marc Zyngier marc.zyng...@arm.com [150224 01:08]:
On 23/02/15 23:02, Tony Lindgren wrote:
* Marc Zyngier marc.zyng...@arm.com [150223 09:48]:
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive
Hi Rui,
On 02/09/2015 05:01 PM, Nishanth Menon wrote:
On 16:55-20150206, grygorii.stras...@linaro.org wrote:
From: Grygorii Strashko grygorii.stras...@linaro.org
Fix following build warning if CONFIG_PM_SLEEP is not set:
drivers/thermal/ti-soc-thermal/ti-bandgap.c:1478:12: warning:
On Thu, Feb 19, 2015 at 01:32:33PM -0800, Mike Turquette wrote:
Quoting Stephen Boyd (2015-02-06 11:30:18)
On 02/06/15 05:39, Russell King - ARM Linux wrote:
On Thu, Feb 05, 2015 at 05:35:28PM -0800, Stephen Boyd wrote:
From what I can tell this code is
now broken because we made
On Tue, Feb 24, 2015 at 04:21:21PM +0200, Peter Ujfalusi wrote:
Use the dma-requests property from DT to get the number of DMA requests.
In case of legacy boot or failure to find the property, use the default
127 as number of requests.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
The DRA7x has more peripherals with DMA requests than the sDMA can handle:
205 vs 127. All DMA requests are routed through the DMA crossbar, which can
be configured to route selected incoming DMA requests to specific sDMA
request.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Instead of magic numbers in the code, use define for number of logical DMA
channels and DMA requests.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/omap-dma.c
Use the dma-requests property from DT to get the number of DMA requests.
In case of legacy boot or failure to find the property, use the default
127 as number of requests.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 11 ++-
1 file changed, 10
Hi,
The series adds support for DMA router type of devices. They are used in SoCs
which has more peripherals with DMA request lines than the DMA controller can
handle.
The router itself is not part of the DMA controller and it's operation should be
transparent (as it is in the HW) for the SW
Do not direct map the virtual channels to sDMA request number. When the
sDMA is behind of a crossbar this direct mapping can cause situations when
certain channel can not be requested since the crossbar request number
will no longer match with the sDMA request line.
The direct mapping for virtual
DMA routers are transparent devices used to mux DMA requests from
peripherals to DMA controllers. They are used when the SoC integrates more
devices with DMA requests then their controller can handle.
DRA7x is one example of such SoC, where the sDMA can hanlde 128 DMA request
lines, but in SoC
On Tue, Feb 24, 2015 at 04:21:22PM +0200, Peter Ujfalusi wrote:
Do not direct map the virtual channels to sDMA request number. When the
sDMA is behind of a crossbar this direct mapping can cause situations when
certain channel can not be requested since the crossbar request number
will no
Hi,
On Mon, Feb 23, 2015 at 07:24:50PM -0800, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [150223 19:29]:
* Felipe Balbi ba...@ti.com [150223 19:19]:
On Mon, Feb 23, 2015 at 07:01:42PM -0800, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [150223 18:43]:
Looks
On 02/24/2015 04:25 PM, Russell King - ARM Linux wrote:
On Tue, Feb 24, 2015 at 04:21:21PM +0200, Peter Ujfalusi wrote:
Use the dma-requests property from DT to get the number of DMA requests.
In case of legacy boot or failure to find the property, use the default
127 as number of requests.
The sDMA requests are routed through the DMA crossbar and without the
crossbar only peripherals using DMA request 0-127 can be used.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/dra7.dtsi | 57 ++---
1 file changed, 33
Fixes: http://bugs.elinux.org/issues/127
the bb.org community was seeing random reboots before this change.
Signed-off-by: Robert Nelson robertcnel...@gmail.com
---
arch/arm/boot/dts/am335x-bone-common.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git
On Tue, Feb 24, 2015 at 10:10:43AM -0600, Robert Nelson wrote:
Fixes: http://bugs.elinux.org/issues/127
the bb.org community was seeing random reboots before this change.
Signed-off-by: Robert Nelson robertcnel...@gmail.com
that's a dead giveaway considering the connector in the board :-)
* Ravikumar Kattekola r...@ti.com [150219 08:13]:
On 1/31/2015 10:36 PM, Ravikumar Kattekola wrote:
Fix bypass clock source for a few DPLLs.
On DRA7x/OMAP5, for a few DPLLs, both CLKINP and CLKINPULOW are connected
to a mux and the output from mux is routed to the bypass clkout.
Add a
Hi,
On Thu, Feb 05, 2015 at 12:19:23PM +0100, Yegor Yefremov wrote:
I have a problem with my am335x based board and USB.
Kernel: Linux version 3.18.1 (YegorYefremov@development1) (gcc version
4.9.2 (Buildroot 2015.02-git-00797-gf1b07c0) ) #1 SMP Thu Jan 15
15:31:27 CET 2015
I took two
On Tue, Feb 24, 2015 at 10:10 AM, Robert Nelson robertcnel...@gmail.com wrote:
Fixes: http://bugs.elinux.org/issues/127
the bb.org community was seeing random reboots before this change.
Sorry.. ^ beagleboard.org i shouldn't use shorthand in mainline commits..
Regards,
--
Robert Nelson
I have tested it with
X.Org X Server 1.12.4
Release Date: 2012-08-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-4-mx5 armv7l Debian
(coming from Debian Wheezy) on:
* gta04 (SPI panel)
* openpandora (SPI panel)
* BeagleBoard XM (with RGB panel)
* PandaBoard ES (w/o
* Vignesh R vigne...@ti.com [150209 22:43]:
In am33xx and am43xx, ehrpwm tbclk is derived from functional clock of
PWMSS. The schematics and TRMs show that there is only one input clock to
the PWMSS. But currently, tbclk is wrongly shown to be deriving from
dpll_per_m2_ck instead of functional
On 02/24/2015 04:28 PM, Russell King - ARM Linux wrote:
On Tue, Feb 24, 2015 at 04:21:22PM +0200, Peter Ujfalusi wrote:
Do not direct map the virtual channels to sDMA request number. When the
sDMA is behind of a crossbar this direct mapping can cause situations when
certain channel can not be
* Pali Rohár pali.ro...@gmail.com [150218 16:03]:
On Wednesday 18 February 2015 22:02:30 Pali Rohár wrote:
On Wednesday 18 February 2015 13:21:03 Pali Rohár wrote:
Hello,
I tried to test OMAP AES driver on Nokia N900 with special
Nokia bootloader which enable L3 firewall for OMAP
On Tuesday 24 February 2015 18:25:12 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [150218 16:03]:
On Wednesday 18 February 2015 22:02:30 Pali Rohár wrote:
On Wednesday 18 February 2015 13:21:03 Pali Rohár wrote:
Hello,
I tried to test OMAP AES driver on Nokia N900 with
* Pali Rohár pali.ro...@gmail.com [150224 09:42]:
On Tuesday 24 February 2015 18:25:12 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [150218 16:03]:
--- a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
+++ b/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
@@ -3938,8 +3938,9 @@ int
On Tuesday 24 February 2015 18:37:34 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [150224 09:42]:
On Tuesday 24 February 2015 18:25:12 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [150218 16:03]:
--- a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
+++
* Pali Rohár pali.ro...@gmail.com [150224 09:52]:
On Tuesday 24 February 2015 18:37:34 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [150224 09:42]:
On Tuesday 24 February 2015 18:25:12 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [150218 16:03]:
---
On Tue, Feb 24, 2015 at 06:01:23PM +0200, grygorii.stras...@linaro.org wrote:
Hi Rui,
On 02/09/2015 05:01 PM, Nishanth Menon wrote:
On 16:55-20150206, grygorii.stras...@linaro.org wrote:
From: Grygorii Strashko grygorii.stras...@linaro.org
Fix following build warning if CONFIG_PM_SLEEP
* Ivaylo Dimitrov ivo.g.dimitrov...@gmail.com [150209 08:07]:
On 9.02.2015 17:02, Nishanth Menon wrote:
On 17:48-20150208, Ivaylo Dimitrov wrote:
With legacy boot i2c buses on Nokia N900 are numbered i2c1, i2c2 and i2c3.
Commit 20b80942ef4e (ARM: dts: OMAP3+: Add i2c aliases) fixed the
* Roger Quadros rog...@ti.com [150218 00:13]:
On 18/02/15 10:00, Roger Quadros wrote:
On 13/01/15 17:54, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [150113 04:26]:
Hi,
During system suspend L3INIT_960M_GFCLK and L3INIT_480M_GFCLK clocks
remain
active on the DRA7 platform.
* Tony Lindgren t...@atomide.com [150220 07:47]:
* Pali Rohár pali.ro...@gmail.com [150220 01:56]:
On Friday 20 February 2015 10:24:35 Arnd Bergmann wrote:
On Thursday 19 February 2015 17:49:50 Pali Rohár wrote:
Offset for smc91x must be zero otherwise smc91x linux kernel
driver does
* Felipe Balbi ba...@ti.com [150219 10:08]:
As it turns out, tps62362 is actually on I2C bus0,
not bus1. This has gone unnoticed because Linux
doesn't use (as of now) that regulator at all, it's
setup by the bootloader and left as is.
While at that, also add missing reg property for
our
* Peter Ujfalusi peter.ujfal...@ti.com [150220 05:45]:
Hi,
While working on the DMA crossbar support for DRA7 typo of devices I have
noticed that the dma-channels and dma-requests properties of sdma wrongly
has # at the beginning.
According to the documentation, it should not have:
* Felipe Balbi ba...@ti.com [150224 08:23]:
On Tue, Feb 24, 2015 at 10:10:43AM -0600, Robert Nelson wrote:
Fixes: http://bugs.elinux.org/issues/127
the bb.org community was seeing random reboots before this change.
Signed-off-by: Robert Nelson robertcnel...@gmail.com
that's a dead
* Roger Quadros rog...@ti.com [150224 04:40]:
In commit 87517d26d888 (ARM: dts: dra7-evm: Add extcon nodes for USB)
we enabled Extcon USB gpio to tackle the USB ID pin and get
peripheral mode to work.
But the extcon-gpio-usb driver [1] didn't make it into v4.0
and this makes the USB driver
* Roger Quadros rog...@ti.com [150223 07:22]:
Hi,
These changes fix SATA boot and NAND for OMAP based boards.
I must also point out that basic SATA operation is also
broken when TI_PIPE3 driver is built as a module.
I will be investigating that on lower priority.
OK applying into
On Wed, 07 Jan 2015, Vignesh R wrote:
In one shot mode, sequencer automatically disables all enabled steps at
the end of each cycle. (both ADC steps and TSC steps) Hence these steps
need not be saved in reg_se_cache for clearing these steps at a later
stage.
Also, when ADC wakes up Sequencer
On Tue, 24 Feb 2015, NeilBrown wrote:
The twl4030 usb phy needs to be active while we are using
the USB VBUS as a current source for charging.
In particular, the usb3v1 regulator must be enabled and the
PHY_PWR_PHYPWD bit must be set to keep the phy powered.
commit
On 02/24/2015 06:27 PM, Tony Lindgren wrote:
* Ravikumar Kattekola r...@ti.com [150219 08:13]:
On 1/31/2015 10:36 PM, Ravikumar Kattekola wrote:
Fix bypass clock source for a few DPLLs.
On DRA7x/OMAP5, for a few DPLLs, both CLKINP and CLKINPULOW are connected
to a mux and the output from mux
On 02/24/2015 07:15 PM, Tony Lindgren wrote:
* Vignesh R vigne...@ti.com [150209 22:43]:
In am33xx and am43xx, ehrpwm tbclk is derived from functional clock of
PWMSS. The schematics and TRMs show that there is only one input clock to
the PWMSS. But currently, tbclk is wrongly shown to be
On 24/02/15 22:31, NeilBrown wrote:
On Tue, 24 Feb 2015 12:40:32 +0200 Tomi Valkeinen tomi.valkei...@ti.com
wrote:
Hi,
On 24/02/15 11:37, NeilBrown wrote:
commit 303e4697e762dc92a40405f4e4b8aac02cd0d70b
OMAPDSS: rename display-sysfs 'name' entry
broke the xorg X server on my
Hi,
On Thursday 05 February 2015 11:51 AM, Vignesh R wrote:
On Wednesday 21 January 2015 03:44 PM, Vignesh R wrote:
On Tuesday 20 January 2015 09:34 PM, Lee Jones wrote:
On Tue, 20 Jan 2015, R, Vignesh wrote:
On 1/20/2015 5:23 PM, Lee Jones wrote:
On Wed, 07 Jan 2015, Vignesh R wrote:
72 matches
Mail list logo
