Add DSS hwmod struct for AM43x SOC.
Signed-off-by: Sathya Prakash M R sath...@ti.com
---
This is based on below patch series which is yet to be merged
http://permalink.gmane.org/gmane.linux.ports.arm.omap/100892
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 85
DSS support for AM437x is added in this patch series.
Patch #1 adds the hwmod entries and
patch #2 adds the DT entry.
Sathya Prakash M R (2):
ARM: OMAP2+: AM43x - Add DSS hwmod
ARM: DTS: AM43x: Add DSS node
arch/arm/boot/dts/am4372.dtsi | 27 +
Add device node for DSS module for AM43x
Signed-off-by: Sathya Prakash M R sath...@ti.com
---
arch/arm/boot/dts/am4372.dtsi | 27 +++
1 file changed, 27 insertions(+)
diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi
index ddc1df7..f10fc0a
Hi,
On Monday 22 July 2013 12:52 AM, Alan Stern wrote:
On Sun, 21 Jul 2013, Sylwester Nawrocki wrote:
What's wrong with the platform_data structure, why can't that be used
for this?
At the point the platform data of some driver is initialized, e.g. in
board setup code the PHY pointer is
Urgent info
Your email I'd picked 1,000,000.00 euros. These are your draw numbers;
85,49,73,64,95,84,99,11.
contact Mrs Elena Beyer:Email micro.s...@aol.com, Call: 0034602480047
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
Hi,
On 07/22/2013 11:17 AM, 菲 徐 wrote:
Hi all:
I met a problem about USB Ethernet on panda board with kernel 3.10 . USB
Ethernet can be detected when device tree enabled but failed to connect to
network.
We don't yet support USB Host on panda with DT boot on 3.10. It should work
with
On 07/20/2013 07:42 AM, NAVEEN KRISHNA CHATRADHI wrote:
Hello Sebastian,
Hello Naveen,
I just did one more testing.
In case of iio/adc/exynos_adc.c there is a bug in the remove path.
If I fix the bug in the driver, with below patch
--- a/drivers/iio/adc/exynos_adc.c
+++
Hi,
Please don't drop mailing list from cc.
On 07/22/2013 11:27 AM, xufei...@hotmail.com wrote:
Hi roger:
Do you mean it works from 3.11-rc2. But I've tested with 3.11-rc2, there
is the same problem.
Should I have to use 3.11-rc1 with your patch.
OK. In your earlier mail you
Hello Sebastian,
--- Original Message ---
Sender : Sebastian Andrzej Siewiorbige...@linutronix.de
Date : Jul 22, 2013 13:55 (GMT+05:30)
Title : Re: [PATCH] of: provide of_platform_unpopulate()
On 07/20/2013 07:42 AM, NAVEEN KRISHNA CHATRADHI wrote:
Hello Sebastian,
Hello Naveen,
Add support to show CPSW hardware statistics to user via ethtool
so user can find if there were any error reported by hardware or
the system is over loaded duing high data rate transfer.
Signed-off-by: Mugunthan V N mugunthan...@ti.com
---
drivers/net/ethernet/ti/cpsw.c | 202
Hi Jonathan,
On Sat, Jul 20, 2013 at 1:43 PM, Jonathan Cameron ji...@kernel.org wrote:
On 07/19/2013 10:27 AM, Oleksandr Kozaruk wrote:
The GPADC is general purpose ADC found on TWL6030, and TWL6032 PMIC,
known also as Phoenix and PhoenixLite.
The TWL6030 and TWL6032 have GPADC with 17 and
Hi,
I observe the following problem on booting v3.11-rc1 on OMAP3 beagle board.
[5.888946] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM
[5.896057] Modules linked in:
[5.899322] CPU: 0 PID: 9 Comm: rcu_sched Not tainted
3.11.0-rc2-1-g1ea701a #876
[5.907501]
On 08/07/13 17:21, Russell King - ARM Linux wrote:
Also looks like the nonfunctional video stuff is even more nonfunctional
than usual:
omapdss DSI error: can't get VDDS_DSI regulator
omapdss HDMI error: can't get VDDA_HDMI_DAC regulator
Those should be followed by ...requests probe
Em 22-07-2013 02:32, Paul Walmsley escreveu:
On Sun, 21 Jul 2013, Joe Perches wrote:
I certainly don't object at all if Andrew picks
up the patches you mentioned and drops these 2.
Andrew, here are links to Cesar's original patches
Boot on all OMAP2+ devices is broken with earlycon enabled
as discussed here [1]
There were 2 issues which were rootcaused
1. Issue caused due to hwmod doing a reset of console uart while
earlycon was using it (seen only on am335x devices)
2. omap serial causing a NULL context restore with
Memory controllers in OMAP (like GPMC and EMIF) have the hwmods marked with
HWMOD_INIT_NO_IDLE and are left in enabled state post initial setup.
Even if they have drivers missing, avoid idling them as part of
omap_device_late_idle()
Signed-off-by: Rajendra Nayak rna...@ti.com
---
Some hwmods which are marked with HWMOD_INIT_NO_IDLE are left in enabled
state post setup(). When a omap_device gets created for such hwmods
make sure the omap_device and pm_runtime states are also in sync for such
hwmods by doing a omap_device_enable() and pm_runtime_set_active() for the
device.
With commit '82702ea11ddfe0e43382e1fa5b66d807d8114916' ARM: OMAP2+:
Fix serial init for device tree based booting stubbing out
omap_serial_early_init()
for Device tree based booting, there was a crash observed on AM335x based
devices
when hwmod does a _setup_reset() early at boot.
This was
From: Grygorii Strashko grygorii.stras...@ti.com
If earlyprintk is enabled and current UART is console port the platform
code can mark it as RPM_ACTIVE to sync real IP state with PM Runtime and
avoid resuming of already active device, but now, driver initialization
will be performed in the wrong
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: linux-omap@vger.kernel.org
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/boot/dts/omap2420-h4.dts | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/omap2420-h4.dts
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: linux-omap@vger.kernel.org
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/boot/dts/omap4.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap4.dtsi
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: linux-omap@vger.kernel.org
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/boot/dts/omap3.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: linux-omap@vger.kernel.org
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/boot/dts/omap3-igep0020.dts | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: linux-omap@vger.kernel.org
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/boot/dts/omap3430-sdp.dts | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: linux-omap@vger.kernel.org
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/boot/dts/omap5.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/omap5.dtsi
Cc: Benoît Cousson b-cous...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: linux-omap@vger.kernel.org
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/boot/dts/omap3-igep0030.dts | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Hi Linus,
On Sunday 21 July 2013 10:19 PM, Linus Walleij wrote:
On Thu, Jul 18, 2013 at 8:56 PM, Nishanth Menon n...@ti.com wrote:
I carry forward my TI internal objection to this approach:
It is actually a very good sign of FOSS-maturity that you as a company
take unresolved architectural
On Friday 19 July 2013 10:01 PM, Nishanth Menon wrote:
On 07/19/2013 11:24 AM, Sourav Poddar wrote:
These series add support for I2C/MCSPI/UART pin control datas.
The series is done on top of Rajendra Nayak series[1](posted to the
list),
which has basic dt boot enable for dra7.
These patches
GPADC is the general purpose ADC present on twl6030.
The dt data is interrupt used to trigger end of ADC
conversion.
Signed-off-by: Oleksandr Kozaruk oleksandr.koza...@ti.com
---
arch/arm/boot/dts/twl6030.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git
The GPADC is general purpose ADC found on TWL6030, and TWL6032 PMIC,
known also as Phoenix and PhoenixLite.
The TWL6030 and TWL6032 have GPADC with 17 and 19 channels
respectively. Some channels have current source and are used for
measuring voltage drop on resistive load for detecting battery ID
Hello,
v7 - addressed clean up comments, removed test channels
v6 - addressed comments about trim bits, checkpatch clean up
v5 - gpadc DT node renamed from gpadc to generic adc, added
temperature channels; raw code is corracted with calibration
data.
v4 - addressed comments: fixed style
Hi Alan,
On 07/11/2013 06:14 PM, Alan Stern wrote:
On Thu, 11 Jul 2013, Roger Quadros wrote:
The other two problems are both related to the interaction between
system PM and runtime PM. Suppose the controller is already runtime
suspended when the system goes to sleep. Because it is
Hello.
On 22-07-2013 9:29, Paul Walmsley wrote:
From: Lokesh Vutla lokeshvu...@ti.com
On 37xx EVM non-dt boot fails with current mainline,
because of broken GPIO numbering in the board file
that uses hardcoded GPIOs.
So marking omap3_evm_display_init() with CONFIG_BROKEN
for now as
On Sunday 21 July 2013 07:10 AM, Linus Walleij wrote:
On Sun, Jul 21, 2013 at 6:54 AM, Javier Martinez Canillas
martinez.jav...@gmail.com wrote:
Linus, are you still planing to send this patches as fixes for the
v3.11 -rc cycle or did you decide to wait for v3.12?
It will go into the
On Mon, Jul 22, 2013 at 12:55:18PM +0530, Kishon Vijay Abraham I wrote:
The issue (or one of the issues) in this discussion is that
Greg does not like the idea of using names or IDs to associate
PHYs with controllers, because they are too prone to
duplications or other
On 22/07/13 11:01, Rajendra Nayak wrote:
Boot on all OMAP2+ devices is broken with earlycon enabled
as discussed here [1]
There were 2 issues which were rootcaused
1. Issue caused due to hwmod doing a reset of console uart while
earlycon was using it (seen only on am335x devices)
2. omap
On Mon, 22 Jul 2013, Kishon Vijay Abraham I wrote:
The PHY and the controller it is attached to are both physical
devices.
The connection between them is hardwired by the system
manufacturer and cannot be changed by software.
PHYs are generally described by
On Mon, 22 Jul 2013, Roger Quadros wrote:
Right, I understand it now. How does the below code look?
+static int omap_ehci_suspend(struct device *dev)
+{
+ struct usb_hcd *hcd = dev_get_drvdata(dev);
+ bool do_wakeup = device_may_wakeup(dev);
+ int ret;
+
+
On Monday 22 July 2013 08:20 AM, Sricharan R wrote:
Hi Linus,
On Sunday 21 July 2013 10:19 PM, Linus Walleij wrote:
On Thu, Jul 18, 2013 at 8:56 PM, Nishanth Menon n...@ti.com wrote:
I carry forward my TI internal objection to this approach:
It is actually a very good sign of FOSS-maturity
Hi Nishanth,
On Fri, Jul 19, 2013 at 5:10 PM, Nishanth Menon n...@ti.com wrote:
On 07/19/2013 07:10 AM, Ruslan Bilovol wrote:
The OMAP4 SoC family uses specially-designed
PMIC (power management IC) companion chip for power
management needs: TWL6030/TWL6032.
Therefore there is a typical
On Mon, 22 Jul 2013, Roger Quadros wrote:
I observe the following problem on booting v3.11-rc1 on OMAP3 beagle board.
[5.888946] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM
[5.896057] Modules linked in:
[5.899322] CPU: 0 PID: 9 Comm: rcu_sched Not tainted
Also CCing correct devicetree list that was changed recently
On Mon, Jul 22, 2013 at 7:24 PM, Ruslan Bilovol ruslan.bilo...@ti.com wrote:
Hi Nishanth,
On Fri, Jul 19, 2013 at 5:10 PM, Nishanth Menon n...@ti.com wrote:
On 07/19/2013 07:10 AM, Ruslan Bilovol wrote:
The OMAP4 SoC family uses
Hi,
On 07/19/2013 04:26 PM, Felipe Balbi wrote:
Hi,
[...]
please don't remove this code. It'll be good to have this around when we
move the driver to threaded IRQs without IRQF_ONESHOT. In fact, it would
be very simple to implement such a change, wanna take it up ?
It should be doable in few
On Mon, 2013-07-22 at 14:07 +0530, Mugunthan V N wrote:
Add support to show CPSW hardware statistics to user via ethtool
so user can find if there were any error reported by hardware or
the system is over loaded duing high data rate transfer.
Signed-off-by: Mugunthan V N mugunthan...@ti.com
Hi
On Mon, 22 Jul 2013, Rajendra Nayak wrote:
Memory controllers in OMAP (like GPMC and EMIF) have the hwmods marked with
HWMOD_INIT_NO_IDLE and are left in enabled state post initial setup.
Even if they have drivers missing, avoid idling them as part of
omap_device_late_idle()
Since this
HWMOD removal for MMC is breaking edma_start as the events are being manually
triggered due to unused channel list not being clear, Thanks to Balaji TK for
finding this issue.
This patch fixes the issue, by reading the dmas property from the DT node if
it exists and clearing the bits in the
HWMOD removal for MMC is breaking edma_start as the events are being manually
triggered due to unused channel list not being clear, Thanks to Balaji TK for
finding this issue.
This patch fixes the issue, by reading the dmas property from the DT node if
it exists and clearing the bits in the
Hi,
After Linus's commit fb2af0020a51709ad87ea8055c325d3fbde04158 (Merge
branch 'for-linus' of git://git.linaro.org/people/rmk/linux-arm), the
OMAP2430 SDP here stopped booting.
Here's the bootlog at the commit before the merge, commit 790eac5640:
On Mon, Jul 22, 2013 at 06:07:47PM +, Paul Walmsley wrote:
After Linus's commit fb2af0020a51709ad87ea8055c325d3fbde04158 (Merge
branch 'for-linus' of git://git.linaro.org/people/rmk/linux-arm), the
OMAP2430 SDP here stopped booting.
Here's the bootlog at the commit before the merge,
On Mon, 22 Jul 2013, Russell King - ARM Linux wrote:
Bear in mind that I'm almost at the point of not boot-testing anything
I sent to Linus because of the uselessness of the SDP4430 board now
that it's DT only - the only platform which boot-tests anything I send
is the 3430LDP board now. If
On Wed, Jul 10, 2013 at 2:24 PM, Tony Lindgren t...@atomide.com wrote:
How about I'll push an immutable branch against v3.11-rc1 when it's
tagged and send a pull request to Linus W for the first three patches?
That way we can base other branches on this if needed.
Linus, does that sound OK
On Fri, Jul 12, 2013 at 5:36 PM, Grygorii Strashko
grygorii.stras...@ti.com wrote:
On 07/10/2013 11:36 PM, Linus Walleij wrote:
I guess we need a patch set prepared which adds the active state
and helper function as the first patch, i.e. this:
Hi,
On Mon, Jul 22, 2013 at 08:25:05PM +0300, Illia Smyrnov wrote:
please don't remove this code. It'll be good to have this around when we
move the driver to threaded IRQs without IRQF_ONESHOT. In fact, it would
be very simple to implement such a change, wanna take it up ?
It should be
On Tue, Jul 16, 2013 at 11:18 AM, Tony Lindgren t...@atomide.com wrote:
Here's a pull request for the pinctrl-single changes posted
few weeks ago. Assuming this pull request and the patches
are OK, I'd like to also merge this branch into omap tree so
we can have the wake-up events working. So
On Sat, Jun 8, 2013 at 5:27 PM, Tony Lindgren t...@atomide.com wrote:
Subject: [PATCH] pinctrl: single: Prepare for supporting SoC specific features
Let's replace is_pinconf with flags and add struct pcs_soc so we
can support also other features like pin wake-up events. Let's
export the
On 07/21/2013 06:44 PM, Grant Likely wrote:
On Sun, Jul 21, 2013 at 9:48 PM, Rob Herring robherri...@gmail.com wrote:
On 07/21/2013 09:42 AM, Rob Herring wrote:
On 07/19/2013 01:14 PM, Sebastian Andrzej Siewior wrote:
So I called of_platform_populate() on a device to get each child device
The mailbox DT node data has been added for OMAP2420,
OMAP2430, OMAP3430/OMAP3630, OMAP44xx devices. Data
for OMAP5 and other SoCs will be added separately.
The mailbox static device initialization logic is also
adjusted for a DT boot.
Signed-off-by: Suman Anna s-a...@ti.com
---
Hi,
This is an updated series for adding the device tree support to
the OMAP mailbox driver. The series is based on 3.11-rc2 and I
have tested this on Beagle-XM, Panda4 and OMAP5 uEVM (with
out-of-tree clock patches).
Changes in v2:
- Removed the #ti,mbox-data-cells from DT bindings and node
Add the hwmod data for the mailbox IP in OMAP5 SoC.
This is needed to be able to enable the OMAP mailbox
support for OMAP5.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 42 ++
1 file changed, 42 insertions(+)
diff --git
A new structure, omap_mbox_device, is added to contain
the global variables pertinent to a mailbox h/w IP block.
This enables the support for having multiple instances of
the same h/w IP block in the SoC. The startup sequence for
each mailbox is also simplified along the way, removing the
usage of
Logic has been added to the OMAP2+ mailbox code to
parse the mailbox dt nodes and construct the different
mailboxes associated with the instance. The design is
based on gathering the same information that was being
passed previously through the platform data, except for
the interrupt type
Add the mailbox device DT node for OMAP5 SoC.
Signed-off-by: Suman Anna s-a...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index e643620..a08f1ca 100644
---
On Mon, Jun 10, 2013 at 5:36 PM, Tony Lindgren t...@atomide.com wrote:
At least on omaps, each board typically has at least one device
configured as wake-up capable from deeper idle modes. In the
deeper idle modes the normal interrupt wake-up path won't work
as the logic is powered off and
On Fri, Jun 7, 2013 at 10:50 PM, Tony Lindgren t...@atomide.com wrote:
+static irqreturn_t pcs_omap_handle_irq(int irq, void *data)
+{
+ struct pcs_omap *pcso = data;
+ struct list_head *pos;
+ unsigned int wakeirq;
+
+ list_for_each(pos, pcso-wakeirqs) {
+
On Fri, Jun 7, 2013 at 10:50 PM, Tony Lindgren t...@atomide.com wrote:
For wake-up events from deeper idle modes we need to check the
configured padconf registers for the wake-up bit and then call
the related interrupt handler.
Done in collaboration with Roger Quadros rog...@ti.com.
Cc:
On Thu, Jul 18, 2013 at 5:15 PM, Tony Lindgren t...@atomide.com wrote:
There's no need to duplicate essentially the same functions. Let's
introduce static int pinctrl_pm_select_state() and make the other
related functions call that.
This allows us to add support later on for multiple active
On Thu, Jul 18, 2013 at 5:15 PM, Tony Lindgren t...@atomide.com wrote:
It's quite common that we need to dynamically change some pins for a
device for runtime PM, or toggle a pin between rx and tx. Changing all
What does change mean above?
Please reword to remux if that is what is meant.
On Tue, Jul 16, 2013 at 11:05 AM, Tony Lindgren t...@atomide.com wrote:
To toggle dynamic states, let's add the optional active state in
addition to the static default state. Then if the optional active
state is defined, we can require that idle and sleep states cover
the same pingroups as
On Fri, Jul 19, 2013 at 9:03 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 07/19/2013 04:29 AM, Grygorii Strashko wrote:
First of all, I'd like to mention that these patches do *not* connect
pinctrl to PM runtime, so until driver will call pinctrl_select_state()
or pinctrl_pm_select_*()
On Mon, Jul 15, 2013 at 04:23:26PM +0300, Felipe Balbi wrote:
On Mon, Jul 15, 2013 at 12:58:17AM -0700, Tony Lindgren wrote:
Author: Tony Lindgren t...@atomide.com
Date: Mon Jul 15 00:39:41 2013 -0700
ARM: multi_v7: Enabled omap4430 sdp nfsroot
By adding support for
On Fri, Jul 19, 2013 at 03:45:38AM -0700, Tony Lindgren wrote:
The following changes since commit ad81f0545ef01ea651886dddac4bef6cec930092:
Linux 3.11-rc1 (2013-07-14 15:18:27 -0700)
are available in the git repository at:
Hi Roger,
On Mon, Jul 22, 2013 at 6:30 AM, Roger Quadros rog...@ti.com wrote:
Hi,
I observe the following problem on booting v3.11-rc1 on OMAP3 beagle board.
[5.888946] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM
[5.896057] Modules linked in:
[5.899322] CPU: 0
On Monday 22 July 2013 11:18 PM, Paul Walmsley wrote:
Hi
On Mon, 22 Jul 2013, Rajendra Nayak wrote:
Memory controllers in OMAP (like GPMC and EMIF) have the hwmods marked with
HWMOD_INIT_NO_IDLE and are left in enabled state post initial setup.
Even if they have drivers missing, avoid
Hi,
On Monday 22 July 2013 08:34 PM, Greg KH wrote:
On Mon, Jul 22, 2013 at 12:55:18PM +0530, Kishon Vijay Abraham I wrote:
The issue (or one of the issues) in this discussion is that
Greg does not like the idea of using names or IDs to associate
PHYs with controllers, because
Hi,
On Monday 22 July 2013 08:14 PM, Alan Stern wrote:
On Mon, 22 Jul 2013, Kishon Vijay Abraham I wrote:
The PHY and the controller it is attached to are both physical
devices.
The connection between them is hardwired by the system
manufacturer and cannot be changed by
75 matches
Mail list logo
