-Original Message-
From: Hunter, Jon
Sent: Thursday, April 11, 2013 7:17 AM
To: Shilimkar, Santosh
Cc: Cousson, Benoit; linux-omap@vger.kernel.org; linux-arm-
ker...@lists.infradead.org; t...@atomide.com; Hiremath, Vaibhav
Subject: Re: [PATCH v2 11/11] ARM: OMAP2+: omap_hwmod: Don't
Hi Benoit,
Are there any review comments on this patch?
Could you please accept this patch if there are not any review comments?
Thanks
Manish Badarkhe
-Original Message-
From: Vishwanathrao Badarkhe, Manish
Sent: Monday, March 11, 2013 3:30 PM
To: devicetree-disc...@lists.ozlabs.org;
Hi,
On Thursday 11 April 2013 01:11 AM, Paul Walmsley wrote:
From: Kishon Vijay Abraham I kis...@ti.com
Commit 92702df3570e (ARM: OMAP4: PM: fix PM regression introduced by recent
clock cleanup) makes the 'ocp2scp_usb_phy_phy_48m' as optional
functional clock causing regression in MUSB. But
This is a resend. The single change is the added changelog
https://patchwork.kernel.org/patch/1886421/
Andreas Fenkart (1):
gpio/omap: implement irq_enable/disable using mask/unmask.
drivers/gpio/gpio-omap.c |2 ++
1 file changed, 2 insertions(+)
--
1.7.10.4
--
To unsubscribe from this
In PM suspend, some omaps can't detect sdio irqs via the sdio interface.
The way to implement this, is to declare the corresponding pin as part
of the sdio interface and as a gpio input via pinctrl-single states.
The MMC driver request states default active and idle during the
probe, then toggles
On 12/02/13 21:15, David Miller wrote:
From: Mugunthan V N mugunthan...@ti.com
Date: Tue, 12 Feb 2013 01:22:17 +0530
This patch series implements Dual EMAC mode implementation of CPSW
which acts as two standalone EMAC by segregating the switch using VIDs
and port VLAN
Mugunthan V N (3):
On Friday 12 April 2013 02:43 PM, Andreas Fenkart wrote:
In PM suspend, some omaps can't detect sdio irqs via the sdio interface.
The way to implement this, is to declare the corresponding pin as part
of the sdio interface and as a gpio input via pinctrl-single states.
The MMC driver request
On Thu, Apr 11, 2013 at 05:19:21PM +0100, Stephen Warren wrote:
On 04/10/2013 10:46 PM, Li Haifeng wrote:
2013/4/10 Stephen Warren swar...@wwwdotorg.org:
On 04/10/2013 03:35 AM, Li Haifeng wrote:
Hi, everyone.
Recently, I try to run kdump on pandaboard ES with omap4460. After
load
Hi,
On Fri, Apr 12, 2013 at 03:49:52PM +0530, Santosh Shilimkar wrote:
On Friday 12 April 2013 02:43 PM, Andreas Fenkart wrote:
In PM suspend, some omaps can't detect sdio irqs via the sdio interface.
The way to implement this, is to declare the corresponding pin as part
of the sdio
On Wed, 10 Apr 2013 11:08:00 +0200, Peter Ujfalusi peter.ujfal...@ti.com
wrote:
Boards supported upstream all use TWL6040 as audio codec, enable the
common
ASoC machine driver by default for them.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Tested-by: Jyri Sarha jsa...@ti.com
Brings
This is a resend of an earlier patch
http://comments.gmane.org/gmane.linux.ports.arm.omap/90381
It's rebased against Linux 3.9-rc6 / 31880c37c11e28cb8
Main changes are two bug fixes. Also did lots of testing.
Fixes are a race condition during suspend and the gpio
irq being disabled unintendedly.
Without functional clock the omap_hsmmc module can't forward
SDIO IRQs to the system. This patch reconfigures dat1 line as a
gpio while the fclk is off. It uses regulare SDIO IRQ detection of
the module, while fclk is present.
Reviewed-by: Grant Likely grant.lik...@secretlab.ca
Signed-off-by:
Signed-off-by: Andreas Fenkart andreas.fenk...@streamunlimited.com
diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
index c52a0d1..0f9eb54 100644
--- a/drivers/mmc/host/omap_hsmmc.c
+++ b/drivers/mmc/host/omap_hsmmc.c
@@ -212,6 +212,7 @@ struct omap_hsmmc_host {
PSTATE shows current state of data lines.
Signed-off-by: Andreas Fenkart andreas.fenk...@streamunlimited.com
diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
index 0f9eb54..f292d1d 100644
--- a/drivers/mmc/host/omap_hsmmc.c
+++ b/drivers/mmc/host/omap_hsmmc.c
@@ -54,6
On 04/12/2013 04:45 AM, Will Deacon wrote:
...
Back to the SMP point: Stephen, did you ever get anywhere with that
disable_nonboot_cpus thread from a few months back? I'm still keen to get
that working, and I *thought* we had a potential solution...
No, I've been side-tracked on too many other
Hello,
This is the second attempt to solve the issue that IRQ flags when
defined using Device Trees, are not passed to drivers that try
to obtain them from a IORESOURCE_IRQ struct resource.
According to
Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
the #interrupt-cells
When defining an IRQ trigger type and level flags from a Device Tree
a call to of_irq_to_resource() is made to parse the interrupts
property cells and return a struct resource.
But the flags are not saved on this struct resource which means that
drivers that try to obtain this information from an
According to
Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
the #interrupt-cells property of an interrupt-controller is used
to define the number of cells needed to specify a single interrupt.
A commonly used variant is two cell on which #interrupt-cells = 2
and the first
On 04/12/2013 12:05 PM, Javier Martinez Canillas wrote:
...
So, is better to add an irq_get_trigger_type() function to obtain
the edge/level flags for an IRQ.
diff --git a/include/linux/irq.h b/include/linux/irq.h
+static inline u32 irq_get_trigger_type(unsigned int irq)
+{
+ struct
AM33XX based platforms use dpll_mpu clock. Add same to common dtsi
and remove the dummy clock node entry as AM33XX platform supports
only device tree based boot.
Cc: Benoit Cousson b-cous...@ti.com
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Paul Walmsley p...@pwsan.com
Cc: Tony Lindgren
With OMAP3+ and AM33xx supported SoC having defined CPU device tree
entries with operating-points and clock nodes defined, we can now use
the SoC generic cpufreq-cpu0 driver by registering appropriate device.
Cc: Benoit Cousson b-cous...@ti.com
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc:
Call OMAP2+ generic lateinit hook from AM specific late init hook.
This allows the generic late initializations such as cpufreq hooks
to be active.
Cc: Benoit Cousson b-cous...@ti.com
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Paul Walmsley p...@pwsan.com
Cc: Tony Lindgren t...@atomide.com
OMAP443x, OMAP446x and OMAP447x platforms use dpll_mpu clock.
Add same to common definition.
Cc: Benoit Cousson b-cous...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
RFC of this patch approach for OMAP3 was discussed in
http://marc.info/?t=13637032569r=1w=2
along with the detailed
The following version 4 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
maintaining support of the legacy omap-cpufreq driver when used in
OMAP34xx and OMAP36xx platforms use dpll1 clock. Add same to common
definition.
Cc: Benoit Cousson b-cous...@ti.com
Signed-off-by: Nishanth Menon n...@ti.com
---
RFC of this patch was discussed in http://marc.info/?t=13637032569r=1w=2
along with the detailed context as to why this is an
OMAP clock data is located in arch/arm/mach-omap2/cclockXYZ_data.c.
However, this presents an obstacle for using these clock nodes in
Device Tree definitions. This is especially true for board specific
clocks initially. The fixed clocks are currently found via clock
aliases table. There are many
* Nishanth Menon n...@ti.com [130412 15:59]:
--- /dev/null
+++ b/drivers/clk/omap/clk.c
+/**
+ * omap_clk_src_get() - Get OMAP clock from node name when needed
+ * @clkspec: clkspec argument
+ * @data:unused
+ *
+ * REVISIT: We assume the following:
+ * 1. omap clock names end with
On 16:31-20130412, Tony Lindgren wrote:
* Nishanth Menon n...@ti.com [130412 15:59]:
--- /dev/null
+++ b/drivers/clk/omap/clk.c
+/**
+ * omap_clk_src_get() - Get OMAP clock from node name when needed
+ * @clkspec: clkspec argument
+ * @data: unused
+ *
+ * REVISIT: We
* Tony Lindgren t...@atomide.com [130410 15:32]:
* Jon Hunter jon-hun...@ti.com [130410 15:30]:
Are you saying that you want to use the version with that is using the
pre-processor definitions? I was thinking that may be we could do that
as a clean-up for v3.11 and just use the original
Selecting CONFIG_DMADEVICES is optional, and we must
be able to continue even without DMA. Otherwise things
like omap4430sdp nfsroot will fail if DMA is not
selected.
Note that the driver already supports PIO mode, but
we fail to fall back to PIO if requesting DMA channels
fails.
Signed-off-by:
The bootloader configures the pins, but has pull bits
set without pull enable bits. While this is harmless,
and won't do anything, it seems to cause confusion at
least for me every time looking at the pin configuration.
Fix it for DT based boot.
Signed-off-by: Tony Lindgren t...@atomide.com
---
On 04/12/2013 11:56 PM, Stephen Warren wrote:
On 04/12/2013 12:05 PM, Javier Martinez Canillas wrote:
...
So, is better to add an irq_get_trigger_type() function to obtain
the edge/level flags for an IRQ.
diff --git a/include/linux/irq.h b/include/linux/irq.h
+static inline u32
According to
Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
the #interrupt-cells property of an interrupt-controller is used
to define the number of cells needed to specify a single interrupt.
A commonly used variant is two cell on which #interrupt-cells = 2
and the first
On 04/12/2013 07:06 PM, Tony Lindgren wrote:
* Tony Lindgren t...@atomide.com [130410 15:32]:
* Jon Hunter jon-hun...@ti.com [130410 15:30]:
Are you saying that you want to use the version with that is using the
pre-processor definitions? I was thinking that may be we could do that
as a
34 matches
Mail list logo
