Quoting Peter Ujfalusi (2014-07-14 03:10:28)
On 05/06/2014 04:39 PM, Peter Ujfalusi wrote:
Tero: can I have your ack for this patch or do you have further concerns?
Yea looks good to me, except for the fact that there is some work on
getting
default rate/parent support through DT. I
* Paul Walmsley p...@pwsan.com [140725 12:16]:
On Mon, 7 Jul 2014, Tony Lindgren wrote:
With v3.16-rc4 the PM features for omap3 should be working
finally for device tree based booting. At lest beaglexm and
3xxevm should work.
Just to follow up briefly on this: there was indeed a bug
* Felipe Balbi ba...@ti.com [140728 11:13]:
On Mon, Jul 28, 2014 at 12:57:39PM -0500, Michael Welling wrote:
On Mon, Jul 28, 2014 at 10:57:18AM -0500, Felipe Balbi wrote:
Basically it means what you said above: the hub disconnected. I
can't
tell why. You'll have to ask
On 07/29/2014 09:27 AM, Mike Turquette wrote:
Quoting Peter Ujfalusi (2014-07-14 03:10:28)
On 05/06/2014 04:39 PM, Peter Ujfalusi wrote:
Tero: can I have your ack for this patch or do you have further concerns?
Yea looks good to me, except for the fact that there is some work on getting
On Mon, 28 Jul 2014, Tony Lindgren wrote:
Hmm I think the difference with the working v3.10 one is that you have
root=/dev/mmcblk0p2 instead of root=/dev/nfs. As the Ethernet on beagle
is on the USB EHCI, this is still blocking the deeper idle states AFAIK.
Hmm? There's no Ethernet on the
On Tue, 29 Jul 2014, Paul Walmsley wrote:
I should probably read back those writes to autosuspend_delay_ms, just to
make sure they are reaching the right destinations.
Just took a whack at that, looks like the autosuspend_delay_ms files are
being set correctly:
* Paul Walmsley p...@pwsan.com [140729 01:27]:
On Mon, 28 Jul 2014, Tony Lindgren wrote:
Hmm I think the difference with the working v3.10 one is that you have
root=/dev/mmcblk0p2 instead of root=/dev/nfs. As the Ethernet on beagle
is on the USB EHCI, this is still blocking the deeper
Hi Michael,
On 07/28/2014 09:10 PM, Felipe Balbi wrote:
On Mon, Jul 28, 2014 at 12:57:39PM -0500, Michael Welling wrote:
On Mon, Jul 28, 2014 at 10:57:18AM -0500, Felipe Balbi wrote:
Hi,
On Mon, Jul 28, 2014 at 10:29:49AM -0500, Michael Welling wrote:
On Mon, Jul 28, 2014 at 11:02:47AM
* Suman Anna s-a...@ti.com [140624 17:45]:
Hi,
This patch series is mainly a cleanup of the current OMAP mailbox drivers
in preparation for adding DT support and adoption to the upcoming mailbox
framework from Jassi Brar [1]. It removes the OMAP1 mailbox driver as there
are no users for it
* Roger Quadros rog...@ti.com [140728 02:48]:
This driver is needed by SATA, PCIe and USB modules on TI SoCs.
Signed-off-by: Roger Quadros rog...@ti.com
You need to send this to a...@kernel.org to avoid conflicts.
Acked-by: Tony Lindgren t...@atomide.com
---
The following changes since commit 33753cd2ba41c72a0756edc5dc094d91602deda5:
ARM: OMAP2+: gpmc: fix gpmc_hwecc_bch_capable() (2014-07-23 01:48:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
* Roger Quadros rog...@ti.com [140711 03:25]:
On 07/11/2014 12:42 PM, Gupta, Pekon wrote:
Therefore, I suggest you to move following code from NAND driver to
GPMC driver, nothing other than. And this exported function does not
need any NAND framework information, except number_of_sectors.
On Wed, Jul 23, 2014 at 04:00:47PM +0200, Laurent Pinchart wrote:
Thank you. Assuming there's currently no conflict to be resolved, I believe
the easiest would be for both you and Tony to merge my branch in your trees.
Okay, I applied the patches to my arm/omap branch. I will push them out
Hi Suman,
On Tue, Jul 8, 2014 at 7:22 PM, Suman Anna s-a...@ti.com wrote:
The remoteproc driver core currently relies on iommu_present() on
the bus the device is on, to perform MMU management. However, this
logic doesn't scale for multi-arch, especially for processors that
do not have an
Hi Suman,
On Tue, Jul 8, 2014 at 7:22 PM, Suman Anna s-a...@ti.com wrote:
A remote processor may need to load certain firmware sections into
internal memories (eg: RAM at L1 or L2 levels) for performance or
other reasons.
Can you please provide as much details as you can about the scenario
On Tuesday 29 July 2014 03:32:24 Tony Lindgren wrote:
The following changes since commit 33753cd2ba41c72a0756edc5dc094d91602deda5:
ARM: OMAP2+: gpmc: fix gpmc_hwecc_bch_capable() (2014-07-23 01:48:24 -0700)
are available in the git repository at:
* Paul Walmsley p...@pwsan.com [140725 05:58]:
Hi Tony
The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:
Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git
* Felipe Balbi ba...@ti.com [140725 09:55]:
On Tue, Jul 22, 2014 at 09:14:20PM +, Paul Walmsley wrote:
On Tue, 17 Jun 2014, Tomi Valkeinen wrote:
From: Sathya Prakash M R sath...@ti.com
Add DSS hwmod data for AM43xx.
Signed-off-by: Sathya Prakash M R sath...@ti.com
* Arnd Bergmann a...@arndb.de [140729 04:08]:
On Tuesday 29 July 2014 03:32:24 Tony Lindgren wrote:
The following changes since commit 33753cd2ba41c72a0756edc5dc094d91602deda5:
ARM: OMAP2+: gpmc: fix gpmc_hwecc_bch_capable() (2014-07-23 01:48:24
-0700)
are available in the git
The following changes since commit cbf14f3ab9bd6295b345fc812f08ddd844fb183e:
ARM: AM33xx: hwmod_data: Remove legacy mailbox addrs (2014-07-15 05:08:56
-0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
* Felipe Balbi ba...@ti.com [140728 14:19]:
OMAP INTC irqchip driver will be moved under
drivers/irqchip/ soon but we still have a dependency
with mach-omap2 when it comes to idle functions.
In order to make it easy to share those function
prototypes with OMAP PM code, we introduce this new
Hi Pekon,
On 07/23/2014 01:58 PM, Pekon Gupta wrote:
This patch adds support for parallel NOR device (S29GL512S10) present on
J6-EVM.
The Flash device is connected to GPMC controller on chip-select[0] and
accessed
as memory-mapped device. It has data-witdh=x16, capacity-64MBytes(512Mbits)
* Felipe Balbi ba...@ti.com [140728 14:19]:
now that we don't need to support legacy board-files,
we can completely switch over to a linear irq domain
and make use of irq_alloc_domain_generic_chips() to
allocate all generic irq chips for us.
This patch seems to somehow break off-idle for
On Tue, 29 Jul 2014, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [140729 01:27]:
On Mon, 28 Jul 2014, Tony Lindgren wrote:
Hmm I think the difference with the working v3.10 one is that you have
root=/dev/mmcblk0p2 instead of root=/dev/nfs. As the Ethernet on beagle
is on
On Wednesday 23 July 2014 14:29:36 Kishon Vijay Abraham I wrote:
On Monday 21 July 2014 08:45 PM, Felipe Balbi wrote:
On Mon, Jul 21, 2014 at 05:04:57PM +0200, Laurent Pinchart wrote:
Hi Felipe,
What happened to these two patches ?
looks like I lost them.
On Monday 16 December
* Dr. H. Nikolaus Schaller h...@goldelico.com [140728 13:45]:
Yes,
the boot loader either loads gta04a3.dtb gta04.dtb or gta05.dtb
depending on board revision.
Therefore we have multiple device tree files to represent such hardware
differences. Like Gumstix Overo variants (using a
On Tue, 29 Jul 2014, Paul Walmsley wrote:
I will add code to read back the values from the sysfs files, just to make
sure they are being set.
Confirmed that they are.
Are you using NFS root on 37xxevm or MMC root?
- Paul
--
To unsubscribe from this list: send the line unsubscribe
Hi,
Am 29.07.2014 um 14:41 schrieb Tony Lindgren:
* Dr. H. Nikolaus Schaller h...@goldelico.com [140728 13:45]:
Yes,
the boot loader either loads gta04a3.dtb gta04.dtb or gta05.dtb
depending on board revision.
Therefore we have multiple device tree files to represent such hardware
Hello,
On Tue, Jul 29, 2014 at 3:03 PM, Dr. H. Nikolaus Schaller
h...@goldelico.com wrote:
Hi,
So what's the conclusion? Are changes needed to this patch
series or not?
I advocate that no changes are needed.
I agree with Dr. H. Nikolaus on this regard. A DeviceTree should be a
description
On Tue, Jul 29, 2014 at 05:01:33AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140728 14:19]:
OMAP INTC irqchip driver will be moved under
drivers/irqchip/ soon but we still have a dependency
with mach-omap2 when it comes to idle functions.
In order to make it easy to
Hi,
On Tue, Jul 29, 2014 at 05:14:25AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140728 14:19]:
now that we don't need to support legacy board-files,
we can completely switch over to a linear irq domain
and make use of irq_alloc_domain_generic_chips() to
allocate all
* Paul Walmsley p...@pwsan.com [140729 06:00]:
On Tue, 29 Jul 2014, Paul Walmsley wrote:
I will add code to read back the values from the sysfs files, just to make
sure they are being set.
Confirmed that they are.
Hmm maybe different u-boot version then? I'm using
* Felipe Balbi ba...@ti.com [140729 07:13]:
On Tue, Jul 29, 2014 at 05:01:33AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140728 14:19]:
OMAP INTC irqchip driver will be moved under
drivers/irqchip/ soon but we still have a dependency
with mach-omap2 when it comes to idle
* Felipe Balbi ba...@ti.com [140729 07:18]:
Hi,
On Tue, Jul 29, 2014 at 05:14:25AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140728 14:19]:
now that we don't need to support legacy board-files,
we can completely switch over to a linear irq domain
and make use of
On Tue, Jul 29, 2014 at 08:06:55AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140729 07:13]:
On Tue, Jul 29, 2014 at 05:01:33AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140728 14:19]:
OMAP INTC irqchip driver will be moved under
drivers/irqchip/ soon but
On Tue, Jul 29, 2014 at 11:59:07AM +0300, Roger Quadros wrote:
Hi Michael,
On 07/28/2014 09:10 PM, Felipe Balbi wrote:
On Mon, Jul 28, 2014 at 12:57:39PM -0500, Michael Welling wrote:
On Mon, Jul 28, 2014 at 10:57:18AM -0500, Felipe Balbi wrote:
Hi,
On Mon, Jul 28, 2014 at 10:29:49AM
* Felipe Balbi ba...@ti.com [140729 08:22]:
On Tue, Jul 29, 2014 at 08:06:55AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140729 07:13]:
This is the third time I rebase the series after a long hiatus and it
always comes out to the same result - let's wait some more.
On Tuesday 29 July 2014 04:39:18 Tony Lindgren wrote:
The following changes since commit cbf14f3ab9bd6295b345fc812f08ddd844fb183e:
ARM: AM33xx: hwmod_data: Remove legacy mailbox addrs (2014-07-15 05:08:56
-0700)
are available in the git repository at:
On Tue, Jul 29, 2014 at 04:20:20AM +0200, Sebastian Reichel wrote:
Hi,
On Mon, Jul 28, 2014 at 04:16:01PM -0500, Felipe Balbi wrote:
this will let us drop .handle_irq and .init_irq fields
from our generic machine_descs.
Signed-off-by: Felipe Balbi ba...@ti.com
---
On Tue, Jul 29, 2014 at 08:20:52AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140729 07:18]:
Hi,
On Tue, Jul 29, 2014 at 05:14:25AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140728 14:19]:
now that we don't need to support legacy board-files,
we can
On 07/29/2014 03:59 AM, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [140624 17:45]:
Hi,
This patch series is mainly a cleanup of the current OMAP mailbox drivers
in preparation for adding DT support and adoption to the upcoming mailbox
framework from Jassi Brar [1]. It removes the OMAP1
Hi,
On Tue, Jul 29, 2014 at 10:36:49AM -0500, Felipe Balbi wrote:
On Tue, Jul 29, 2014 at 04:20:20AM +0200, Sebastian Reichel wrote:
Hi,
On Mon, Jul 28, 2014 at 04:16:01PM -0500, Felipe Balbi wrote:
this will let us drop .handle_irq and .init_irq fields
from our generic
Hi Ohad,
On 07/29/2014 05:57 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Tue, Jul 8, 2014 at 7:22 PM, Suman Anna s-a...@ti.com wrote:
The remoteproc driver core currently relies on iommu_present() on
the bus the device is on, to perform MMU management. However, this
logic doesn't scale for
On Tue, Jul 29, 2014 at 1:23 AM, Tero Kristo t-kri...@ti.com wrote:
On 07/29/2014 09:27 AM, Mike Turquette wrote:
Quoting Peter Ujfalusi (2014-07-14 03:10:28)
On 05/06/2014 04:39 PM, Peter Ujfalusi wrote:
Tero: can I have your ack for this patch or do you have further
concerns?
Yea
Hi,
On Tue, Jul 29, 2014 at 10:40:57AM -0500, Felipe Balbi wrote:
On Tue, Jul 29, 2014 at 08:20:52AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140729 07:18]:
Hi,
On Tue, Jul 29, 2014 at 05:14:25AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140728
Hi,
On Tue, Jul 29, 2014 at 02:38:24PM +0200, Laurent Pinchart wrote:
On Wednesday 23 July 2014 14:29:36 Kishon Vijay Abraham I wrote:
On Monday 21 July 2014 08:45 PM, Felipe Balbi wrote:
On Mon, Jul 21, 2014 at 05:04:57PM +0200, Laurent Pinchart wrote:
Hi Felipe,
What happened to
Hi,
this series is on top of [PATCH v4] 8250-core based serial driver for OMAP.
I will refresh it once I fixed the runtime-pm issue.
Patches 1-3 are independent of the series and just bug fixes. Patches 4+ are
RFC only for now. Its been tested on dra7, am33xx won't work as-is (even with
patch 5
The rx path of the 8250_dma user in the RX-timeout case:
- it starts the RX transfer
- if the rx-timeout interrupt occures, it dmaengine_pause() the transfer
- step two is dmaengine_terminate_all() on this channel.
- based on dmaengine_tx_status() it learns the number of transfered
bytes.
- the
The rx path of the 8250_dma user in the RX-timeout case:
- it starts the RX transfer
- if the rx-timeout interrupt occures, it dmaengine_pause() the transfer
- step two is dmaengine_terminate_all() on this channel.
- the rx interrupt occures, it does not start the RX-transfer because
according
After TX dma completes the code will queue another DMA transfer. If
serial8250_tx_dma() fails then there is no plan B to continue the
transfer manually.
This patch enables the TX-fifo empty event so it can be tried again via
DMA or use the manual fallback in case it fails.
Cc: Heikki Krogerus
This patch adds the required pieces to OMAP uart for DMA support. The TX
burst size is set to 1 so we can send an arbitrary amout of bytes.
The RX burst is currently set to 8 which means we receive an interrupt
every eight bytes and have to reprogramm everything. Seven bytes in the
RX-fifo mean
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
arch/arm/boot/dts/dra7.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi b/arch/arm/boot/dts/dra7.dtsi
index 10066f4..a904561 100644
--- a/arch/arm/boot/dts/dra7.dtsi
+++
The omap needs a DMA request pending right away. If it is enqueued once
the bytes are in the FIFO then nothing will happen and the FIFO will be
later purged via RX-timeout interrupt.
This patch requeues RX-DMA request on completion but not if it was
canceled due to the RX-timeout.
Cc: Heikki
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
arch/arm/boot/dts/am33xx.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 4a4e02d..cdccbd6 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++
On 07/29/2014 08:58 PM, Sebastian Andrzej Siewior wrote:
diff --git a/drivers/dma/omap-dma.c b/drivers/dma/omap-dma.c
index b19f04f..81ede01 100644
--- a/drivers/dma/omap-dma.c
+++ b/drivers/dma/omap-dma.c
@@ -970,6 +970,12 @@ static int omap_dma_terminate_all(struct omap_chan *c)
Hi Ohad,
On 07/29/2014 06:00 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Tue, Jul 8, 2014 at 7:22 PM, Suman Anna s-a...@ti.com wrote:
A remote processor may need to load certain firmware sections into
internal memories (eg: RAM at L1 or L2 levels) for performance or
other reasons.
Can you
On Tue, 29 Jul 2014, Tony Lindgren wrote:
Hmm maybe different u-boot version then? I'm using
2014.04-1-g5f09f5b.
Are you using NFS root on 37xxevm or MMC root?
Using nfsroot and omap2plus_defconfig. My dmesg attached
in case it provides some clues. I don't have console=ttyO
here,
On Tue, Jul 29, 2014 at 12:51:45AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [140728 11:13]:
On Mon, Jul 28, 2014 at 12:57:39PM -0500, Michael Welling wrote:
On Mon, Jul 28, 2014 at 10:57:18AM -0500, Felipe Balbi wrote:
Basically it means what you said above: the
On Tue, 29 Jul 2014, Michael Welling wrote:
Today I enabled debugging in the core hub driver and found that
once the external HUB suspends, the root HUB suspends.
Naturally. You can prevent that by forcing the root hub to remain
active.
Once the root HUB suspends, it seems there is no way
Hello, Good Day.
I am Senator Ahmed Rufai Sani Yerima from Nigeria. I will like to send my
daughter - AMINA to your country for investment, if you could advise me on any
profitable investment outlook in your country. Due to my political position
here in Nigeria, I am afraid something bad
Hi Grygorii and Grant,
On Monday 28 July 2014 23:52:34 Grant Likely wrote:
On Mon, Jul 28, 2014 at 11:47 AM, Grygorii Strashko wrote:
On 07/28/2014 05:05 PM, Grant Likely wrote:
On Thu, 12 Jun 2014 19:53:43 +0300, Grygorii Strashko wrote:
Use clkops-clocks property to specify clocks
Hi,
This is an updated version of the OMAP Mailbox framework adoption
DT support series, refreshed to work with the v9 version of the mailbox
framework [1] from Jassi Brar while also addressing some minor review
comments. Detailed changes are summarized below. Patches are based on
3.16-rc2.
The
The '#mbox-cells' property is added to all the OMAP mailbox
nodes. This property is mandatory with the new mailbox framework.
Cc: Benoît Cousson bcous...@baylibre.com
Cc: Rob Herring robh...@kernel.org
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Ian Campbell
The sub-mailbox devices are added to the Mailbox DT nodes on
OMAP2420, OMAP2430, OMAP3, AM33xx, AM43xx, OMAP4 and OMAP5
family of SoCs. This data represents the same mailboxes that
used to be represented in hwmod attribute data previously.
The node name is chosen based on the .name field of
The OMAP mailbox driver and its existing clients (remoteproc
for OMAP4+) are adapted to use the generic mailbox framework.
No changes are done to OMAP3 TI DSP/Bridge driver as it is being
deleted.
The main changes for the adaptation are:
- The tasklet used for Tx is replaced with the state
Logic has been added to the OMAP2+ mailbox code to parse the
mailbox dt nodes and construct the different sub-mailboxes
associated with the instance. The DT representation of the
sub-mailbox devices is different from legacy platform data
representation to allow flexibility of interrupt
Add the device tree bindings document for OMAP2+ mailbox.
Cc: Rob Herring robh...@kernel.org
Cc: Pawel Moll pawel.m...@arm.com
Cc: Mark Rutland mark.rutl...@arm.com
Cc: Ian Campbell ijc+devicet...@hellion.org.uk
Cc: Kumar Gala ga...@codeaurora.org
Signed-off-by: Suman Anna s-a...@ti.com
---
* Paul Walmsley p...@pwsan.com [140729 12:39]:
On Tue, 29 Jul 2014, Tony Lindgren wrote:
Hmm maybe different u-boot version then? I'm using
2014.04-1-g5f09f5b.
Are you using NFS root on 37xxevm or MMC root?
Using nfsroot and omap2plus_defconfig. My dmesg attached
in case
On 07/29/2014 07:12 PM, Mike Turquette wrote:
Oh yea, seems this got lost into the myriad of branches I have. I can push
this on top of my for-v3.17/ti-clk-drv if you like.
That is the easiest thing for me. I think that Peter wanted to take
this as a fix for 3.16 though. Peter is that
69 matches
Mail list logo
