Hi,
This a preamble patch series for McBSP support on OAMP34xx. it adds few
register definitions and and base addresses for all the McBSP instances.
It also modifies read/write functions to do 16/32 ops depending on CPU.
It doesn't add any functionality.
Regards,
Chandra Shekhar
--
To
Hi,
This Patch adds base address for all the instances on OMAP34xx and defines some
relevant register.
It also populates McBSP structure for all the instances for 34xx.
Regards,
Chandra Shekhar
Signed-off-by: Chandra Shekhar [EMAIL PROTECTED]
---
arch/arm/mach-omap2/mcbsp.c | 53
Hi,
this patch modifies the read write function to do
16/32 bit read write depending on CPU.
Regards,
Chandra Shekhar
Signed-off-by: Chandra Shekhar [EMAIL PROTECTED]
---
arch/arm/mach-omap1/mcbsp.c |1 +
arch/arm/mach-omap2/mcbsp.c |3 +++
arch/arm/plat-omap/mcbsp.c
* David Brownell [EMAIL PROTECTED] [080808 03:37]:
On Thursday 07 August 2008, chandra shekhar wrote:
This patch is to fix I2C transmit overflow error.
I guess it should fix the OSK5912 error. I dont have the board to test it.
Yes, it makes those error reports go away.
I'd say to merge
Hi,
* chandra shekhar [EMAIL PROTECTED] [080808 09:07]:
Hi,
this patch modifies the read write function to do
16/32 bit read write depending on CPU.
Regards,
Chandra Shekhar
Signed-off-by: Chandra Shekhar [EMAIL PROTECTED]
---
arch/arm/mach-omap1/mcbsp.c |1 +
===
--- linux-omap-2.6.orig/arch/arm/plat-omap/mcbsp.c 2008-08-07
16:39:51.0 +0530
+++ linux-omap-2.6/arch/arm/plat-omap/mcbsp.c 2008-08-07
16:45:00.0 +0530
@@ -29,9 +29,31 @@
struct omap_mcbsp **mcbsp_ptr;
* shekhar, chandra [EMAIL PROTECTED] [080808 09:52]:
===
--- linux-omap-2.6.orig/arch/arm/plat-omap/mcbsp.c 2008-08-07
16:39:51.0 +0530
+++ linux-omap-2.6/arch/arm/plat-omap/mcbsp.c 2008-08-07
16:45:00.0 +0530
On Thu, Aug 07, 2008 at 06:07:50PM -0500, Woodruff, Richard wrote:
If I write a series of control register commands to device A, then
write a go operation to device B, I would hope all of A's writes
had completed before B gets the go. SO gives you this. DEVICE may
not with out barriers.
Hi,
Resending Patch after fixing tony's comments.
this patch modifies the read write function to do
16/32 bit read write depending on CPU.
Regards,
Chandra Shekhar
Signed-off-by: Chandra Shekhar [EMAIL PROTECTED]
---
arch/arm/plat-omap/mcbsp.c| 23 ++-
* David Brownell [EMAIL PROTECTED] [080808 02:51]:
On Thursday 07 August 2008, Jean Delvare wrote:
Still no testers for these patches?
Right now I don't seem to be able to boot OMAP1 in mainline,
so pulling that H2 out of its box would be futile. :(
Grr, looks like I can't access my H2
* Premi, Sanjeev [EMAIL PROTECTED] [080806 15:03]:
For 35x processors we need to make compile time decisions to exlude the code
that may not be applicable for the specifc processor e.g. excluding the code
applicable for DSP/ SGX or both depending upon the exact part number.
This continuous
* Madhusudhan Chikkature [EMAIL PROTECTED] [080808 07:14]:
From: Madhusudhan Chikkature[EMAIL PROTECTED]
ARM: OMAP3: Fixes required to make HSMMC driver work as module.Complete the
previously applied patch.
This patch provides the necessary fixes to make the HSMMC driver work as
loadble
* Arun KS [EMAIL PROTECTED] [080806 14:19]:
This patch enables high speed MMC support for OMAP2EVM board
Pushing today.
Tony
Signed-off-by: Arun KS [EMAIL PROTECTED]
---
arch/arm/mach-omap2/Makefile |3 ++-
arch/arm/mach-omap2/board-omap2evm.c | 10 ++
2 files
* Arun KS [EMAIL PROTECTED] [080806 14:25]:
Update omap2evm defconfig
- Enable hsmmc support.
Pushing today.
Tony
Signed-off-by: Arun KS [EMAIL PROTECTED]
---
arch/arm/configs/omap2_evm_defconfig | 22 +++---
1 files changed, 19 insertions(+), 3 deletions(-)
diff
The musb code currently kills the SH randconfig build (and this will hose
any platform that also selects HAVE_CLK -- a PPC or AVR32 randconfig
would have also hit this eventually), as can be seen here:
http://kisskb.ellerman.id.au/kisskb/buildresult/41095/
This initial failure comes from the
On Thu, 7 Aug 2008, Catalin Marinas wrote:
Many of the architecture people in ARM seem to be on holiday, I'll try
to get clarification in about a week time.
That would be really great. For reference, here is the assembly code in
question:
* Adrian Hunter [EMAIL PROTECTED] [080806 09:52]:
I have split the patch into 3 patches, tidied up drivers/mtd/onenand/omap2.c
ready to be sent to MTD (which I will do shortly), and made multi-omap changes
Thanks. I'll push these to l-o tree today.
Tony
--
To unsubscribe from this list: send
On Fri, Aug 08, 2008 at 11:32:45AM +0300, Felipe Balbi wrote:
other users. Why this driver isn't using ioread/writeXX_rep() is beyond
I'll try to fix io routines asap. From your next mail I could see that
it's really bogus :-p
drivers/usb/musb/musb_core.c: In function 'fifo_setup':
* Paul Walmsley [EMAIL PROTECTED] [080808 11:57]:
GPTIMER12 IRQ is at IRQ 95 on OMAP3, unlike OMAP2. (ref: OMAP34xx
Multimedia High Security (HS) Device Silicon Revision 3.0 Security
Addendum Rev. B, SWPU119B)
That probably explains why it did not work earlier :) Pushing today.
Tony
On Fri, Aug 08, 2008 at 12:04:45PM +0300, Felipe Balbi wrote:
On Fri, Aug 08, 2008 at 11:32:45AM +0300, Felipe Balbi wrote:
other users. Why this driver isn't using ioread/writeXX_rep() is beyond
I'll try to fix io routines asap. From your next mail I could see that
it's really bogus :-p
* David Brownell [EMAIL PROTECTED] [080808 02:51]:
On Thursday 07 August 2008, Tony Lindgren wrote:
Two problems on the OSK5912:
- cpufreq oopses on boot
- continuous i2c overflow errors
ISTR both of these bugs are in mainline too. I'd say the
I2C regression is higher
On Thu, 2008-08-07 at 22:20 +0100, Russell King - ARM Linux wrote:
On Thu, Aug 07, 2008 at 03:38:55PM -0500, Woodruff, Richard wrote:
From: Russell King - ARM Linux [mailto:[EMAIL PROTECTED]
Is DEVICE really safe for things other than FIFOs with out the use of
barriers?
As far
On Fri, Aug 08, 2008 at 12:44:49PM +0100, Catalin Marinas wrote:
There are already CPUs with weaker memory ordering model than ARM (e.g.
Alpha) and they are supported by Linux. Of course, there may be problems
with drivers since most of them are developed in x86.
There are, and they are
On Thursday 07 August 2008, Tony Lindgren wrote:
* David Brownell [EMAIL PROTECTED] [080808 03:37]:
On Thursday 07 August 2008, chandra shekhar wrote:
This patch is to fix I2C transmit overflow error.
I guess it should fix the OSK5912 error. I dont have the board to test it.
Yes, it
As I commented in
http://marc.info/?l=linux-omapm=121792042504348w=2
I can't quite see why anything is using omap_mmc_config for
anything related to hsmmc ... it contains two structs that
don't match what the hsmmc driver understands.
- Dave
@@ -83,9 +84,17 @@ static struct
25 matches
Mail list logo
