From: Mathieu J. Poirier mathieu.poir...@canonical.com
https://bugs.launchpad.net/bugs/630885
When booting, the omapdss subsystem is looking for a regulator named
vdds_sdi. When the regulator is not found the initialisation sequence
is aborted resulting in omapfb not finding a display to work
Tomi,
-Original Message-
From: Valkeinen, Tomi
Sent: Wednesday, February 16, 2011 7:28 PM
To: Janorkar, Mayuresh
Cc: linux-omap@vger.kernel.org
Subject: Re: [RESEND][PATCH v2] OMAP: DSS: Adding two APIs for panel-taal:
check_timings and set_timings
Hi,
On Wed, 2011-02-16 at
On Wed, Feb 16, 2011 at 11:47:33AM -0800, Kevin Hilman wrote:
G, Manjunath Kondaiah manj...@ti.com writes:
Hi Kevin,
On Mon, Feb 14, 2011 at 02:06:53PM -0800, Kevin Hilman wrote:
G, Manjunath Kondaiah manj...@ti.com writes:
From: Manjunath G Kondaiah manj...@ti.com
Enable
All,
Due to the important number of modifications recently done on the
OMAP4 data compared to the original and the total absence of explanation
in the changelog, I re-submit the data before the driver series in order
to maintain the integrity of the original file and to avoid a huge pain
during
Add hwspinlock hwmod data for OMAP4 chip
Signed-off-by: Cousson, Benoit b-cous...@ti.com
Signed-off-by: Hari Kanigeri h-kanige...@ti.com
Signed-off-by: Ohad Ben-Cohen o...@wizery.com
Cc: Paul Walmsley p...@pwsan.com
[b-cous...@ti.com: Move the data to keep the original
order and add missing
Update omap4 hwmod file with McSPI info.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Signed-off-by: Charulatha V ch...@ti.com
Signed-off-by: Govindraj.R govindraj.r...@ti.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
Reviewed-by: Kevin Hilman khil...@ti.com
---
[b-cous...@ti.com: Remove
Add dss, dispc, dsi1, dsi2, hdmi, rfbi and venc hwmods.
In OMAP4 there are severals IPs that can be reached by differents
interconnect paths depending of the access initiator (MPU vs. SDMA).
In the case of the DSS, both L3 direct path and L4 CFG path can be
used to access all the DSS IPs. The two
Add the data for the 11 timers IPs.
OMAP4 contains two differents IP variants for the timers:
- 8 x regular timer (3, 4, 5, 6, 7, 8, 9 11)
- 3 x 1ms timer (1, 2 10)
The regular timers registers programming model was changed due to the
adaptation to the new IP interface. Unfortunately the 1ms
Mailbox hwmod data for omap4.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com
[b-cous...@ti.com: Re-order the structures
and remove the irq line name]
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 68 +++-
1 files
Add HWMOD entries for the OMAP DMIC. The HWMOD entires define the system
resource requirements for the driver such as DMA addresses, channels,
and IRQ's. Placing this information in the HWMOD database allows for
more generic drivers to be written and having the specific implementation
details
Add mcbsp data including a revision member in hwmod_class in
order to provide mcbsp revision information in different omap.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Signed-off-by: Charulatha V ch...@ti.com
[b-cous...@ti.com: Remove the
Add more hwmod structures but keep them commented out for the moment
until the driver adaptation to hwmod / omap_device is done.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Paul Walmsley p...@pwsan.com
Cc: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 1009
Hi,
Does the current Mux Framework support configuration of Registers like
CONTROL_DSIPHY, CONTROL_USB etc in SYSCTRL_PADCONF_CORE in OMAP4? Could
someone guide me to an example?
Thanks,
Archit
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
Colin,
On Tue, 2011-02-15 at 16:26 -0800, Colin Cross wrote:
On Tue, Feb 15, 2011 at 3:04 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Fri, Feb 11, 2011 at 06:50:57PM -0800, Colin Cross wrote:
+ENDPROC(cpu_resume_turn_mmu_on)
+cpu_resume_after_mmu:
+ str
On Thu, Feb 17, 2011 at 11:24:41AM +0100, Benoit Cousson wrote:
All,
Due to the important number of modifications recently done on the
OMAP4 data compared to the original and the total absence of explanation
in the changelog, I re-submit the data before the driver series in order
to
Hi Manjunath,
On 2/17/2011 11:42 AM, G, Manjunath Kondaiah wrote:
On Thu, Feb 17, 2011 at 11:24:41AM +0100, Benoit Cousson wrote:
All,
Due to the important number of modifications recently done on the
OMAP4 data compared to the original and the total absence of explanation
in the changelog, I
Hi all,
This is what I have for next merge window. If you have
patches that should go in, please re-send them now as I
don't have anything in my queue.
I dropped Ming's DMA rework because I'm not sure that's
the best approach. IMO, it's better to simplify DMA
programming by having one
During development, even though board is wired
to e.g. OTG, we might want to compile host-only
or peripheral-only configurations.
Let's allow that to happen.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/musb/musb_core.c | 25 -
1 files changed, 0
Just a few cosmetic fixes to usb_gadget_probe_driver()
and usb_gadget_unregister_driver().
Decreased a few indentation levels with goto statements.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/musb/musb_gadget.c | 150 +---
1 files changed, 79
struct usb_request's list_head is supposed to be
used only by gadget drivers, but musb is abusing
that. Give struct musb_request its own list_head
and prevent musb from poking into other driver's
business.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/musb/musb_core.h |4 +-
On Thu, Feb 17, 2011 at 12:07:21PM +0530, Hema HK wrote:
Using omap_device_build API instead of platform_device_register for
OMAP2430,OMAP3xxx, OMAP4430 and AM35x musb device registration.
The device specific resources defined in centralized
database will be used.
Signed-off-by: Hema HK
Hi Archit,
Those control registers are not a part of the mux list.
So the mux framework does not support configuring them.
Only the pad mux registers are configured.
Thanks,
Sricharan
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
(Avoid top posting please)
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Sricharan R
Sent: Thursday, February 17, 2011 5:05 PM
To: Archit Taneja; Benoit Cousson; linux-omap@vger.kernel.org
Subject: RE: OMAP4 Mux FW
On Wed, Feb 16, 2011 at 04:47:19PM +0530, Anand Gadiyar wrote:
Most revisions of the OMAP4 Blaze/SDP platform do not have
the EHCI signals routed by default. The pads are routed
for the alternate HSI functionality instead, and explicit
board modifications are needed to route the signals to
Hi,
On Thu, Feb 17, 2011 at 01:33:21PM +0200, Felipe Balbi wrote:
On Thu, Feb 17, 2011 at 12:07:21PM +0530, Hema HK wrote:
Using omap_device_build API instead of platform_device_register for
OMAP2430,OMAP3xxx, OMAP4430 and AM35x musb device registration.
The device specific resources
On Thu, Feb 17, 2011 at 12:07:16PM +0530, Hema HK wrote:
This patch series makes OMAP2PLUS and AM35x musb module implemented
in HWMOD FW way. It also implements musb driver to
use the runtime pm apis for OMAP2PLUS.
As per the OMAP usbotg specification[1] musb sysconfig register
has to be
Russell King - ARM Linux wrote:
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
---
arch/arm/mach-s3c64xx/sleep.S | 63 +-
arch/arm/mach-s5pv210/sleep.S | 104
+
--
arch/arm/plat-s3c24xx/sleep.S | 57
Hi Felipe,
-Original Message-
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Thursday, February 17, 2011 5:24 PM
To: Felipe Balbi
Cc: Hema HK; linux-...@vger.kernel.org;
linux-omap@vger.kernel.org; Tony Lindgren; Kevin Hilman;
Cousson, Benoit; Paul Walmsley
Subject: Re: [PATCH 5/6 v8]
On Thu, Feb 17, 2011 at 12:06:04PM +0530, Hema HK wrote:
From: Kalliguddi, Hema hem...@ti.com
Remove the regulator enable while driver loading and enable it only when
the cable/device is connected and disable it when disconnected.
Remove the configuration of config_state and config_trans
Hi,
On Thu, Feb 17, 2011 at 02:20:11PM +0200, Felipe Balbi wrote:
On Thu, Feb 17, 2011 at 12:06:04PM +0530, Hema HK wrote:
From: Kalliguddi, Hema hem...@ti.com
Remove the regulator enable while driver loading and enable it only when
the cable/device is connected and disable it when
On Thu, Feb 17, 2011 at 12:06:04PM +0530, Hema HK wrote:
From: Kalliguddi, Hema hem...@ti.com
You name is twisted in all this series, this will make git log look
weird:
Hema HK (1):
usb: musb: Using runtime pm APIs for musb.
Kalliguddi, Hema (7):
usb: otg: enable regulator only on
Hi Greg, all,
Here are the tested set of patches for the next merge window.
We have a pending fixes pull request [1] which could be
integrated to this one if wanted/needed.
I'll be waiting for v2.6.38-rc5 appear on greg/usb-next
before sending the pull request otherwise we will have
conflicts
During development, even though board is wired
to e.g. OTG, we might want to compile host-only
or peripheral-only configurations.
Let's allow that to happen.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/musb/musb_core.c | 25 -
1 files changed, 0
Just a few cosmetic fixes to usb_gadget_probe_driver()
and usb_gadget_unregister_driver().
Decreased a few indentation levels with goto statements.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/musb/musb_gadget.c | 150 +---
1 files changed, 79
struct usb_request's list_head is supposed to be
used only by gadget drivers, but musb is abusing
that. Give struct musb_request its own list_head
and prevent musb from poking into other driver's
business.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/musb/musb_core.h |4 +-
From: Hema HK hem...@ti.com
Calling runtime pm APIs pm_runtime_put_sync() and pm_runtime_get_sync()
for enabling/disabling the clocks, sysconfig settings.
Enable clock, configure no-idle/standby when active and configure force
idle/standby
and disable clock when idled. This is taken care by the
From: Hema HK hem...@ti.com
Remove the regulator enable while driver loading and enable it only when
the cable/device is connected and disable it when disconnected.
Remove the configuration of config_state and config_trans register
configuration as these registers are programmed when regulator
From: Hema HK hem...@ti.com
Declare the .phy_suspend function pointer to twl4030_usb_data structure.
OMAP internal phy suspend function will be hooked though this function
pointer to use in the transceiver driver.
Signed-off-by: Hema HK hem...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: Paul
From: Hema HK hem...@ti.com
Introduced the suspend/resume function for the OMAP4430 internal PHY.
This will be used by the twl6030-usb transceiver driver.
Moved the clock enable/disable function calls and power on/off of the PHY
code from power on/off functions to suspend/resume function.
Pass
From: Hema HK hem...@ti.com
To get the ID status there was an I2C read transfer. Removed this I2C
read transfer as this info can be used from existing variable(linkstat).
Signed-off-by: Hema HK hem...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: Paul Walmsley p...@pwsan.com
Signed-off-by:
From: Hema HK hem...@ti.com
Introduce the twl6030_phy_suspend function and assign to otg.set_suspend
function pointer.
This function is used by the musb-omap2430 platform driver
during suspend/resume.
Signed-off-by: Hema HK hem...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: Paul Walmsley
From: Hema HK hem...@ti.com
Save the last event in the otg_transceiver so that it can used in the
musb driver and gadget driver to configure the musb and enable the
vbus for host mode and OTG mode, if the device is connected during boot.
Signed-off-by: Hema HK hem...@ti.com
Cc: Tony Lindgren
From: Hema HK hem...@ti.com
OMAP4430 is embedded with UTMI PHY. This PHY does not support the
OTG features like ID pin detection and VBUS detection. This function
is exported to an external companion chip TWL6030. Software must retrieve
the OTG HNP and SRP status from the TWL6030 and configure
most of our notifications, will be called from IRQ
context, so an atomic notifier suits the job better.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/otg/ab8500-usb.c|6 +++---
drivers/usb/otg/nop-usb-xceiv.c |2 +-
drivers/usb/otg/twl4030-usb.c |6 +++---
Hi Tony,
here are the patches for next merge window which I
have queued for you. A pull request is comming tomorrow.
All patches where boot tested on omap4430 pandaboard.
Anand Gadiyar (2):
arm: omap4: usb: explicitly configure MUSB pads
arm: omap4: 4430sdp: drop ehci support
Hema HK (5):
From: Anand Gadiyar gadi...@ti.com
Use the mux framework APIs to explicitly configure
the MUSB pads. The MUSB controller in OMAP4 can use
either the old ULPI interface, or the new internal PHY.
Configure the pads accordingly.
Signed-off-by: Anand Gadiyar gadi...@ti.com
Cc: Tony Lindgren
From: Anand Gadiyar gadi...@ti.com
Most revisions of the OMAP4 Blaze/SDP platform do not have
the EHCI signals routed by default. The pads are routed
for the alternate HSI functionality instead, and explicit
board modifications are needed to route the signals to
the USB PHY on the board.
Also,
From: Hema HK hem...@ti.com
OMAP2430 hwmod data structures are populated with base address, L3 and L4
interface clocks, IRQs and sysconfig register details.
As per OMAP USBOTG specification, need to configure the USBOTG
to smart idle/standby or no idle/standby during data transfer and
force
From: Hema HK hem...@ti.com
OMAP3 hwmod data structures are populated for USBOTG with base address,
L3 and L4 interface clocks, IRQs and sysconfig register details.
This is applicable for OMAP3430 amd OMAP3630.
As per OMAP USBOTG specification, need to configure the USBOTG
to smart idle/standby
From: Hema HK hem...@ti.com
OMAP4 hwmod data structures are populated with base address, L3 and L4
interface clocks, IRQs and sysconfig register details.
As per OMAP USBOTG specification, need to configure the USBOTG
to smart idle/standby or no idle/standby during data transfer and
force
From: Hema HK hem...@ti.com
AM35xx hwmod data structures are populated for USBOTG with base address,
L3 and L4 interface clocks and IRQ.
Signed-off-by: Hema HK hem...@ti.com
Cc: Tony Lindgren t...@atomide.com
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Cousson, Benoit b-cous...@ti.com
Cc:
From: Hema HK hem...@ti.com
Using omap_device_build API instead of platform_device_register for
OMAP2430,OMAP3xxx, OMAP4430 and AM35x musb device registration.
The device specific resources defined in centralized
database will be used.
Signed-off-by: Hema HK hem...@ti.com
Cc: Tony Lindgren
This set of patches, along with some other patches under
discussion on alkml, should enable omap3 and omap4 kernels to be
built with CONFIG_THUMB2_KERNEL.
This patch set builds on recent cleanup done by the omap
maintainers.
At least some of this code definitely works, most features have
been
For CONFIG_THUMB2_KERNEL, the existing definition of do_wfi() will
insert invalid code into the instruction stream.
Any assembler which can assemble Thumb-2 is guaranteed to accept
the wfi mnemonic, so for the Thumb-2 case, just use the mnemonic.
The ARM case is left as-is.
Signed-off-by: Dave
Code marked with ENTRY() also needs a matching ENDPROC() directive,
in order to ensure that the type and instruction set of the
symbol are correctly annotated.
ENDPROC() tags the affected symbol as a function symbol, which will
ensure that link-time fixups don't accidentally switch to the
wrong
For various reasons, Linux now only officially supports being built
with tools which are new enough to understand the SMC instruction.
Replacing the hand-encoded instructions when the mnemonic also
allows for correct assembly in Thumb-2 (otherwise, the result is
random data in the middle of the
* Build unconditionally as ARM for correct interoperation with
OMAP firmware.
* Remove deprecated PC-relative stores
* Add the required ENDPROC() directive for each ENTRY().
* .align before data words
Signed-off-by: Dave Martin dave.mar...@linaro.org
---
arch/arm/mach-omap2/sram34xx.S
* Build unconditionally as ARM for correct interoperation with
OMAP firmware.
* Fix an out-of-range ADR when building for ARM.
* Remove deprecated PC-relative stores.
* Add the required ENDPROC() directive for each ENTRY().
* .align before data words.
* Handle non-interworking return
Hello.
On 17-02-2011 14:30, Felipe Balbi wrote:
Just a few cosmetic fixes to usb_gadget_probe_driver()
and usb_gadget_unregister_driver().
Decreased a few indentation levels with goto statements.
Signed-off-by: Felipe Balbiba...@ti.com
[...]
diff --git a/drivers/usb/musb/musb_gadget.c
Hi,
On Thu, Feb 17, 2011 at 04:00:30PM +0300, Sergei Shtylyov wrote:
diff --git a/drivers/usb/musb/musb_gadget.c b/drivers/usb/musb/musb_gadget.c
index 2fe3046..86decba 100644
--- a/drivers/usb/musb/musb_gadget.c
+++ b/drivers/usb/musb/musb_gadget.c
@@ -1801,90 +1801,95 @@ void
Hi Felipe and Hema,
Sorry for this late review, but I have a couple of comments on this one.
Since I was planning to send usb hwmod data file to Tony directly like I
did for the other drivers, I can handle the update myself if you want.
On 2/17/2011 1:41 PM, Balbi, Felipe wrote:
From: Hema
On Thu, Feb 17, 2011 at 10:41:52AM +, Lorenzo Pieralisi wrote:
When calling suspend from cpuidle, do you flush the stack (ie CPU
context) from L2 using outer_cache functions ? This has to be done when
one CPU is shut down with L2 enabled for the MMU off resume path to work
properly.
I
Russell King - ARM Linux wrote:
On Wed, Feb 16, 2011 at 04:47:19PM +0530, Anand Gadiyar wrote:
Most revisions of the OMAP4 Blaze/SDP platform do not have
the EHCI signals routed by default. The pads are routed
for the alternate HSI functionality instead, and explicit
board modifications
On Thu, Feb 17, 2011 at 09:09:02PM +0900, Kukjin Kim wrote:
Hi Russell,
I tested on SMDKV210(S5PV210) and SMDKC110(S5PC110).
Thanks for testing. It looks like I'm missing a load for r3 in the
s5pv210 code. The replacement patch below should resolve this.
arch/arm/mach-s3c64xx/sleep.S
Benoit,
-Original Message-
From: Cousson, Benoit [mailto:b-cous...@ti.com]
Sent: Thursday, February 17, 2011 7:13 PM
To: Balbi, Felipe
Cc: Tony Lindgren; Linux OMAP Mailing List; Linux ARM Kernel
Mailing List; Kalliguddi, Hema; Kevin Hilman; Paul Walmsley
Subject: Re: [patch-v2.6.39 6/7]
Currently, the core DSS platform device requests for an irq line for OMAP2 and
OMAP3. Make DISPC and DSI platform devices request for a shared IRQ line.
On OMAP3, the logical OR of DSI and DISPC interrupt lines goes to the MPU. There
is a register DSS_IRQSTATUS which tells if the interrupt came
On Wed, 16 Feb 2011, Raghuveer Murthy wrote:
On Monday 14 February 2011 09:32 PM, Valkeinen, Tomi wrote:
On Thu, 2011-02-03 at 07:56 -0600, Murthy, Raghuveer wrote:
- Adding dss_feature for DPLL fclk
- Enabling pixel clock generation for DPI interface
A bit more description what the
Hi Benoit,
One minor comment;
On Thu, Feb 17, 2011 at 3:54 PM, Benoit Cousson b-cous...@ti.com wrote:
Add dss, dispc, dsi1, dsi2, hdmi, rfbi and venc hwmods.
In OMAP4 there are severals IPs that can be reached by differents
interconnect paths depending of the access initiator (MPU vs. SDMA).
On Thu, Feb 17, 2011 at 02:43:21PM +0100, Cousson, Benoit wrote:
Hi Felipe and Hema,
Sorry for this late review, but I have a couple of comments on this one.
Since I was planning to send usb hwmod data file to Tony directly
like I did for the other drivers, I can handle the update myself
On Thu, Feb 17, 2011 at 05:15:27PM +0200, Felipe Balbi wrote:
On Thu, Feb 17, 2011 at 02:43:21PM +0100, Cousson, Benoit wrote:
Hi Felipe and Hema,
Sorry for this late review, but I have a couple of comments on this one.
Since I was planning to send usb hwmod data file to Tony directly
On 2/17/2011 4:18 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 05:15:27PM +0200, Felipe Balbi wrote:
On Thu, Feb 17, 2011 at 02:43:21PM +0100, Cousson, Benoit wrote:
Hi Felipe and Hema,
Sorry for this late review, but I have a couple of comments on this one.
Since I was planning to send
hi,
On Thu, Feb 17, 2011 at 03:15:10PM +0200, Felipe Balbi wrote:
I can update the commit log, but basically it's the counterpart of
musb_start(). See that we call:
if (!is_otg_enabled(musb))
musb_start(musb);
so we need to undo that on the error path.
Better ?
usb: musb: gadget:
On Thu, Feb 17, 2011 at 04:21:47PM +0100, Cousson, Benoit wrote:
On 2/17/2011 4:18 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 05:15:27PM +0200, Felipe Balbi wrote:
On Thu, Feb 17, 2011 at 02:43:21PM +0100, Cousson, Benoit wrote:
Hi Felipe and Hema,
Sorry for this late review, but I
On Thu, Feb 17, 2011 at 8:32 PM, Semwal, Sumit sumit.sem...@ti.com wrote:
Hi Benoit,
One minor comment;
On Thu, Feb 17, 2011 at 3:54 PM, Benoit Cousson b-cous...@ti.com wrote:
Add dss, dispc, dsi1, dsi2, hdmi, rfbi and venc hwmods.
In OMAP4 there are severals IPs that can be reached by
On Wed, Feb 16, 2011 at 05:34:40PM +0530, Hema HK wrote:
Moved all the board specific internal PHY functions out of usb_musb.c file
as this file is shared between the OMAP2+ and AM35xx platforms.
There exists a file which has the functions specific to internal PHY
used for OMAP4 platform.
On 2/17/2011 4:26 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 04:21:47PM +0100, Cousson, Benoit wrote:
On 2/17/2011 4:18 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 05:15:27PM +0200, Felipe Balbi wrote:
On Thu, Feb 17, 2011 at 02:43:21PM +0100, Cousson, Benoit wrote:
Hi Felipe and
From: Anand S Sawant saw...@ti.com
omap_sr_probe() creates the smartreflex debug directory and its
underlying nvalue debug directory. These directories are removed in
omap_sr_remove().
Basic smartreflex functionality tested on OMAP3630 Zoom3 OMAP4430 SDP
Signed-off-by: Anand S Sawant
Kevin,
On Tue, Feb 15, 2011 at 9:36 PM, Kevin Hilman khil...@ti.com wrote:
Sawant, Anand saw...@ti.com writes:
Kevin,
On Sat, Feb 12, 2011 at 5:20 AM, Kevin Hilman khil...@ti.com wrote:
Hi Anand,
Anand S Sawant saw...@ti.com writes:
omap_sr_probe() creates the smartreflex debug
* Cousson, Benoit b-cous...@ti.com [110217 03:05]:
McSPI is already merged to l-o master. Will not this series breaks spi
hwmod?
The master branch is just a merge of the various branches, I have not
yet merged any of the hwmod touching branches into omap-for-linus.
It will not break, it
* Cousson, Benoit b-cous...@ti.com [110217 07:52]:
On 2/17/2011 4:26 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 04:21:47PM +0100, Cousson, Benoit wrote:
On 2/17/2011 4:18 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 05:15:27PM +0200, Felipe Balbi wrote:
On Thu, Feb 17, 2011 at
* Felipe Balbi ba...@ti.com [110217 07:25]:
Tony, what do you prefer ? Do we clear out the dependency, or you queue
all the patches I have manually ??
Let's apply Benoit's hwmod data patches first into omap-for-linus,
then rebasing other patches to that should be trivial and I can
pull in
On Thu, Feb 17, 2011 at 08:20:01AM -0800, Tony Lindgren wrote:
* Cousson, Benoit b-cous...@ti.com [110217 07:52]:
On 2/17/2011 4:26 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 04:21:47PM +0100, Cousson, Benoit wrote:
On 2/17/2011 4:18 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at
On Thu, Feb 17, 2011 at 08:21:57AM -0800, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [110217 07:25]:
Tony, what do you prefer ? Do we clear out the dependency, or you queue
all the patches I have manually ??
Let's apply Benoit's hwmod data patches first into omap-for-linus,
then
* Felipe Balbi ba...@ti.com [110217 08:20]:
On Thu, Feb 17, 2011 at 08:20:01AM -0800, Tony Lindgren wrote:
Maybe no need to rebase, I'll apply Benoit's series first into
omap-for-linus, then let's applying the other hwmod related patches
should be trivial.
So I can drop the omap4
Hi,
Noticed one cosmetic thing below.
* Benoit Cousson b-cous...@ti.com [110217 02:23]:
Update omap4 hwmod file with McSPI info.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Signed-off-by: Charulatha V ch...@ti.com
Signed-off-by: Govindraj.R govindraj.r...@ti.com
Acked-by: Grant Likely
On Thu, Feb 17, 2011 at 1:42 PM, Dave Martin dave.mar...@linaro.org wrote:
For various reasons, Linux now only officially supports being built
with tools which are new enough to understand the SMC instruction.
Replacing the hand-encoded instructions when the mnemonic also
allows for correct
On Thu, Feb 17, 2011 at 1:42 PM, Dave Martin dave.mar...@linaro.org wrote:
* Build unconditionally as ARM for correct interoperation with
OMAP firmware.
* Fix an out-of-range ADR when building for ARM.
* Remove deprecated PC-relative stores.
* Add the required ENDPROC() directive for
On 2/17/2011 5:59 PM, Tony Lindgren wrote:
* Felipe Balbiba...@ti.com [110217 08:20]:
On Thu, Feb 17, 2011 at 08:20:01AM -0800, Tony Lindgren wrote:
Maybe no need to rebase, I'll apply Benoit's series first into
omap-for-linus, then let's applying the other hwmod related patches
should be
On Thu, Feb 17, 2011 at 06:14:24PM +0100, Cousson, Benoit wrote:
On 2/17/2011 5:59 PM, Tony Lindgren wrote:
* Felipe Balbiba...@ti.com [110217 08:20]:
On Thu, Feb 17, 2011 at 08:20:01AM -0800, Tony Lindgren wrote:
Maybe no need to rebase, I'll apply Benoit's series first into
On Thu, Feb 17, 2011 at 06:14:24PM +0100, Cousson, Benoit wrote:
On 2/17/2011 5:59 PM, Tony Lindgren wrote:
* Felipe Balbiba...@ti.com [110217 08:20]:
On Thu, Feb 17, 2011 at 08:20:01AM -0800, Tony Lindgren wrote:
Maybe no need to rebase, I'll apply Benoit's series first into
On 2/17/2011 6:17 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 06:14:24PM +0100, Cousson, Benoit wrote:
On 2/17/2011 5:59 PM, Tony Lindgren wrote:
* Felipe Balbiba...@ti.com [110217 08:20]:
On Thu, Feb 17, 2011 at 08:20:01AM -0800, Tony Lindgren wrote:
Maybe no need to rebase, I'll
On Thu, Feb 17, 2011 at 06:24:53PM +0100, Cousson, Benoit wrote:
On 2/17/2011 6:17 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 06:14:24PM +0100, Cousson, Benoit wrote:
On 2/17/2011 5:59 PM, Tony Lindgren wrote:
* Felipe Balbiba...@ti.com [110217 08:20]:
On Thu, Feb 17, 2011 at
On 2/17/2011 6:37 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 06:24:53PM +0100, Cousson, Benoit wrote:
On 2/17/2011 6:17 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 06:14:24PM +0100, Cousson, Benoit wrote:
On 2/17/2011 5:59 PM, Tony Lindgren wrote:
* Felipe Balbiba...@ti.com
On 2/17/2011 6:05 PM, Tony Lindgren wrote:
Hi,
Noticed one cosmetic thing below.
* Benoit Coussonb-cous...@ti.com [110217 02:23]:
Update omap4 hwmod file with McSPI info.
Signed-off-by: Benoit Coussonb-cous...@ti.com
Signed-off-by: Charulatha Vch...@ti.com
Signed-off-by:
On Thu, Feb 17, 2011 at 06:46:59PM +0100, Cousson, Benoit wrote:
On 2/17/2011 6:37 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 06:24:53PM +0100, Cousson, Benoit wrote:
On 2/17/2011 6:17 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 06:14:24PM +0100, Cousson, Benoit wrote:
On 2/17/2011
On Thu, Feb 17, 2011 at 07:52:17PM +0200, Felipe Balbi wrote:
On Thu, Feb 17, 2011 at 06:46:59PM +0100, Cousson, Benoit wrote:
On 2/17/2011 6:37 PM, Balbi, Felipe wrote:
On Thu, Feb 17, 2011 at 06:24:53PM +0100, Cousson, Benoit wrote:
On 2/17/2011 6:17 PM, Balbi, Felipe wrote:
On Thu, Feb
* Cousson, Benoit b-cous...@ti.com [110217 09:45]:
Done, boot tested, and that does remove the warning about the
missing opt clock you had with the previous data.
git://gitorious.org/omap-pm/linux.git for_2.6.39/omap4_hwmod_data
Just let me know if it does break anything else.
Pulled
On Thu, Feb 10, 2011 at 01:48:54PM +0200, Felipe Balbi wrote:
Hi,
On Thu, Feb 10, 2011 at 05:07:06PM +0530, Premi, Sanjeev wrote:
diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig
index 5a7c8f1..ac137d1 100644
--- a/drivers/usb/Kconfig
+++ b/drivers/usb/Kconfig
@@ -10,8
On Thu, Feb 17, 2011 at 10:18:49AM -0800, Tony Lindgren wrote:
* Cousson, Benoit b-cous...@ti.com [110217 09:45]:
Done, boot tested, and that does remove the warning about the
missing opt clock you had with the previous data.
git://gitorious.org/omap-pm/linux.git
On Thu, Feb 17, 2011 at 02:38:45PM +0200, Felipe Balbi wrote:
From: Hema HK hem...@ti.com
Introduced the suspend/resume function for the OMAP4430 internal PHY.
This will be used by the twl6030-usb transceiver driver.
Moved the clock enable/disable function calls and power on/off of the PHY
1 - 100 of 146 matches
Mail list logo
