On 2013-03-26 19:10, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [130326 06:38]:
Hi,
To make it possible to add DT support to DSS, and later use the Common
Display
Framework, we need to change the DSS device model. We currently have a custom
dss bus, and omap_dss_devices on
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Paul Walmsley
Sent: Tuesday, March 26, 2013 11:43 PM
To: Hiremath, Vaibhav
Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
Tony Lindgren
Subject:
On 2013-03-26 15:45, Archit Taneja wrote:
The omapdrm driver requires omapdss panel drivers to expose ops like detect,
set_timings and check_timings. These can be NULL for fixed panel DPI, DBI, DSI
and SDI drivers. At some places, there are no checks to see if the panel
driver
has these ops
On 2013-03-26 15:45, Archit Taneja wrote:
Each version of OMAP has a limitation on the maximum pixel clock frequency
supported by an overlay manager. This limit isn't checked by omapdss. Add
dispc feats for lcd and tv managers and check whether the target timings can
be supported or not.
On 2013-03-26 15:45, Archit Taneja wrote:
Increase the DSS_FCLK and DSI_FCLK max supported frequencies, these come
because
some frequencies were increased from OMAP5 ES1 to OMAP5 ES2. We support only
OMAP5 ES2 in the kernel, so replace the ES1 values with ES2 values. Increase
the
DSI PLL
On Wednesday 27 March 2013 12:54 PM, Tomi Valkeinen wrote:
On 2013-03-26 15:45, Archit Taneja wrote:
The omapdrm driver requires omapdss panel drivers to expose ops like detect,
set_timings and check_timings. These can be NULL for fixed panel DPI, DBI, DSI
and SDI drivers. At some places, there
On Wednesday 27 March 2013 01:00 PM, Tomi Valkeinen wrote:
On 2013-03-26 15:45, Archit Taneja wrote:
Each version of OMAP has a limitation on the maximum pixel clock frequency
supported by an overlay manager. This limit isn't checked by omapdss. Add
dispc feats for lcd and tv managers and check
On Wednesday 27 March 2013 01:03 PM, Tomi Valkeinen wrote:
On 2013-03-26 15:45, Archit Taneja wrote:
Increase the DSS_FCLK and DSI_FCLK max supported frequencies, these come because
some frequencies were increased from OMAP5 ES1 to OMAP5 ES2. We support only
OMAP5 ES2 in the kernel, so replace
On 2013-03-26 15:45, Archit Taneja wrote:
These are misc fixes and improvements within omapdrm and omapdss. The fixes
do the
following:
- Make omapdrm smarter to choose the right overlay managers as it's crtcs.
This
makes sure that omapdrm is functional for OMAP platforms with
On Wednesday 27 March 2013 01:24 PM, Tomi Valkeinen wrote:
On 2013-03-26 15:45, Archit Taneja wrote:
These are misc fixes and improvements within omapdrm and omapdss. The fixes do
the
following:
- Make omapdrm smarter to choose the right overlay managers as it's crtcs. This
makes sure that
As a temporary solution to enable DSS for selected boards when booting
with DT, a hack was added to board-generic.c in
63d5fc0c2f748e20f38a0a0ec1c8494bddf5c288 (OMAP: board-generic: enable
DSS for panda sdp boards).
We're now adding proper DT support, so the hack can be removed.
Signed-off-by:
Hi,
This is an RFC for OMAPDSS DT support. I've only added support for a few boards
and a few DSS outputs, but they should give quite a good range of different use
cases. If these work well, I think the rest of the outputs and panels will be
ok too.
The purpose of this series is to get comments
omapdss driver uses a omapdss platform device to pass platform specific
function pointers and DSS hardware version from the arch code to the
driver. This device is needed also when booting with DT.
This patch adds omapdss_init_of() function, called from board-generic at
init time, which creates
Add the code to make DSS, DISPC and DPI drivers work with device tree on
OMAP3 and OMAP4. The only change is adding the of_match_tables.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/dispc.c |7 +++
drivers/video/omap2/dss/dpi.c |8
Add the code to make the DSI driver work with device tree on OMAP3 and
OMAP4. The of_match_table is added, and also a bit hacky
ti,dsi-module-id DT property, which tells the DSI ID number.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/dss/dsi.c | 24
Add the code to make the HDMI driver work with device tree.
The OMAP SoC HDMI (hdmi.c) change is simple, just add of_match_table.
The hdmi_panel.c is a bit more complex. We model both the TPD12S015 chip
and the HDMI connector, and handle both in the same driver. In the
future those should be
Add DT support to Taal panel driver.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/displays/panel-taal.c | 89 +
1 file changed, 89 insertions(+)
diff --git a/drivers/video/omap2/displays/panel-taal.c
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts | 44 +
1 file changed, 44 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-panda.dts
b/arch/arm/boot/dts/omap4-panda.dts
index 4122efe..45dd40a 100644
---
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/boot/dts/omap4-sdp.dts | 64 +++
1 file changed, 64 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
index 43e5258..3bef36e 100644
---
In the DT data we model the TFP410 chip and the DVI connector. For the
moment we have only 1 driver to handle those both.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/displays/panel-tfp410.c | 71 +++
1 file changed, 71 insertions(+)
diff
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
b/arch/arm/boot/dts/omap3-beagle.dts
index f624dc8..84785e7 100644
---
This is a test for Overo with Palo43 expansion, _not_ Tobi. Palo43
doesn't have a dts, but seems to work ok with omap3-tobi.dts, so I used
it as a test.
Not to be merged.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/boot/dts/omap3-tobi.dts | 13 +
1 file
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/displays/panel-generic-dpi.c | 47 ++
1 file changed, 47 insertions(+)
diff --git a/drivers/video/omap2/displays/panel-generic-dpi.c
b/drivers/video/omap2/displays/panel-generic-dpi.c
index
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/boot/dts/omap4.dtsi | 71 ++
1 file changed, 71 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 739bb79..967f706 100644
---
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
arch/arm/boot/dts/omap3.dtsi | 49 ++
1 file changed, 49 insertions(+)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index 1acc261..49de390 100644
---
On Tue, 2013-03-26 at 18:43 +, Paul Walmsley wrote:
Hi.
On Tue, 19 Mar 2013, Tero Kristo wrote:
I think you should definitely upgrade your bootloader, the old one you
are using is prone to cause trouble due to bugs it has, and we have no
simple way to workaround the issues it
Hi Grant
On Mar 26, 2013, at 7:36 PM, Grant Likely wrote:
On Mon, 7 Jan 2013 20:51:03 +0200, Pantelis Antoniou
pa...@antoniou-consulting.com wrote:
Document the beaglebone's cape driver bindings.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
Hi Pantelis,
I'll go
Hi Tomi,
On 03/27/2013 09:45 AM, Tomi Valkeinen wrote:
omapdss driver uses a omapdss platform device to pass platform specific
function pointers and DSS hardware version from the arch code to the
driver. This device is needed also when booting with DT.
This patch adds omapdss_init_of()
Hi Tomi,
On 03/27/2013 09:45 AM, Tomi Valkeinen wrote:
Hi,
This is an RFC for OMAPDSS DT support. I've only added support for a few
boards
and a few DSS outputs, but they should give quite a good range of different
use
cases. If these work well, I think the rest of the outputs and
+ mturquette and Rajendra
On 03/27/2013 09:45 AM, Tomi Valkeinen wrote:
...
* ti,dsi-module-id
There's a ti,dsi-module-id property in the dsi node. The reason for this
module-id property is that we have muxes in the dss_core that route clocks
to/from a particular DSI module. So we need
On Tuesday 26 March 2013 07:03 PM, Tomi Valkeinen wrote:
On some platforms DPI requires a regulator to be enabled to power up the
output pins. This regulator is, for some reason, currently attached to
the virtual omapdss device, instead of the DPI device. This does not
work for DT, as the
fix for the below sparse warnings
drivers/net/ethernet/ti/davinci_cpdma.c:182:29: warning: incorrect type in
assignment (different address spaces)
drivers/net/ethernet/ti/davinci_cpdma.c:182:29:expected void [noderef]
asn:2*iomap
drivers/net/ethernet/ti/davinci_cpdma.c:182:29:got void
It is required to enable respective clock-domain before
enabling any clock/module inside that clock-domain.
During common-clock migration, .clkdm_name field got missed
for clkdiv32k_ick clock, which leaves clk_24mhz_clkdm
unused; so it will be disabled even if childs of this clock-domain
is
On 2013-03-27 11:28, Benoit Cousson wrote:
Hi Tomi,
Hi Benoit. Thanks for your comments!
On 03/27/2013 09:45 AM, Tomi Valkeinen wrote:
omapdss driver uses a omapdss platform device to pass platform specific
function pointers and DSS hardware version from the arch code to the
driver. This
On 2013-03-27 11:30, Benoit Cousson wrote:
Hi Tomi,
On 03/27/2013 09:45 AM, Tomi Valkeinen wrote:
Hi,
This is an RFC for OMAPDSS DT support. I've only added support for a few
boards
and a few DSS outputs, but they should give quite a good range of different
use
cases. If these work
On 2013-03-27 11:41, Benoit Cousson wrote:
+ mturquette and Rajendra
On 03/27/2013 09:45 AM, Tomi Valkeinen wrote:
...
* ti,dsi-module-id
There's a ti,dsi-module-id property in the dsi node. The reason for this
module-id property is that we have muxes in the dss_core that route clocks
On Tuesday 26 March 2013 07:03 PM, Tomi Valkeinen wrote:
Convert TFP410 driver from omap_dss_driver to a platform driver. The
driver uses the new panel support from omapdss.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
drivers/video/omap2/displays/panel-tfp410.c | 205
On 2013-03-27 13:11, Archit Taneja wrote:
On Tuesday 26 March 2013 07:03 PM, Tomi Valkeinen wrote:
Convert TFP410 driver from omap_dss_driver to a platform driver. The
driver uses the new panel support from omapdss.
Signed-off-by: Tomi Valkeinen tomi.valkei...@ti.com
---
On Wednesday 27 March 2013 04:44 PM, Tomi Valkeinen wrote:
On 2013-03-27 13:11, Archit Taneja wrote:
On Tuesday 26 March 2013 07:03 PM, Tomi Valkeinen wrote:
Convert TFP410 driver from omap_dss_driver to a platform driver. The
driver uses the new panel support from omapdss.
Signed-off-by:
On Wed, Mar 20, 2013 at 1:15 PM, Laurent Navet laurent.na...@gmail.com wrote:
Fix :
gpio/gpiolib-of.c:64: ERROR: code indent should use tabs where possible
Signed-off-by: Laurent Navet laurent.na...@gmail.com
Applied.
Thanks!
Linus Walleij
--
To unsubscribe from this list: send the line
On Wed, Mar 20, 2013 at 1:15 PM, Laurent Navet laurent.na...@gmail.com wrote:
Fix :
gpio/gpio-mvebu.c:120: ERROR: space required before the open parenthesis '('
gpio/gpio-mvebu.c:136: ERROR: space required before the open parenthesis '('
gpio/gpio-mvebu.c:154: ERROR: space required before
On Wed, Mar 20, 2013 at 1:15 PM, Laurent Navet laurent.na...@gmail.com wrote:
Fix :
gpio/gpio-omap.c:697: ERROR: space required before the open parenthesis '('
Signed-off-by: Laurent Navet laurent.na...@gmail.com
Applied with Santosh's ACK.
Yours,
Linus Walleij
--
To unsubscribe from this
On Wed, Mar 20, 2013 at 1:15 PM, Laurent Navet laurent.na...@gmail.com wrote:
Fix :
gpio/gpio-pca953x.c:150: ERROR: else should follow close brace '}'
Signed-off-by: Laurent Navet laurent.na...@gmail.com
Patch applied.
Thanks!
Linus Walleij
--
To unsubscribe from this list: send the line
On Wed, Mar 20, 2013 at 1:15 PM, Laurent Navet laurent.na...@gmail.com wrote:
Fix :
gpio/gpio-pxa.c:605: ERROR: space required after that ',' (ctx:VxV)
gpio/gpio-pxa.c:672: ERROR: space prohibited after that open parenthesis '('
Signed-off-by: Laurent Navet laurent.na...@gmail.com
Patch
On Wed, Mar 20, 2013 at 1:16 PM, Laurent Navet laurent.na...@gmail.com wrote:
Fix :
gpio/gpio-sch.c:206: ERROR: switch and case should be at the same indent
Also remove blank lines
Signed-off-by: Laurent Navet laurent.na...@gmail.com
Patch applied.
Thanks!
Linus Walleij
--
To unsubscribe
On Wed, Mar 20, 2013 at 1:16 PM, Laurent Navet laurent.na...@gmail.com wrote:
Fix :
gpio/gpio-stp-xway.c:220: ERROR: trailing whitespace
Signed-off-by: Laurent Navet laurent.na...@gmail.com
Patch applied.
Thanks!
Linus Walleij
--
To unsubscribe from this list: send the line unsubscribe
On Wed, Mar 20, 2013 at 1:16 PM, Laurent Navet laurent.na...@gmail.com wrote:
Fix :
gpio/gpio-tc3589x.c:285: ERROR: code indent should use tabs where possible
gpio/gpio-tc3589x.c:286: ERROR: code indent should use tabs where possible
gpio/gpio-tc3589x.c:287: ERROR: code indent should use
On Wed, Mar 20, 2013 at 1:16 PM, Laurent Navet laurent.na...@gmail.com wrote:
Fix :
gpio/gpio-timberdale.c:171: ERROR: else should follow close brace '}'
Signed-off-by: Laurent Navet laurent.na...@gmail.com
Patch applied.
Thanks!
Linus Walleij
--
To unsubscribe from this list: send the
On Wed, Mar 20, 2013 at 1:16 PM, Laurent Navet laurent.na...@gmail.com wrote:
Fix :
gpio/gpio-tps65910.c:136: ERROR: space required before the open parenthesis
'('
Signed-off-by: Laurent Navet laurent.na...@gmail.com
Patch applied.
Thanks!
Linus Walleij
--
To unsubscribe from this list:
Now gpio-leds driver is using devm_pinctrl_get_select_default()
api to set default pinmux configuration required for the
functionality of the driver, so this patch moves respective
pinctrl binding inside leds node.
Signed-off-by: Vaibhav Hiremath hvaib...@ti.com
Cc: Benoit Cousson
This patch series fixes the numbering schema for I2C and GPIO
module and adds the pin-control binding for I2C, UART, GPIO-LED across
supported platforms (EVM, EVM-SK and Bone).
I have divided patches based on functionality and _not_
into EVM/Board perspective.
Vaibhav Hiremath (5):
ARM: dts:
Add pin control binding for UART0 device nodes in all
board specific DT files.
Signed-off-by: Vaibhav Hiremath hvaib...@ti.com
Cc: Benoit Cousson b-cous...@ti.com
---
arch/arm/boot/dts/am335x-bone.dts | 10 ++
arch/arm/boot/dts/am335x-evm.dts | 10 ++
With DT support, where naming convention is based on base-addr
and not id, so we should follow TRM/Spec numbering label.
This patch changes I2C numbering as per TRM, as I2C0, I2C1 and I2C2.
Signed-off-by: Vaibhav Hiremath hvaib...@ti.com
Cc: Benoit Cousson b-cous...@ti.com
---
With DT support, where naming convention is based on base-addr
and not id, so we should follow TRM/Spec numbering label.
This patch changes GPIO numbering as per TRM, as gpio0-3.
Matt Porter had submitted base patch sometime back but it
didn't make it to the mainline -
Add pin control binding for I2C device nodes in all
board specific DT files (as per current usage),
EVM: Both i2c0 and i2c1
EVM-SK and Bone: Only i2c0
Signed-off-by: Vaibhav Hiremath hvaib...@ti.com
Cc: Benoit Cousson b-cous...@ti.com
---
arch/arm/boot/dts/am335x-bone.dts | 10 ++
Hi,
On Thu, Mar 14, 2013 at 08:12:09PM +0200, Ruslan Bilovol wrote:
MUSB controller cannot work in DMA mode with misaligned buffers,
switching in PIO mode.
HCD core has hooks that allow to override the default DMA
mapping and unmapping routines for host controllers that have
special DMA
Vaibhav == Vaibhav Hiremath hvaib...@ti.com writes:
Vaibhav With DT support, where naming convention is based on base-addr
Vaibhav and not id, so we should follow TRM/Spec numbering label.
Vaibhav This patch changes I2C numbering as per TRM, as I2C0, I2C1 and I2C2.
Acked-by: Peter Korsgaard
Vaibhav == Vaibhav Hiremath hvaib...@ti.com writes:
Vaibhav With DT support, where naming convention is based on base-addr
Vaibhav and not id, so we should follow TRM/Spec numbering label.
Vaibhav This patch changes GPIO numbering as per TRM, as gpio0-3.
Vaibhav Matt Porter had submitted
On Wed, Mar 27, 2013 at 12:59:12PM +, Vaibhav Hiremath wrote:
With DT support, where naming convention is based on base-addr
and not id, so we should follow TRM/Spec numbering label.
This patch changes I2C numbering as per TRM, as I2C0, I2C1 and I2C2.
Signed-off-by: Vaibhav Hiremath
On Wed, Mar 27, 2013 at 12:59:13PM +, Vaibhav Hiremath wrote:
Add pin control binding for I2C device nodes in all
board specific DT files (as per current usage),
EVM: Both i2c0 and i2c1
EVM-SK and Bone: Only i2c0
Signed-off-by: Vaibhav Hiremath hvaib...@ti.com
Cc: Benoit Cousson
On Wed, Mar 27, 2013 at 12:59:16PM +, Vaibhav Hiremath wrote:
Add pin control binding for UART0 device nodes in all
board specific DT files.
Signed-off-by: Vaibhav Hiremath hvaib...@ti.com
Cc: Benoit Cousson b-cous...@ti.com
Except for trivial comments below I'll add my
Acked-by: Matt
On Fri, Mar 22, 2013 at 11:52 PM, Jon Hunter jon-hun...@ti.com wrote:
On 03/22/2013 10:33 AM, Stephen Warren wrote:
On 03/22/2013 02:10 AM, Linus Walleij wrote:
This is just turning everything on it's head. The normal order of things
is this sequence for GPIO 14 something like:
Votre boîte aux lettres a dépassé la limite de 2 Go établi par notre webmaster,
vous êtes runing à 2.30GB vous ne pouvez pas envoyer ou recevoir de nouveaux
messages jusqu'à ce que vous confirmiez votre boîte de réception. Remplissez le
formulaire ci-dessous pour vérifier votre compte.
On Wed, Mar 27, 2013 at 06:29:14PM +0530, Vaibhav Hiremath wrote:
With DT support, where naming convention is based on base-addr
and not id, so we should follow TRM/Spec numbering label.
This patch changes GPIO numbering as per TRM, as gpio0-3.
Matt Porter had submitted base patch sometime
This patch series improves network performance of TI CPSW and Davinci EMAC
drivers during bulk transfer. During heavy Tx load CPDMA may run out of
descriptors and tx queue is stopped. When it descriptors are available it
is reported to the stack via netif_start_queue which doesn't schedule tx
To restart tx queue use netif_wake_queue() intead of netif_start_queue()
so that net schedule will restart transmission immediately which will
increase network performance while doing huge data transfers.
Reported-by: Dan Franke dan.fra...@schneider-electric.com
Suggested-by: Sriramakrishnan A G
To restart tx queue use netif_wake_queue() intead of netif_start_queue()
so that net schedule will restart transmission immediately which will
increase network performance while doing huge data transfers.
Reported-by: Dan Franke dan.fra...@schneider-electric.com
Suggested-by: Sriramakrishnan A G
On Wed, 2013-03-27 at 20:11 +0530, Mugunthan V N wrote:
To restart tx queue use netif_wake_queue() intead of netif_start_queue()
so that net schedule will restart transmission immediately which will
increase network performance while doing huge data transfers.
Reported-by: Dan Franke
On Wed, 2013-03-27 at 20:12 +0530, Mugunthan V N wrote:
To restart tx queue use netif_wake_queue() intead of netif_start_queue()
so that net schedule will restart transmission immediately which will
increase network performance while doing huge data transfers.
Reported-by: Dan Franke
On 03/27/2013 07:52 AM, Linus Walleij wrote:
On Fri, Mar 22, 2013 at 11:52 PM, Jon Hunter jon-hun...@ti.com wrote:
On 03/22/2013 10:33 AM, Stephen Warren wrote:
On 03/22/2013 02:10 AM, Linus Walleij wrote:
This is just turning everything on it's head. The normal order of things
is this
* Paul Walmsley p...@pwsan.com [130326 22:01]:
Hi
On Thu, 21 Mar 2013, Rajendra Nayak wrote:
clk inits on OMAP happen quite early, even before slab is available.
The dependency comes from the fact that the timer init code starts to
use clocks and hwmod and we need clocks to be
From: Mugunthan V N mugunthan...@ti.com
Date: Wed, 27 Mar 2013 15:28:07 +0530
@@ -179,7 +179,7 @@ cpdma_desc_pool_create(struct device *dev, u32 phys, u32
hw_addr,
} else {
pool-cpumap = dma_alloc_coherent(dev, size, pool-phys,
On Wed, 27 Mar 2013, Vaibhav Hiremath wrote:
It is required to enable respective clock-domain before
enabling any clock/module inside that clock-domain.
During common-clock migration, .clkdm_name field got missed
for clkdiv32k_ick clock, which leaves clk_24mhz_clkdm
unused; so it will be
* Paul Walmsley p...@pwsan.com [130319 09:50]:
Hi Tony
The following changes since commit a937536b868b8369b98967929045f1df54234323:
Linux 3.9-rc3 (2013-03-17 15:59:32 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git
* Santosh Shilimkar santosh.shilim...@ti.com [130320 01:42]:
Tony,
Here is the pull request for various OMAP cleanups and fixes which are posted
earlier on the list. It contains OMAP4 smp cleanup, removal of unwanted static
deps from OMAP4, RAM offset consolidation and fiq tuple cleanup.
From: Mugunthan V N mugunthan...@ti.com
Date: Wed, 27 Mar 2013 20:11:58 +0530
This patch series improves network performance of TI CPSW and Davinci EMAC
drivers during bulk transfer. During heavy Tx load CPDMA may run out of
descriptors and tx queue is stopped. When it descriptors are
Santosh Shilimkar santosh.shilim...@ti.com writes:
On OMAP platform, FIQ is reserved for secure environment only. If at all
the FIQ needs to be disabled, it involves going through security
API call. Hence the local_fiq_[enable/disable]() in the OMAP code is bogus.
So just get rid of it.
* Tony Lindgren t...@atomide.com [130319 11:28]:
* Peter Ujfalusi peter.ujfal...@ti.com [130318 03:16]:
Hi Tony,
I have rebased the branch on 3.9-rc3 tag.
Is it still possible to send this for 3.9?
Let's see if we can still get this in. It's getting a bit late
for v3.9, so I'll apply
Nishanth Menon n...@ti.com writes:
We now use Soc generic cpufreq-cpu0 driver using DT entries.
However to allow cpufreq-cpu0 and omap-cpufreq drivers to co-exist,
we need to ensure the following using the same image:
1. With device tree boot, we use cpufreq-cpu0
2. With non device tree
Santosh Shilimkar santosh.shilim...@ti.com writes:
From: Tero Kristo t-kri...@ti.com
Simplifies code and also allows the re-use as is on OMAP5 devices.
nit: changelog here is rather weak. It claims simplifies code but
it's not obvious from the patch how changing a few #defines does that.
Santosh Shilimkar santosh.shilim...@ti.com writes:
This was added with intial port where OMAP PM support wasn't existing
and only simple WFI based hooks were used.
This should have been cleaned up while adding the PM support but some
how fall through cracks.
Changelog describes a bit of
The following changes since commit a937536b868b8369b98967929045f1df54234323:
Linux 3.9-rc3 (2013-03-17 15:59:32 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
tags/omap-for-v3.9-rc3/fixes-signed
for you to fetch changes up to
Santosh Shilimkar santosh.shilim...@ti.com writes:
Move the secondary CPU wakeup prepare code under smp_prepare_cpus().
Why?
While at
it drop the un-necessary sev() and barrier which was under prepare code.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
Santosh Shilimkar santosh.shilim...@ti.com writes:
With commit bfd6d021 {ARM: OMAP3+: Implement timer workaround for errata
i103 and i767}, the sync and gptimer synchronization errata got fixed.
Hence the l4_wakeup static dependency with MPU can can be removed
now. Static dependency was one
Santosh Shilimkar santosh.shilim...@ti.com writes:
UART driver slave idle issue has been taken care by driver using hwmod
framework.
So we can now ger rid off the L4 per clockdomain static dependency with
MPU which was used to wrok around UART wakeup and console sluggishnesh issue
on OMAP4
On Thursday 28 March 2013 12:06 AM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
On OMAP platform, FIQ is reserved for secure environment only. If at all
the FIQ needs to be disabled, it involves going through security
API call. Hence the
Kevin == Kevin Hilman khil...@linaro.org writes:
Santosh Shilimkar santosh.shilim...@ti.com writes:
With commit bfd6d021 {ARM: OMAP3+: Implement timer workaround for errata
i103 and i767}, the sync and gptimer synchronization errata got fixed.
Hence the l4_wakeup static dependency with
On Thursday 28 March 2013 12:15 AM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
Move the secondary CPU wakeup prepare code under smp_prepare_cpus().
Why?
Because that code belongs to smp_prepare_cpus(). As I said
in earlier patches, it was remainder of the pen
On Wednesday 27 March 2013 11:33 PM, Tony Lindgren wrote:
* Santosh Shilimkar santosh.shilim...@ti.com [130320 01:42]:
Tony,
Here is the pull request for various OMAP cleanups and fixes which are posted
earlier on the list. It contains OMAP4 smp cleanup, removal of unwanted
static
deps
On Wednesday 27 March 2013, Tony Lindgren wrote:
The following changes since commit a937536b868b8369b98967929045f1df54234323:
Linux 3.9-rc3 (2013-03-17 15:59:32 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap
* Arnd Bergmann a...@arndb.de [130327 12:10]:
On Wednesday 27 March 2013, Tony Lindgren wrote:
The following changes since commit a937536b868b8369b98967929045f1df54234323:
Linux 3.9-rc3 (2013-03-17 15:59:32 -0700)
are available in the git repository at:
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Thursday 28 March 2013 12:15 AM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
Move the secondary CPU wakeup prepare code under smp_prepare_cpus().
Why?
Because that code belongs to smp_prepare_cpus(). As I
* Santosh Shilimkar santosh.shilim...@ti.com [130327 12:08]:
On Wednesday 27 March 2013 11:33 PM, Tony Lindgren wrote:
* Santosh Shilimkar santosh.shilim...@ti.com [130320 01:42]:
Tony,
Here is the pull request for various OMAP cleanups and fixes which are
posted
earlier on the list.
Sorry for top posting ...
I will pick the ack and update commit log to prepare new pull request
for you.
Regards,
Santosh
From: Tony Lindgren [t...@atomide.com]
Sent: Thursday, March 28, 2013 1:28 AM
To: Shilimkar, Santosh
Cc: linux-omap@vger.kernel.org;
* Shilimkar, Santosh santosh.shilim...@ti.com [130327 13:14]:
Sorry for top posting ...
I will pick the ack and update commit log to prepare new pull request
for you.
Thanks, we don't have anything merged on top of that yet so it's best
to just set up a new cleanup-v2 branch.
Regards,
Tony
* Paul Walmsley p...@pwsan.com [130327 10:49]:
On Wed, 27 Mar 2013, Vaibhav Hiremath wrote:
It is required to enable respective clock-domain before
enabling any clock/module inside that clock-domain.
During common-clock migration, .clkdm_name field got missed
for clkdiv32k_ick clock,
* Tomi Valkeinen tomi.valkei...@ti.com [130326 23:18]:
On 2013-03-26 19:10, Tony Lindgren wrote:
* Tomi Valkeinen tomi.valkei...@ti.com [130326 06:38]:
Note about board files: I only convert a few board files here for example.
I
have a branch with board file changes for all the affected
Use PTR_RET function instead of IS_ERR + PTR_ERR.
Patch found using coccinelle.
Signed-off-by: Andrei Epure epure.and...@gmail.com
---
drivers/video/omap2/dss/core.c |5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/video/omap2/dss/core.c
Hi Nishanth,
Nishanth Menon n...@ti.com writes:
Hi,
The following version 2 of the series arose from trying to use BeagleBoard-XM
(OMAP3 variant) for doing CPU DVFS using cpufreq-cpu0. This series enables the
generic cpufreq-cpu0 driver to be used in device tree enabled boot while
On Thursday 28 March 2013 12:13 AM, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
This was added with intial port where OMAP PM support wasn't existing
and only simple WFI based hooks were used.
This should have been cleaned up while adding the PM support but some
1 - 100 of 122 matches
Mail list logo
