Tony Lindgren t...@atomide.com writes:
Hi,
Here's a pull request to fix potential hardware breaking configuration
on BeagleBones. For the other fixes, apologies for these coming in so
late, seems that people have been busy finding regressions.
Regards,
Tony
The following changes since
On Fri, Jun 05, 2015 at 06:16:52PM +0100, Mark Brown wrote:
On Fri, Jun 05, 2015 at 07:49:00PM +0900, Greg Kroah-Hartman wrote:
On Thu, Jun 04, 2015 at 10:20:26AM -0700, Tony Lindgren wrote:
Greg, there's now commit 9809889c708e in tty-linus and commit
9e91597f2423 in tty-next.
Yes,
Hello Paul, +Menon (since you asked about the USB_OTG trap),
On 08-06-15 04:38, Paul Walmsley wrote:
Hi Jeroen,
On Sun, 7 Jun 2015, Paul Walmsley wrote:
On Sun, 7 Jun 2015, Jeroen Hofstee wrote:
Turns out my suspicion was wrong. This is what I know at the moment,
depending on the
Hello Paul,
On 07-06-15 21:56, Paul Walmsley wrote:
On Sun, 7 Jun 2015, Jeroen Hofstee wrote:
Turns out my suspicion was wrong. This is what I know at the moment,
depending on the bootpins, u-boot will trigger a bad access when loading
a file over ethernet, but only the first time. Clearing
Since kobject_init_and_add takes a format string, make sure that the
passed in name cannot be accidentally parsed.
Signed-off-by: Kees Cook keesc...@chromium.org
---
drivers/video/fbdev/omap2/dss/display-sysfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Here are some basic OMAP test results for Linux v4.1-rc7.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v4.1-rc7/20150607230110/
Test summary
Build: uImage:
Pass ( 3/ 3): omap1_defconfig, omap1_defconfig_1510innovator_only,
On Wed, May 06, 2015 at 07:39:52AM -0700, Tony Lindgren wrote:
In different SoC we can have different number of CCs (OMAP-L138 has two) and
each CC can have different number of TCs associated with. In AM335x we have
one CC with 3 TC, in OMAP-L138 we have two CC, CC0 has 2 TC, CC1 has 1 TC.
Hi Boris,
On 05/06/15 12:39, Boris Brezillon wrote:
Hi Jon,
On Fri, 5 Jun 2015 09:46:09 +0100
Jon Hunter jonath...@nvidia.com wrote:
On 05/06/15 00:02, Paul Walmsley wrote:
Hi folks
just a brief comment on this one:
On Thu, 30 Apr 2015, Boris Brezillon wrote:
Clock rates are
The crossbar for eDMA works exactly the same way as sDMA, but sDMA
requires an offset of 1, while no offset is needed for eDMA.
Based on the patch from Misael Lopez Cruz misael.lo...@ti.com
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
CC: Misael Lopez Cruz misael.lo...@ti.com
---
Hi,
Changes since v01:
- Drop change in compatible for the crossbar driver and do the configuration
based on the DT structure.
The ti-dma-crossbar driver in it's current form can work when it is used with
sDMA (omap-dma). On DRA7x class of devices we have both sDMA and eDMA available.
The sDMA
From: Misael Lopez Cruz misael.lo...@ti.com
In preparation for supporting multiple DMA crossbar instances,
make the idr xbar instance specific.
Signed-off-by: Misael Lopez Cruz misael.lo...@ti.com
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/ti-dma-crossbar.c | 9
11 matches
Mail list logo
