This patch adds support for speed enhanced variant of OMAP35x
processors. These parts allow ARM and IVA running at 720MHz
and 520MHz respectively.
These parts can be detected at runtime by reading contents of
PRODID.SKUID[3:0] at 0x4830A20C [1].
This patch specifically does following:
* Add new
On Wed, Feb 9, 2011 at 6:04 AM, Santosh Shilimkar
wrote:
>> -Original Message-
>> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
>> ow...@vger.kernel.org] On Behalf Of Tony Lindgren
>> Sent: Wednesday, February 09, 2011 6:06 AM
>> To: Nicolas Pitre
>> Cc: Santosh Shilimkar; Rus
On Wed, Feb 9, 2011 at 5:45 AM, Santosh Shilimkar
wrote:
>> -Original Message-
>> From: Dave Martin [mailto:dave.mar...@linaro.org]
>> Sent: Tuesday, February 08, 2011 11:11 PM
>> To: Santosh Shilimkar
>> Cc: linux-arm-ker...@lists.infradead.org; Tony Lindgren; Jean Pihet-
>> XID; linux-om
> -Original Message-
> From: Dave Martin [mailto:dave.mar...@linaro.org]
> Sent: Wednesday, February 09, 2011 3:18 PM
> To: Santosh Shilimkar
> Cc: Tony Lindgren; Nicolas Pitre; linux-omap@vger.kernel.org;
> Russell King - ARM Linux; linux-arm-ker...@lists.infradead.org
> Subject: Re: [PATC
On 8 February 2011 16:47, Russell King - ARM Linux
wrote:
> On Tue, Feb 08, 2011 at 10:06:20PM +0530, Santosh Shilimkar wrote:
>> Have tested this series on OMAP4430 and OMAP3430.
>> Don't know if it helps to push some of these patches to be part
>> of rc cycles. At least the SMP specific fixes sh
On Tuesday 08 February 2011, Dave Martin wrote:
> I have a (possibly silly) question ... are the definitions in
> arm/system.h intended to be fully generic, or not? Some features
> suggest an attempt at genericness, but not everything there is
> generic. Maybe I have misconstrued the purpose of t
On Wed, 2011-02-09 at 12:23 +0530, G, Manjunath Kondaiah wrote:
> On Wed, Feb 9, 2011 at 1:13 AM, Ricardo Salveti de Araujo
> wrote:
> > Function beagle_twl_gpio_setup is called after beagle_display_init, what
> > lets reset_gpio with an invalid value at the time it request the gpio.
> > As a side
On Wed, Feb 9, 2011 at 5:17 PM, Ricardo Salveti de Araujo
wrote:
> On Wed, 2011-02-09 at 12:23 +0530, G, Manjunath Kondaiah wrote:
>> On Wed, Feb 9, 2011 at 1:13 AM, Ricardo Salveti de Araujo
>> wrote:
>> > Function beagle_twl_gpio_setup is called after beagle_display_init, what
>> > lets reset_g
Adding DVI support to OMAP4 PandaBoard.
PandaBoard uses TFP410 DVI Framer chip
http://focus.ti.com/lit/ds/symlink/tfp410.pdf
The TFP410 gets its power enable and display data over GPIO lines muxed
in from OMAP4430. PandaBoard supports other LCD displays through expansion
connectors, following boa
On Wed, Feb 9, 2011 at 7:25 PM, Raghuveer Murthy
wrote:
> Adding DVI support to OMAP4 PandaBoard.
>
> PandaBoard uses TFP410 DVI Framer chip
> http://focus.ti.com/lit/ds/symlink/tfp410.pdf
>
> The TFP410 gets its power enable and display data over GPIO lines muxed
> in from OMAP4430. PandaBoard su
On Wed, Jan 26, 2011 at 05:25:35PM +, Dave P. Martin wrote:
> SMP_ON_UP fixups lead to vmlinux link errors if those sections are
> discarded at link-time. In particular this may happen for built-in
> __exit stuff.
>
> This patch modifies the vmlinux linker script to reduce the amount
> of dis
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.
All affected low-level code is now built in Thumb-2. At least some
of t
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
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 co
* Remove deprecated/undefined PC-relative stores
* Add the required ENDPROC() directive for each ENTRY().
* .align before data words
Signed-off-by: Dave Martin
Tested-by: Santosh Shilimkar
Acked-by: Santosh Shilimkar
---
arch/arm/mach-omap2/sram34xx.S | 28
1
* Use BSYM() to get the correct Thumb branch address
for adr ,
* Fix an out-of-range ADR when building for ARM
* Correctly call es3_sdrc_fix as Thumb when copied to SRAM.
* Remove deprecated/undefined PC-relative stores
* Add the required ENDPROC() directive for each ENTRY().
* .alig
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 in
add clk32kg to twl-regulator
add clk32kg board data to Blaze and Panda
Balaji T K (2):
regulator: twl: add clk32kg to twl-regulator
OMAP4: add clk32kg data to omap4panda and blaze board file
arch/arm/mach-omap2/board-4430sdp.c| 10 ++
arch/arm/mach-omap2/board-omap4panda.c |
Vishwanath Sripathy writes:
[...]
>> > + * This is a fundamental structure used to store all the required
>> > + * DVFS related information for a vdd.
>> > + */
>> > +struct omap_vdd_dvfs_info {
>> > + spinlock_t user_lock; /* spin lock */
>>
>> comment redundant
>>
>
> I added this because che
In OMAP4 Blaze and Panda, 32KHz clock to WLAN is supplied from Phoenix TWL6030.
The 32KHz clock state (ON/OFF) is configured in CLK32KG_CFG_[GRP, TRANS, STATE]
register. This follows the same register programming model as other regulators
in TWL6030. So add CLK32KG as pseudo regulator.
Signed-off-
In Blaze and Panda, 32KHz clock - CLK32KG to WLAN is supplied
from Phoenix TWL6030.
Add CLK32KG platform data to blaze and omap4panda board file.
This patch has dependency on :-
[PATCH 1/2] regulator: twl: add clk32kg to twl-regulator
Signed-off-by: Balaji T K
---
arch/arm/mach-omap2/board-4430
On Wed, Feb 09, 2011 at 09:07:25PM +0530, Balaji T K wrote:
> - TWL6030_FIXED_LDO(VUSB, 0x70, 3300, 18, 0, 0x21)
> + TWL6030_FIXED_LDO(VUSB, 0x70, 3300, 18, 0, 0x21),
> + TWL6030_FIXED_LDO(CLK32KG, 0x8C, 1000, 48, 0, 0x21),
It'd seem better to implement a version of this that just doe
On Wed, Feb 09, 2011 at 09:07:31PM +0530, Balaji T K wrote:
> + .constraints = {
> + .valid_modes_mask = REGULATOR_MODE_NORMAL
> + | REGULATOR_MODE_STANDBY,
> + .valid_ops_mask = REGULATOR_CHANGE_MODE
> +
Vishwanath Sripathy writes:
>> This needs a comment to, but I'm not sure I understand what's going on
>> here. What it seems like:
>>
>> if this device has no OPP for this voltage, just silently move on to the
>> next device? doesn't seem quite right, but not sure I fully grok the
>> failure m
On Wed, 9 Feb 2011, Dave Martin wrote:
> 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.
* Santosh Shilimkar [110209 01:59]:
> > From: Dave Martin [mailto:dave.mar...@linaro.org]
> >
> > You could also have a "v7+" unified kernel -- i.e., supporting
> > OMAP3+4+SMP.
> > This is what we currently do in Linaro, since we're focusing on v7
> > and above.
> >
> This sounds good way forward
> -Original Message-
> From: Kevin Hilman [mailto:khil...@ti.com]
> Sent: Wednesday, February 09, 2011 9:30 PM
> To: Vishwanath Sripathy
> Cc: linux-omap@vger.kernel.org; patc...@linaro.org; Thara Gopinath
> Subject: Re: [PATCH 03/13] OMAP: Implement Basic DVFS
>
> Vishwanath Sripathy writ
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Wednesday, February 09, 2011 9:54 PM
> To: Santosh Shilimkar
> Cc: Dave Martin; Nicolas Pitre; linux-omap@vger.kernel.org; Russell
> King - ARM Linux; linux-arm-ker...@lists.infradead.org
> Subject: Re: [PATCH 00/1
On Wed, Feb 09, 2011 at 08:24:21AM -0800, Tony Lindgren wrote:
> * Santosh Shilimkar [110209 01:59]:
> > > From: Dave Martin [mailto:dave.mar...@linaro.org]
> > >
> > > You could also have a "v7+" unified kernel -- i.e., supporting
> > > OMAP3+4+SMP.
> > > This is what we currently do in Linaro, s
On Wed, Feb 09, 2011 at 04:32:04PM +, Russell King - ARM Linux wrote:
> On Wed, Feb 09, 2011 at 08:24:21AM -0800, Tony Lindgren wrote:
> > * Santosh Shilimkar [110209 01:59]:
> > > > From: Dave Martin [mailto:dave.mar...@linaro.org]
> > > >
> > > > You could also have a "v7+" unified kernel --
On Wed, Feb 9, 2011 at 9:14 PM, Mark Brown
wrote:
> On Wed, Feb 09, 2011 at 09:07:25PM +0530, Balaji T K wrote:
>
>> - TWL6030_FIXED_LDO(VUSB, 0x70, 3300, 18, 0, 0x21)
>> + TWL6030_FIXED_LDO(VUSB, 0x70, 3300, 18, 0, 0x21),
>> + TWL6030_FIXED_LDO(CLK32KG, 0x8C, 1000, 48, 0, 0x21),
>
> I
On Wed, 9 Feb 2011, Russell King - ARM Linux wrote:
> On Wed, Feb 09, 2011 at 08:24:21AM -0800, Tony Lindgren wrote:
> > * Santosh Shilimkar [110209 01:59]:
> > > > From: Dave Martin [mailto:dave.mar...@linaro.org]
> > > >
> > > > You could also have a "v7+" unified kernel -- i.e., supporting
> >
On Wed, Feb 9, 2011 at 9:15 PM, Mark Brown
wrote:
> On Wed, Feb 09, 2011 at 09:07:31PM +0530, Balaji T K wrote:
>
>> + .constraints = {
>> + .valid_modes_mask = REGULATOR_MODE_NORMAL
>> + | REGULATOR_MODE_STANDBY,
>> + .valid_op
This patch set adds support for TI816X processor series. This series includes
DM8168, C6A816x and AM389x devices.
The details can be found at following links:
http://focus.ti.com/general/docs/gencontent.tsp?contentId=77960
http://www.ti.com/ww/en/dsp/davinci-netra/index.shtml
This series is arch
This patch updates the common platform files with TI816X support.
The approach taken in this patch is to add TI816X as part of OMAP3 variant where
the cpu class is considered as OMAP34XX and the type is TI816X. This means, both
cpu_is_omap34xx() and cpu_is_ti816x() checks return success on TI816X.
This patch updates the common machine specific source files with support for
TI816X.
The approach taken is to have TI816X only build for OMAP3 when
CONFIG_SOC_OMAPTI816X is defined.
Signed-off-by: Hemant Pedanekar
---
arch/arm/mach-omap2/clock3xxx_data.c |5 +++-
arch/arm/mach-oma
This patch adds minimal support and build configuration for TI816X EVM.
Signed-off-by: Hemant Pedanekar
---
arch/arm/mach-omap2/Kconfig |5 +++
arch/arm/mach-omap2/Makefile |1 +
arch/arm/mach-omap2/board-ti8168evm.c | 57 +
3 files ch
This patch adds support for low level debugging on TI816X boards. Currently the
support for UART3 console on TI816X EVM is added.
Signed-off-by: Hemant Pedanekar
---
arch/arm/mach-omap2/include/mach/debug-macro.S | 12
arch/arm/plat-omap/include/plat/serial.h |8
* Nicolas Pitre [110209 08:44]:
> On Wed, 9 Feb 2011, Russell King - ARM Linux wrote:
>
> > On Wed, Feb 09, 2011 at 08:24:21AM -0800, Tony Lindgren wrote:
> > > * Santosh Shilimkar [110209 01:59]:
> > > > > From: Dave Martin [mailto:dave.mar...@linaro.org]
> > > > >
> > > > > You could also have
* Mark Brown [110201 13:25]:
> On Tue, Feb 01, 2011 at 07:53:26PM +0200, Jarkko Nikula wrote:
>
> > Mark, Liam: is it ok if the 12/13 goes together with rest of the set
> > via linux-omap when ready?
>
> I already acked it.
OK assuming the next series is OK I'll queue it. Still need Paul's
ack
* Grant Erickson [110202 08:56]:
> On 2/1/11 2:32 PM, Tony Lindgren wrote:
> > * Grant Erickson [110128 16:34]:
>
> The long-term solution probably involves adding a function pointer member
> field for each machine description with a generic, default function that
> does something akin to the a
* Omar Ramirez Luna [110202 11:37]:
> Mailbox hwmod support for OMAP 2,3,4.
Hiroshi, any comments on these?
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
On Wed, Feb 9, 2011 at 8:08 AM, Gadiyar, Anand wrote:
> On Wed, Feb 9, 2011 at 7:25 PM, Raghuveer Murthy
> wrote:
>> Adding DVI support to OMAP4 PandaBoard.
>>
>> PandaBoard uses TFP410 DVI Framer chip
>> http://focus.ti.com/lit/ds/symlink/tfp410.pdf
>>
>> The TFP410 gets its power enable and dis
* Kevin Hilman [110204 14:27]:
> "Govindraj.R" writes:
>
> > Changes invloves:
> >
> > 1) Addition of hwmod data for omap2/3/4.
> > 2) McSPI driver hwmod adaptation with cleanup of base address
> >macros and using omap-device API's.
> > 3) Runtime Conversion of McSPI driver.
* Uwe Kleine-König [110208 01:58]:
> On Thu, Feb 03, 2011 at 09:15:08AM +0100, Uwe Kleine-König wrote:
> > Hey Tony,
> >
> > this patch below is now 4 months old and I didn't get any feedback.
> > (Though I
> > somehow missed to cc linux-omap@vger.kernel.org before, sorry for that.)
Sorry I mu
These are only called from omap_nokia770_init which is in .init.text, too.
Signed-off-by: Uwe Kleine-König
---
arch/arm/mach-omap1/board-nokia770.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap1/board-nokia770.c
b/arch/arm/mach-omap1/board-noki
All callers of these functions live in .init.text, so these can go there,
too. There they must not be exported anymore, this is no problem though,
as all callers are always built-in.
Signed-off-by: Uwe Kleine-König
---
arch/arm/plat-omap/common.c |6 ++
arch/arm/plat-omap/in
This variable is only assigned in __init functions and never used later.
Signed-off-by: Uwe Kleine-König
---
arch/arm/plat-omap/common.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm/plat-omap/common.c b/arch/arm/plat-omap/common.c
index 30c698e..d9f10a3 1
after these changes omap1_defconfig and omap2plus_defconfig don't have any
section mismatches any more, making it plausible that the patches earlier
in this series are OK.
Signed-off-by: Uwe Kleine-König
---
arch/arm/mach-omap1/board-ams-delta.c |4 ++--
arch/arm/mach-omap1/board-fsample.c
On Mon, 31 Jan 2011, Kishon Vijay Abraham I wrote:
> Adds a structure member 'name' to 'omap_hwmod_addr_space' structure.
> The drivers can use platform_get_resource_byname() to get resource of
> type 'IORESOURCE_MEM' by name so that it need not rely on the order to get
> the proper resource.
>
>
* Tony Lindgren [110209 11:26]:
> * Uwe Kleine-König [110208 01:58]:
>
> > > There are two more patches in this thread that are not yet
> > > applied/commented. Should I resend?
Thanks Uwe, I've applied them into devel-cleanup branch for the
next merge window.
Regards,
Tony
--
To unsubscribe
On Wed, Feb 9, 2011 at 1:07 PM, Robert Nelson wrote:
> On Wed, Feb 9, 2011 at 8:08 AM, Gadiyar, Anand wrote:
>> On Wed, Feb 9, 2011 at 7:25 PM, Raghuveer Murthy
>> wrote:
>>> Adding DVI support to OMAP4 PandaBoard.
>>>
>>> PandaBoard uses TFP410 DVI Framer chip
>>> http://focus.ti.com/lit/ds/sym
Hi,
* Hemant Pedanekar [110209 08:54]:
>
> 1) Multi-OMAP build with CONFIG_SOC_OMAPTI816X: The kernel built only for
> TI816X OMAP3 SoCs along with any other OMAP2/4 (e.g., OMAP4s). May not boot
> on other OMAP3 SoCs.
This option does not sound right. For the multi-omap builds we need to hav
* Hemant Pedanekar [110209 08:54]:
> --- a/arch/arm/mach-omap2/io.c
> +++ b/arch/arm/mach-omap2/io.c
> @@ -121,6 +121,16 @@ static struct map_desc omap243x_io_desc[] __initdata = {
> #endif
>
> #ifdef CONFIG_ARCH_OMAP3
> +#ifdef CONFIG_SOC_OMAPTI816X
> +static struct map_desc omap34xx_io
* Tony Lindgren [110209 17:45]:
>
> We should just have separate struct map_desc omapti816x_io_desc[] then.
> Maybe have a common struct map_desc omap3_io_desc[] and then separate
> omap3xxx_io_desc and omapti816x_io_desc?
Oh and this will work just fine for map_io without having cpu_is_omap
mac
* Felipe Balbi [110203 02:20]:
> Hi Tony,
>
> When you have some extra time, could you run these on N810
> to check whether I'm on the right path ? After these patches
> all CBUS drivers are using standard request_threaded_irq()
> calls. It's one step closer into getting those in mainline.
Cool
Tony Lindgren wrote on Thursday, February 10, 2011 7:18 AM:
> * Tony Lindgren [110209 17:45]:
>>
>> We should just have separate struct map_desc omapti816x_io_desc[] then.
>> Maybe have a common struct map_desc omap3_io_desc[] and then separate
>> omap3xxx_io_desc and omapti816x_io_desc?
>
> Oh
On Thu, Feb 3, 2011 at 12:57 AM, Omar Ramirez Luna wrote:
> Mailbox hwmod support for OMAP 2,3,4.
>
> This was tested on OMAP3 (3430, 3630), minor testing
> was made on OMAP4.
>
> No testing on OMAP2 since I don't have the hardware.
>
> Highlights from v5 include the comments received from
> previ
From: ext Tony Lindgren
Subject: Re: [PATCH v5 0/5] omap: mailbox: hwmod support
Date: Wed, 9 Feb 2011 10:32:19 -0800
> * Omar Ramirez Luna [110202 11:37]:
>> Mailbox hwmod support for OMAP 2,3,4.
>
> Hiroshi, any comments on these?
Well, I haven't followed hwmod much. If Kevin is ok, ok for m
On Mon, 31 Jan 2011, Sumit Semwal wrote:
> Currently, clock database has tuples for DSS2. Because of
> this, the clock names are different across different OMAP platforms.
>
> This patch aligns the DSS2 clock names and roles across OMAP 2420, 2430, 3xxx,
> 44xx platforms in the clock databases,
Hi!
I am not able to find linux-omap tree on git.kernel.org.
But linux-omap-pm is present.
Something might have gone wrong while maintaining the tree.
Is there any other place where the tree is being mirrored?
-Thanks,
Mayuresh
--
To unsubscribe from this list: send the line "unsubscribe linux-
Mayuresh,
Can you try this link:
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git
Regards,
Keerthy
On Thu, Feb 10, 2011 at 11:57 AM, Janorkar, Mayuresh wrote:
> Hi!
>
> I am not able to find linux-omap tree on git.kernel.org.
> But linux-omap-pm is present.
>
> Something migh
Thanks Keerthy that link is working fine.
My concern was that on git.kernel.org (Main Page) I am unable to find
linux-omap.
-Thanks,
Mayuresh
> -Original Message-
> From: J, KEERTHY
> Sent: Thursday, February 10, 2011 12:13 PM
> To: Janorkar, Mayuresh
> Cc: linux-omap@vger.kernel.org
>
On Thu, Feb 10, 2011 at 13:18, Janorkar, Mayuresh wrote:
> Thanks Keerthy that link is working fine.
>
> My concern was that on git.kernel.org (Main Page) I am unable to find
> linux-omap.
>
http://git.kernel.org/?s=omap -> viola Linux-omap is there
http://git.kernel.org/?s=linux-omap -> linux-om
64 matches
Mail list logo
