Re: [PATCH v4 3/3] wlcore/wl12xx: spi: add wifi support to cm-t335
Uri Mashiach <uri.mashi...@compulab.co.il> writes: > Device tree modifications: > - Pinmux for SPI0 and WiFi GPIOs. > - SPI0 node with wlcore as a child node. > > Cc: Tony Lindgren <t...@atomide.com> > Signed-off-by: Uri Mashiach <uri.mashi...@compulab.co.il> > --- > v1 -> v2: Replace interrupts and interrupt-parent with interrupts-extended. > v2 -> v3: Move the pinctrl-0 = <_pins> to the wlcore node. > v3 -> v4: replace interrupts-extended with interrupts and interrupt-parent. > (revert v2 modification). > According to Rob Herring and > Documentation/devicetree/bindings/interrupt-controller/interrupts.txt, > interrupts-extended should only be used when a device has multiple > interrupt parents. > > arch/arm/boot/dts/am335x-cm-t335.dts | 55 > > 1 file changed, 55 insertions(+) To what tree should this patch go? My wireless-drivers-next tree doesn't even have this file. https://patchwork.kernel.org/patch/7933441/ -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH v7 5/6] ARM: dts: add wl12xx/wl18xx bindings
Tony Lindgren t...@atomide.com writes: After John retired we actually have two set of trees now: mac80211 maintained by Johannes and wireless-drivers maintained by me. I haven't pulled anything from your tree and I'm 100% sure Johannes hasn't either. So green light from me. OK, I'll set up the new branch then. I take your ack is for the whole series? If it's just for the $subject patch, please let me know. It was for the whole series. -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH v7 5/6] ARM: dts: add wl12xx/wl18xx bindings
Tony Lindgren t...@atomide.com writes: Tested OK (boot, scan, join, ping) on Pandaboard ES. thanks for testing it! Great. As suggested by Kalle, I'll apply all these into omap-for-v4.1/wl12xx branch and send a pull request for the arm-soc probably on Friday if no issues are found. Great, thank you. Just in case you want this: Acked-by: Kalle Valo kv...@codeaurora.org -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH v6 2/6] wl12xx: use frequency instead of enumerations for pdata clocks
Tony Lindgren t...@atomide.com writes: I prefer these going through the omap tree. Like Eliad said, drivers/net/wireless/ti does not get that many changes nowadays so the chances of this patchset conflicting with something is very small. OK great. In that case no need to rearrange the patches, I can apply them into an immutable branch once the pending issues have been fixed if Kalle acks them. To avoid merge conflicts that branch is easiest done against v4.0-rc4. Kalle and Arnd, does that work for you guys? I can also base it on 5b7610f23562 (ARM: OMAP2+: Fix wl12xx on dm3730-evm with mainline u-boot) that's on top of -rc2 plus few other fixes now merged to -rc4 mainline if we need a branch based on an earlier tag. Sorry, it seems I forgot to answer this one: Either baseline is good for me, I can't think of any problems with either one. But please do remember that I'm a new maintainer, I might very well miss something ;) -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH v7 5/6] ARM: dts: add wl12xx/wl18xx bindings
Tony Lindgren t...@atomide.com writes: * Kalle Valo kv...@codeaurora.org [150319 23:04]: Tony Lindgren t...@atomide.com writes: Tested OK (boot, scan, join, ping) on Pandaboard ES. thanks for testing it! Great. As suggested by Kalle, I'll apply all these into omap-for-v4.1/wl12xx branch and send a pull request for the arm-soc probably on Friday if no issues are found. Great, thank you. Just in case you want this: Acked-by: Kalle Valo kv...@codeaurora.org Thanks, I can push out a new branch omap-for-v4.1/wl12xx-v2 with your acks assuming you or somebody else have not merged the existing omap-for-v4.1/wl12xx branch yet into the wireless tree? In that case I can scrap omap-for-v4.1/wl12xx and then will reply with a commit that we can consider immutable that can be merged into various trees as needed in case of merge conflicts. But I'll wait for your confirmation first :) After John retired we actually have two set of trees now: mac80211 maintained by Johannes and wireless-drivers maintained by me. I haven't pulled anything from your tree and I'm 100% sure Johannes hasn't either. So green light from me. -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH v6 2/6] wl12xx: use frequency instead of enumerations for pdata clocks
Arnd Bergmann a...@arndb.de writes: On Sunday 15 March 2015 10:43:35 Eliad Peller wrote: The other option would be to have the whole series in a immutable branch against v3.0-rc1 that can be merged into both wirelss tree and omap tree. i think that could be easier. or maybe you can just take them all through the omap tree? the wlcore tree is not under active development, so i don't expect conflicts there. I'm fine with both these approaches. I prefer these going through the omap tree. Like Eliad said, drivers/net/wireless/ti does not get that many changes nowadays so the chances of this patchset conflicting with something is very small. -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH] board-n8x0: add USB initialization
Francisco Alecrim alec...@gmail.com writes: Hi Kalle, Hi again Francisco, On Sun, Feb 28, 2010 at 2:57 PM, Kalle Valo kalle.v...@iki.fi wrote: Please do not add my Signed-off-by unless I have explicitly added it. And I don't recall giving it to this patch, so it can be removed. I got the initial code from http://www.valot.fi/kalle/n8x0/patches/n8x0-add/ 2009-07-31-12:15/07-n8x0-add-usb-support.patch . I just re-organized some variables. So I didn't remove your Signed-off-by. Hehe, I had totally forgotten that patch! Sorry :) And I merged your patch to Tony's code http://www.mail-archive.com/ linux-omap@vger.kernel.org/msg21443.html . So I kept his Signed-off-by. [...] Sorry! I was not sure about keep or not these Signed-off-by. Do you want me to re-send it without your Signed-off-by? No, this was my mistake. Please don't remove the Signed-off-by line. But when you improve a patch originally implemented by somene else it's a good practise to mention the history of the patch. For example, Based on Kalle's and Tony's patches, or something like that, is enough IMHO. -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH] board-n8x0: add USB initialization
Hi Francisco, Francisco Alecrim alec...@gmail.com writes: From: Francisco Alecrim francisco.alec...@openbossa.org Signed-off-by: Kalle Valo kalle.v...@iki.fi Signed-off-by: Francisco Alecrim francisco.alec...@openbossa.org Signed-off-by: Tony Lindgren t...@atomide.com Please do not add my Signed-off-by unless I have explicitly added it. And I don't recall giving it to this patch, so it can be removed. Removing the line doesn't change anything from technical point of view, this is just a little bit of legalise we have to deal with. -- Kalle Valo -- 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/majordomo-info.html
regression: crash from 'ls /sys/modules/wl1251_spi/notes'
Hello, I noticed weird crashes related to wl1251_spi notes sysfs directory with current wireless-testing (2.6.33-rc2 plus some wireless patches). The simplest way to reproduce the problem is to do this on a nokia n900 (arm/omap 3430): # ls /sys/module/wl1251_spi/notes/ [ 4776.503234] Unable to handle kernel NULL pointer dereference at virtual address [ 4776.511596] pgd = cce88000 [ 4776.514343] [] *pgd=8f04a031, *pte=, *ppte= [ 4776.520812] Internal error: Oops: 17 [#1] [ 4776.524871] last sysfs file: /sys/class/net/wlan0/flags [ 4776.530151] Modules linked in: wl1251_spi wl1251 mac80211 cfg80211 [ 4776.536468] CPU: 0Not tainted (2.6.33-rc2-wl-47091-g981eb84 #12) [ 4776.542999] PC is at strlen+0xc/0x20 [ 4776.546630] LR is at sysfs_readdir+0x15c/0x1e0 [ 4776.551116] pc : [c01476ac]lr : [c00f5e6c]psr: a013 [ 4776.551147] sp : cce87f28 ip : fp : be99961c [ 4776.562744] r10: cce87f80 r9 : r8 : [ 4776.568023] r7 : c00b9540 r6 : cce87f80 r5 : ccec4458 r4 : ce808980 [ 4776.574615] r3 : r2 : 0002 r1 : r0 : [ 4776.581207] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 4776.588409] Control: 10c5387d Table: 8ce88019 DAC: 0015 [ 4776.594238] Process ls (pid: 1148, stack limit = 0xcce862e8) [ 4776.599945] Stack: (0xcce87f28 to 0xcce88000) [ 4776.604370] 7f20: 0001 0e16 0004 [ 4776.612640] 7f40: ce808980 ce808980 cf79e34c c00b9540 cf79e2b8 cce86000 c00b982c [ 4776.620910] 7f60: 0001 1000 000690d0 ce808980 c002bae4 c00b98c4 [ 4776.629180] 7f80: 00069100 000690e8 0fd0 ffea [ 4776.637451] 7fa0: 00d9 c002b940 0003 000690d0 1000 [ 4776.645721] 7fc0: 00d9 000690c8 0001 be99961c [ 4776.654022] 7fe0: 400ef954 be999614 400efa10 400ef908 6010 0003 80c69021 80c69421 [ 4776.662292] [c01476ac] (strlen+0xc/0x20) from [c00f5e6c] (sysfs_readdir+0x15c/0x1e0) [ 4776.670501] [c00f5e6c] (sysfs_readdir+0x15c/0x1e0) from [c00b982c] (vfs_readdir+0x80/0xb4) [ 4776.679229] [c00b982c] (vfs_readdir+0x80/0xb4) from [c00b98c4] (sys_getdents64+0x64/0xb4) [ 4776.687866] [c00b98c4] (sys_getdents64+0x64/0xb4) from [c002b940] (ret_fast_syscall+0x0/0x38) [ 4776.696838] Code: c027700c e1a03000 ea00 e2833001 (e5d32000) [ 4776.703063] ---[ end trace 6a3b0fdf4e9def99 ]--- [ 4776.707794] Kernel panic - not syncing: Fatal exception Also removing wl1251_spi causes a crash. The reason for this is that a sysfs file with a null string as name is trying to be removed from the notes directory. I found out that reverting this patch solves the problem: commit 35dead4235e2b67da7275b4122fed37099c2f462 Author: Helge Deller del...@gmx.de Date: Thu Dec 3 00:29:15 2009 +0100 modules: don't export section names of empty sections via sysfs On the parisc architecture we face for each and every loaded kernel module this kernel badness warning: sysfs: cannot create duplicate filename '/module/ac97_bus/sections/.text' Badness at fs/sysfs/dir.c:487 Reason for that is, that on parisc all kernel modules do have multiple .text sections due to the usage of the -ffunction-sections compiler flag which is needed to reach all jump targets on this platform. An objdump on such a kernel module gives: Sections: Idx Name Size VMA LMA File off Algn 0 .note.gnu.build-id 0024 0034 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 1 .text 0058 2**0 CONTENTS, ALLOC, LOAD, READONLY, CODE 2 .text.ac97_bus_match 001c 0058 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 3 .text 00d4 2**0 CONTENTS, ALLOC, LOAD, READONLY, CODE ... Since the .text sections are empty (size of 0 bytes) and won't be loaded by the kernel module loader anyway, I don't see a reason why such sections need to be listed under /sys/module/module_name/sections/section_name either. The attached patch does solve this issue by not exporting section names which are empty. This fixes bugzilla http://bugzilla.kernel.org/show_bug.cgi?id=14703 Signed-off-by: Helge Deller del...@gmx.de CC: ru...@rustcorp.com.au CC: a...@linux-foundation.org CC: james.bottom...@hansenpartnership.com CC: rol...@redhat.com CC: d...@hiauly1.hia.nrc.ca Signed-off-by: Linus Torvalds torva...@linux-foundation.org I was also able to reproduce the problem with vanilla 2.6.32. I'm pretty sure (but haven't tested) that 2.6.32-rc8 does not have this problem. My
Re: regression: crash from 'ls /sys/modules/wl1251_spi/notes'
James Bottomley james.bottom...@hansenpartnership.com writes: On Wed, 2009-12-30 at 13:41 +0200, Kalle Valo wrote: Also removing wl1251_spi causes a crash. The reason for this is that a sysfs file with a null string as name is trying to be removed from the notes directory. Yes, this is because the notes sections describe the text sections. When we ignore an empty text section, we'd need to ignore its corresponding notes section. The reason we didn't see this on parisc is because our compiler doesn't actually produce any notes sections. Also on omap not all modules can reproduce the problem. For example cfg80211, mac80211 and wl1251 modules work just fine, but with wl1251_spi I see the problem everytime. A better, and more comprehensive patch would be to try not to count the empty text sections when we're building the notes section (and actually anywhere else in the file). This patch actually relies on the fact that if sh_size is zero for the text section it should be for the corresponding notes section. If that doesn't work, we'd actually have to do the matching in the construction piece. Can you try it to see if it works for you? If it doesn't, I'll try matching notes to text. It works fine on parisc, but as we don't have a notes section, that's not saying much ... Thanks. I tested the patch on my setup, this time on top of Linus' tree (commit 6b7b284). And the patch fixes the issue, I can't reproduce the problem at all, both 'rmmod wl1251_spi' and ls work without any problems. So here's my tested-by: Tested-by: Kalle Valo kalle.v...@iki.fi Also please consider sending the fix to stable. Thank you for fixing this so fast. -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH] OMAP2: add USB platform data and initialization for Nokia N800 and N810
Luke-Jr l...@dashjr.org writes:
Add platform data and initialization for USB on Nokia N800 and N810 devices
via the TUSB6010 chipset.
Excellent, thank you for doing this.
Tested on Nokia N810 in Linux-OMAP tree. Mainline is not bootable yet.
What's the problem in mainline? I haven't tested n8x0 for months :(
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -117,6 +117,11 @@ config MACH_NOKIA_N8X0
select MACH_NOKIA_N810
select MACH_NOKIA_N810_WIMAX
+config MACH_NOKIA_N8X0_USB
+ bool
+ depends on MACH_NOKIA_N8X0 MACH_OMAP2_TUSB6010
+ default y
+
Is is really needed to add new kconfig variable? Can't we just use
MACH_OMAP2_TUSB6010 in code?
--- /dev/null
+++ b/arch/arm/mach-omap2/board-n8x0-usb.c
I think a separate file is not needed, it's not that much code. I
recommend to just adding it directly to board-n8x0.c. It's simple and
easier for everyone.
--- a/arch/arm/mach-omap2/board-n8x0.c
+++ b/arch/arm/mach-omap2/board-n8x0.c
@@ -109,8 +109,16 @@ static void __init n8x0_init_irq(void)
omap_gpio_init();
}
+#ifdef CONFIG_MACH_NOKIA_N8X0_LCD
+extern void n8x0_usb_init(void);
+#else
+static inline void n8x0_usb_init (void) {}
+#endif
CONFIG_MACH_NOKIA_N8X0_LCD does not look right here.
--
Kalle Valo
--
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/majordomo-info.html
Re: [PATCH] OMAP2: add USB platform data and initialization for Nokia N800 and N810
Luke-Jr l...@dashjr.org writes: On Tuesday 29 December 2009 02:29:22 am Kalle Valo wrote: Luke-Jr l...@dashjr.org writes: Tested on Nokia N810 in Linux-OMAP tree. Mainline is not bootable yet. What's the problem in mainline? I haven't tested n8x0 for months :( Lack of platform support, as far as I know. Until we have cbus, there's no way to get the LCD powered... Oh that. I have only used serial console with mainline. Luckily Felipe did some cbus patches, I haven't checked them yet though. I think a separate file is not needed, it's not that much code. I recommend to just adding it directly to board-n8x0.c. It's simple and easier for everyone. Seemed simpler to manage in a separate file Having lots of small files is difficult IMHO. though not as necessary as the LCD stuff (which I also have a patch against mainline for, but it needs tahvo...) Nice. CONFIG_MACH_NOKIA_N8X0_LCD does not look right here. Heh, looks like my isolate-and-merge-to-mainline got messed up there. Of course it should be CONFIG_MACH_NOKIA_N8X0_USB :) Yeah, maybe eating too much ham caused it ;) Also, scripts/checkpatch.pl gave me a warning about the extern in a .c file, but I couldn't figure out where else it could reasonably go. Any ideas? :/ Yes, just put everything into one file :) No need for externs then. -- Kalle Valo -- 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/majordomo-info.html
wl1251: crash in /sys/module/wl1251_spi/notes
c00b9598 cf7a82b8 cd1a c00b9884 [ 3823.991302] 1f60: 0001 1000 000690d0 cf398d80 c002bae4 c00b991c [ 3823.999572] 1f80: 00069100 000690e8 0fd0 ffea [ 3824.007843] 1fa0: 00d9 c002b940 0003 000690d0 1000 [ 3824.016113] 1fc0: 00d9 000690c8 0001 bef3760c [ 3824.024383] 1fe0: 400ef954 bef37604 400efa10 400ef908 6010 0003 1802 0005e91c [ 3824.032684] [c014772c] (strlen+0xc/0x20) from [c00f5ec4] (sysfs_readdir+0x15c/0x1e0) [ 3824.040893] [c00f5ec4] (sysfs_readdir+0x15c/0x1e0) from [c00b9884] (vfs_readdir+0x80/0xb4) [ 3824.049591] [c00b9884] (vfs_readdir+0x80/0xb4) from [c00b991c] (sys_getdents64+0x64/0xb4) [ 3824.058258] [c00b991c] (sys_getdents64+0x64/0xb4) from [c002b940] (ret_fast_syscall+0x0/0x38) [ 3824.067230] Code: c02770d4 e1a03000 ea00 e2833001 (e5d32000) [ 3824.073455] ---[ end trace 7191ebb2793d480e ]--- [ 3824.078186] Kernel panic - not syncing: Fatal exception -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH] OMAP2: add USB platform data and initialization for Nokia N800 and N810
(dropping lkml) Luke-Jr l...@dashjr.org writes: I think 4 or 5 files with ~350 lines is more manageable than a single 1700- line board file, especially when considering that parts depend on multiple configuration options (LCD, which turns out to be a 128-line file, depends on 3 config options: N8x0, Blizzard, and MIPID). I tend to disagree. Scattering code to small files doesn't benefit that much, just makes it harder to find code. IMHO a 2k line file is perfectly acceptable and usable. But if you really want smaller files, I'm not going to object. You're the one doing the all work here :) -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH] OMAP2: add USB platform data and initialization for Nokia N800 and N810
Luke-Jr l...@dashjr.org writes: On that topic, is there a reason the newer code is under a unified N8x0 config option instead of the split N800/N810 that was used for the old code, or is that simply a symptom of the currently-supported features all being common? IIRC, I just used one common n8x0 file because the n810 board file was very small and I didn't see any benefit from having it separately. -- Kalle Valo -- 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/majordomo-info.html
[PATCH] omap3: rx51: Use wl1251 in SPI mode 3
From: Kalle Valo kalle.v...@nokia.com
Otherwise Extreme Lower Power (ELP) wakeup doesn't work properly.
Signed-off-by: Kalle Valo kalle.v...@nokia.com
---
arch/arm/mach-omap2/board-rx51-peripherals.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/board-rx51-peripherals.c
b/arch/arm/mach-omap2/board-rx51-peripherals.c
index 4f347f8..e66d728 100644
--- a/arch/arm/mach-omap2/board-rx51-peripherals.c
+++ b/arch/arm/mach-omap2/board-rx51-peripherals.c
@@ -59,7 +59,7 @@ static struct spi_board_info
rx51_peripherals_spi_board_info[] __initdata = {
.bus_num= 4,
.chip_select= 0,
.max_speed_hz = 4800,
- .mode = SPI_MODE_2,
+ .mode = SPI_MODE_3,
.controller_data= wl1251_mcspi_config,
.platform_data = wl1251_pdata,
},
--
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/majordomo-info.html
Re: Problem trying to pull particular commit from PM tree
Hi Kevin, Kevin Hilman khil...@deeprootsystems.com writes: 2) When trees are rebased, are the previous commits in the tree lost - i.e. if tree A has commits A', A'', etc, and is rebased on tree B(which does not have the commits A', A'' in it), are the commits A', A'', etc lost? When a branch is rebased, all the commit IDs in that branch change, so finding a change by commit ID in a rebased branch (like PM branch) is impossible. What you could do is to tag the branch (with a date or something) every time you rebase, that way git would store the old commits in the repo. But I doubt it would be worth the effort, but that's one way to store the history. Just my 0.02 EUR :) -- Kalle Valo -- 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/majordomo-info.html
[PATCH v2] rx51: add wl1251 wlan driver support
From: Kalle Valo kalle.v...@nokia.com
wl1251 is connected to the SPI bus in rx51, add support for this.
Signed-off-by: Kalle Valo kalle.v...@nokia.com
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 85 ++
1 files changed, 85 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-rx51-peripherals.c
b/arch/arm/mach-omap2/board-rx51-peripherals.c
index e34d96a..2417193 100644
--- a/arch/arm/mach-omap2/board-rx51-peripherals.c
+++ b/arch/arm/mach-omap2/board-rx51-peripherals.c
@@ -14,6 +14,7 @@
#include linux/input.h
#include linux/input/matrix_keypad.h
#include linux/spi/spi.h
+#include linux/spi/wl12xx.h
#include linux/i2c.h
#include linux/i2c/twl4030.h
#include linux/clk.h
@@ -36,6 +37,37 @@
#define SYSTEM_REV_B_USES_VAUX30x1699
#define SYSTEM_REV_S_USES_VAUX3 0x8
+#define RX51_WL1251_POWER_GPIO 87
+#define RX51_WL1251_IRQ_GPIO 42
+
+static void rx51_wl1251_set_power(bool enable);
+
+static struct wl12xx_platform_data wl1251_pdata = {
+ .set_power = rx51_wl1251_set_power,
+};
+
+static struct omap2_mcspi_device_config wl1251_mcspi_config = {
+ .turbo_mode = 0,
+ .single_channel = 1,
+};
+
+/* list all spi devices here */
+enum {
+ RX51_SPI_WL1251,
+};
+
+static struct spi_board_info rx51_peripherals_spi_board_info[] __initdata = {
+ [RX51_SPI_WL1251] = {
+ .modalias = wl1251,
+ .bus_num= 4,
+ .chip_select= 0,
+ .max_speed_hz = 4800,
+ .mode = SPI_MODE_2,
+ .controller_data= wl1251_mcspi_config,
+ .platform_data = wl1251_pdata,
+ },
+};
+
static int board_keymap[] = {
KEY(0, 0, KEY_Q),
KEY(0, 1, KEY_O),
@@ -257,6 +289,55 @@ static struct regulator_init_data rx51_vdac = {
},
};
+static void rx51_wl1251_set_power(bool enable)
+{
+ gpio_set_value(RX51_WL1251_POWER_GPIO, enable);
+}
+
+static void __init rx51_init_wl1251(void)
+{
+ int irq, ret;
+
+ ret = gpio_request(RX51_WL1251_POWER_GPIO, wl1251 power);
+ if (ret 0)
+ goto error;
+
+ ret = gpio_direction_output(RX51_WL1251_POWER_GPIO, 0);
+ if (ret 0)
+ goto err_power;
+
+ ret = gpio_request(RX51_WL1251_IRQ_GPIO, wl1251 irq);
+ if (ret 0)
+ goto err_power;
+
+ ret = gpio_direction_input(RX51_WL1251_IRQ_GPIO);
+ if (ret 0)
+ goto err_irq;
+
+ irq = gpio_to_irq(RX51_WL1251_IRQ_GPIO);
+ if (irq 0)
+ goto err_irq;
+
+ rx51_peripherals_spi_board_info[RX51_SPI_WL1251].irq = irq;
+
+ return;
+
+err_irq:
+ gpio_free(RX51_WL1251_IRQ_GPIO);
+
+err_power:
+ gpio_free(RX51_WL1251_POWER_GPIO);
+
+error:
+ printk(KERN_ERR wl1251 board initialisation failed\n);
+ wl1251_pdata.set_power = NULL;
+
+ /*
+* Now rx51_peripherals_spi_board_info[1].irq is zero and
+* set_power is null, and wl1251_probe() will fail.
+*/
+}
+
static int rx51_twlgpio_setup(struct device *dev, unsigned gpio, unsigned n)
{
/* FIXME this gpio setup is just a placeholder for now */
@@ -538,6 +619,10 @@ static inline void board_smc91x_init(void)
void __init rx51_peripherals_init(void)
{
+ rx51_init_wl1251();
+
+ spi_register_board_info(rx51_peripherals_spi_board_info,
+ ARRAY_SIZE(rx51_peripherals_spi_board_info));
rx51_i2c_init();
board_onenand_init();
board_smc91x_init();
--
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/majordomo-info.html
Re: [PATCH v2 2/2] omap: RX-51: enable tsc2005
Aaro Koskinen aaro.koski...@nokia.com writes: I sent a wl1251 patch which adds spi_board_info and conflicts with this patch: http://www.mail-archive.com/linux-omap@vger.kernel.org/msg17604.html How do we handle this? I can resend/rebase this patch once the wl1251 patch is integrated. Ok, thanks. I'll resend the wl1251 patch just to be sure that it doesn't get lost. BTW, check the comment from Tommi Rantala - spi_board_info can be marked with __initdata. I'll add it to my patch. -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH v2 2/2] omap: RX-51: enable tsc2005
Aaro Koskinen aaro.koski...@nokia.com writes:
Enable tsc2005 touchscreen driver on the RX-51 board.
Signed-off-by: Aaro Koskinen aaro.koski...@nokia.com
---
The patch is for 2.6.32-rc6.
[...]
+static struct spi_board_info rx51_peripherals_spi_board_info[] = {
+ [0] = {
+ .modalias = tsc2005,
+ .bus_num= 1,
+ .chip_select= 0,
+ .irq= OMAP_GPIO_IRQ(RX51_TSC2005_IRQ_GPIO),
+ .max_speed_hz = 600,
+ .controller_data= tsc2005_mcspi_config,
+ .platform_data = tsc2005_config,
+ },
+};
I sent a wl1251 patch which adds spi_board_info and conflicts with
this patch:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg17604.html
How do we handle this?
--
Kalle Valo
--
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/majordomo-info.html
Re: [PATCH] rx51: add wl1251 wlan driver support
Kalle Valo kalle.v...@iki.fi writes: From: Kalle Valo kalle.v...@nokia.com wl1251 is connected to the SPI bus in rx51, add support for this. Signed-off-by: Kalle Valo kalle.v...@nokia.com This is intended for 2.6.33. Also to really work it needs this patch: wl1251: rename spi device to wl1251 http://www.spinics.net/lists/linux-wireless/msg40740.html The patch should be in wireless-testing within next few days and finally it will go to 2.6.33. (Please note that the two patches have no compile time dependency so they can go to mainline via separate trees.) -- Kalle Valo -- 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/majordomo-info.html
Re: linux-omap git tree updated to v2.6.32-rc1, important changes, please read
Tony Lindgren t...@atomide.com writes: Please note that Remove omap extra version in Makefile commit means that you now need to set the ARCH and CROSS_COMPILE for your compiler. A handy tip is to create GNUmakefile containing this: ARCH=arm CROSS_COMPILE=arm-linux- include Makefile Now you can just write 'make' to compile the kernel as before. The tip is also here: http://elinux.org/N800#Simplify_make -- Kalle Valo -- 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/majordomo-info.html
Re: Any one is still using omap-kernel on N810???
Stefano Panella stefano.pane...@csr.com writes: Hi guys, Hello, I am new to linux-omap mailing list, I wrote a couple of emails yesterday but I did not get any response yet... Yeah, I saw them. I'm travelling right now and I'm quite slow to answer. Is there any one testing linux-omap on N810? I'm using it occasionally, although due to work I haven't had any spare time during the last few months. I'm trying to keep N800/N810 support in shape and add missing feature support to mainline. As anticipated, the progress is slow :) There's a wiki page which might help you: http://elinux.org/N800 I have got a N810 board and I am trying to install ubuntu on it. Is there any how-to or update instruction I can follow? I recommend installing Mer which is based on Ubuntu. The installation is very easy, but it will be more difficult to use latest kernels. My ultimate goal is to have Mer support latest kernels, let's see how it goes. Here's more information about Mer: http://wiki.maemo.org/Mer -- Kalle Valo -- 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/majordomo-info.html
Re: Any one is still using omap-kernel on N810???
Andy Shevchenko andy.shevche...@gmail.com writes: Is there any how-to or update instruction I can follow? Perhaps more useful to ask in maemo.org. In my opinion it's better to ask about mainline and linux-omap kernels here. In maemo.org people mostly use the old forked 2.6.21 kernel. -- Kalle Valo -- 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/majordomo-info.html
Re: Any one is still using omap-kernel on N810???
Stefano Panella stefano.pane...@csr.com writes: I am now trying to follow all the instructions from http://www.natisbad.org/N810/index.html Thanks, this is a good link. I added it to the n8x0 wiki page. but I am still having problems with the internal MMC card... Sorry, I know nothing about mmc and I currently don't have time to study it. But if you find a solution, please post it here. I'm sure others are also interested. -- Kalle Valo -- 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/majordomo-info.html
Re: Patch format for submission?
Jean Pihet jpi...@mvista.com writes: documentation, but its bit daunting bending my brain around git after many years of SVN/CVS. You can start with the Git tutorial [1] and Everyday Git [2]. The entry point for git documentation is at [3]. [1] http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html [2] http://www.kernel.org/pub/software/scm/git/docs/everyday.html [3] http://www.kernel.org/pub/software/scm/git/docs/git.html For SVN users this is also handy: http://git-scm.com/course/svn.html -- Kalle Valo -- 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/majordomo-info.html
Re: MUSB regression in 2.6.31-rc6
Jarkko Nikula jhnik...@gmail.com writes: By some reason CONFIG_OMAP_LL_DEBUG_UART3=y and CONFIG_DEBUG_LL=y don't work in mainline so hard to trace what is make an oops. You need to apply this patch manually: http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commitdiff;h=73e5b252eb179f601f2da2538ac3b70c21b2c6c2 -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH 8/9] OMAP2: add board file for Nokia N800 and N810
On Fri, Aug 14, 2009 at 2:08 PM, Tony Lindgrent...@atomide.com wrote:
+static struct musb_hdrc_platform_data tusb_data = {
+ .mode = BOARD_MODE,
+ .set_power = tusb_set_power,
+ .set_clock = tusb_set_clock,
+ .min_power = 25, /* x2 = 50 mA drawn from VBUS as peripheral */
+ .power = 100, /* Max 100 mA VBUS for host mode */
+ .clock = osc_ck,
Still passing clock names around?
Sorry, I'm not familiar with this. How should I fix it?
This should be fixed with the clkdev alias, see omap24xx_clks[].
But we need to check how the fix affects other platforms for
drivers/usb/musb/musb_core.c and send the patch via linux-usb.
Maybe take a quick look, and if it looks like a bigger change,
then leave out the tusb_data for now and let's do it in a separate
patch?
Thanks, I'll take a look.
Tony, do you want me to send v2?
Sure, it's best that you update it.
I'll send v2 later today.
Kalle
--
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/majordomo-info.html
Re: [PATCH 8/9] OMAP2: add board file for Nokia N800 and N810
Tony Lindgren t...@atomide.com writes: Still passing clock names around? Sorry, I'm not familiar with this. How should I fix it? This should be fixed with the clkdev alias, see omap24xx_clks[]. But we need to check how the fix affects other platforms for drivers/usb/musb/musb_core.c and send the patch via linux-usb. Maybe take a quick look, and if it looks like a bigger change, then leave out the tusb_data for now and let's do it in a separate patch? I'm not familiar enough the clock framework and right now I don't have enough time to study it properly. So I decided to remove tusb_data and also rest of the now unusable usb code from the board file. I'll send a v2 shortly. -- Kalle Valo -- 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/majordomo-info.html
[PATCH v2] OMAP2: add board file for Nokia N800 and N810
Add board file for Nokia N800 and N810 devices. Currently only serial ports,
onenand, spi and usb are configured, more to come later.
Tested on Nokia N800.
Signed-off-by: Kalle Valo kalle.v...@iki.fi
---
arch/arm/mach-omap2/Kconfig |4 +
arch/arm/mach-omap2/Makefile |2
arch/arm/mach-omap2/board-n8x0.c | 155 ++
3 files changed, 160 insertions(+), 1 deletions(-)
create mode 100644 arch/arm/mach-omap2/board-n8x0.c
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index bf54686..75b1c7e 100644
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -73,6 +73,10 @@ config MACH_OMAP_3430SDP
bool OMAP 3430 SDP board
depends on ARCH_OMAP3 ARCH_OMAP34XX
+config MACH_NOKIA_N8X0
+ bool Nokia N800/N810
+ depends on ARCH_OMAP2420
+
config MACH_NOKIA_RX51
bool Nokia RX-51 board
depends on ARCH_OMAP3 ARCH_OMAP34XX
diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile
index 757c84b..8850a24 100644
--- a/arch/arm/mach-omap2/Makefile
+++ b/arch/arm/mach-omap2/Makefile
@@ -62,7 +62,7 @@ obj-$(CONFIG_MACH_OMAP3_PANDORA) += board-omap3pandora.o
\
mmc-twl4030.o
obj-$(CONFIG_MACH_OMAP_3430SDP)+= board-3430sdp.o \
mmc-twl4030.o
-
+obj-$(CONFIG_MACH_NOKIA_N8X0) += board-n8x0.o
obj-$(CONFIG_MACH_NOKIA_RX51) += board-rx51.o \
board-rx51-peripherals.o \
mmc-twl4030.o
diff --git a/arch/arm/mach-omap2/board-n8x0.c b/arch/arm/mach-omap2/board-n8x0.c
new file mode 100644
index 000..813b57d
--- /dev/null
+++ b/arch/arm/mach-omap2/board-n8x0.c
@@ -0,0 +1,155 @@
+/*
+ * linux/arch/arm/mach-omap2/board-n8x0.c
+ *
+ * Copyright (C) 2005-2009 Nokia Corporation
+ * Author: Juha Yrjola juha.yrj...@nokia.com
+ *
+ * Modified from mach-omap2/board-generic.c
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+#include linux/clk.h
+#include linux/delay.h
+#include linux/gpio.h
+#include linux/init.h
+#include linux/io.h
+#include linux/stddef.h
+#include linux/spi/spi.h
+#include linux/usb/musb.h
+
+#include asm/mach/arch.h
+#include asm/mach-types.h
+
+#include mach/board.h
+#include mach/common.h
+#include mach/irqs.h
+#include mach/mcspi.h
+#include mach/onenand.h
+#include mach/serial.h
+
+static struct omap2_mcspi_device_config p54spi_mcspi_config = {
+ .turbo_mode = 0,
+ .single_channel = 1,
+};
+
+static struct spi_board_info n800_spi_board_info[] __initdata = {
+ {
+ .modalias = p54spi,
+ .bus_num= 2,
+ .chip_select= 0,
+ .max_speed_hz = 4800,
+ .controller_data = p54spi_mcspi_config,
+ },
+};
+
+#if defined(CONFIG_MTD_ONENAND_OMAP2) || \
+ defined(CONFIG_MTD_ONENAND_OMAP2_MODULE)
+
+static struct mtd_partition onenand_partitions[] = {
+ {
+ .name = bootloader,
+ .offset = 0,
+ .size = 0x2,
+ .mask_flags = MTD_WRITEABLE,/* Force read-only */
+ },
+ {
+ .name = config,
+ .offset = MTDPART_OFS_APPEND,
+ .size = 0x6,
+ },
+ {
+ .name = kernel,
+ .offset = MTDPART_OFS_APPEND,
+ .size = 0x20,
+ },
+ {
+ .name = initfs,
+ .offset = MTDPART_OFS_APPEND,
+ .size = 0x40,
+ },
+ {
+ .name = rootfs,
+ .offset = MTDPART_OFS_APPEND,
+ .size = MTDPART_SIZ_FULL,
+ },
+};
+
+static struct omap_onenand_platform_data board_onenand_data = {
+ .cs = 0,
+ .gpio_irq = 26,
+ .parts = onenand_partitions,
+ .nr_parts = ARRAY_SIZE(onenand_partitions),
+ .flags = ONENAND_SYNC_READ,
+};
+
+static void __init n8x0_onenand_init(void)
+{
+ gpmc_onenand_init(board_onenand_data);
+}
+
+#else
+
+static void __init n8x0_onenand_init(void) {}
+
+#endif
+
+/* FIXME: n810 needs UART1 */
+static struct omap_uart_platform_data n8x0_uart_config __initdata = {
+ .enabled_uarts = (1 2),
+};
+
+static void __init n8x0_map_io(void)
+{
+ omap2_set_globals_242x();
+ omap2_map_common_io();
+}
+
+static void __init n8x0_init_irq(void)
+{
+ omap2_init_common_hw(NULL);
+ omap_init_irq();
+ omap_gpio_init();
+}
+
+static void __init n8x0_init_machine(void)
+{
+ /* FIXME: add n810
Re: [PATCH 8/9] OMAP2: add board file for Nokia N800 and N810
Russell King - ARM Linux li...@arm.linux.org.uk writes:
On Tue, Aug 11, 2009 at 12:55:58PM +0300, Tony Lindgren wrote:
+#include mach/gpio.h
linux/gpio.h
+#include mach/io.h
linux/io.h
Thanks, will fix.
+static struct musb_hdrc_platform_data tusb_data = {
+.mode = BOARD_MODE,
+.set_power = tusb_set_power,
+.set_clock = tusb_set_clock,
+.min_power = 25, /* x2 = 50 mA drawn from VBUS as peripheral */
+.power = 100, /* Max 100 mA VBUS for host mode */
+.clock = osc_ck,
Still passing clock names around?
Sorry, I'm not familiar with this. How should I fix it?
Tony, do you want me to send v2?
--
Kalle Valo
--
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/majordomo-info.html
Re: OMAP PM status?
Kevin Hilman khil...@deeprootsystems.com writes: Hi Kalle, Hello, Kalle Valo kalle.v...@iki.fi writes: as you might guess, I'm eagerly waiting for OMAP PM support to hit mainline :) I'm just curious, what's the current status? Are we going to get PM support in 2.6.32? Hmmm, good question. To avoid giving an answer that can be archived and used against me, I updated the PM branch wiki page[1] with a 'mainline plans' section[2] which I can edit as plans slip^Wchange. :) Excellent, the page was very helpful for me and I'm sure also for others. Especially I'm interested about 2420 support for n8x0. Well, I'm afraid I've done basically no testing for OMAP2, and have been focusing solely on OMAP3. I'm pretty sure things at least should compile for OMAP2, as care has been taken to keep OMAP2 up to speed with OMAP3 for the base features, but I haven't done any boot testing on OMAP2 for some time. I'm sorry to hear that, but I understand that you don't have time for everything. That being said, all the infrastructure for OMAP2 that was in linux-omap is already in mainline so will work as good as it did in linux-omap. The last time I actually tried PM on OMAP2, I found/fixed a bug[3] in the asm sleep code for OMAP2 that was causing fault. At least it no longer faults when suspended Of course, I'll be glad to take any OMAP2 patches/fixes and get them upstream with the rest of my changes, but I'm afraid with my current plans, I do not have the cycles to spend on OMAP2. As soon as I find some spare time (which usually means three to four months from now :) I'll start experimenting with N800 PM. If I have any problems, I'll send email to the list as usual. Thanks. -- Kalle Valo -- 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/majordomo-info.html
OMAP PM status?
Hi Kevin, as you might guess, I'm eagerly waiting for OMAP PM support to hit mainline :) I'm just curious, what's the current status? Are we going to get PM support in 2.6.32? Especially I'm interested about 2420 support for n8x0. -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH v2 0/2] Nokia n8x0 support for mainline
On Sat, Aug 8, 2009 at 12:57 PM, Kalle Valokalle.v...@iki.fi wrote: Here's v2 of n8x0 patches. Added proper commit logs and fixed copyright years reported by our patch review machine Felipe Balbi :) I hope these are now ready for mainline. These patches depend on my serial omap tag removal patches. The patches also depend on the patch below, which I sent earlier this week: Author: Kalle Valo kalle.v...@iki.fi Date: Fri Aug 7 15:46:30 2009 +0300 omap2: compile usb-tusb6010.c For some reason usb-tusb6010.c was't compiled, add it to Makefile and Kconfig. This is prepraration for upcoming n8x0 support. Signed-off-by: Kalle Valo kalle.v...@iki.fi Kalle -- 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/majordomo-info.html
[PATCH v2 0/2] Nokia n8x0 support for mainline
Here's v2 of n8x0 patches. Added proper commit logs and fixed copyright years reported by our patch review machine Felipe Balbi :) I hope these are now ready for mainline. These patches depend on my serial omap tag removal patches. --- Kalle Valo (2): OMAP2: n8x0: add n8x0_defconfig OMAP2: add board file for Nokia N800 and N810 arch/arm/configs/n8x0_defconfig | 1104 ++ arch/arm/mach-omap2/Kconfig |4 arch/arm/mach-omap2/Makefile |2 arch/arm/mach-omap2/board-n8x0.c | 307 +++ 4 files changed, 1416 insertions(+), 1 deletions(-) create mode 100644 arch/arm/configs/n8x0_defconfig create mode 100644 arch/arm/mach-omap2/board-n8x0.c -- 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/majordomo-info.html
[PATCH v2 1/2] OMAP2: add board file for Nokia N800 and N810
Add board file for Nokia N800 and N810 devices. Currently only serial ports,
onenand, spi and usb are configured, more to come later.
Tested on Nokia N800.
Signed-off-by: Kalle Valo kalle.v...@iki.fi
---
arch/arm/mach-omap2/Kconfig |4
arch/arm/mach-omap2/Makefile |2
arch/arm/mach-omap2/board-n8x0.c | 307 ++
3 files changed, 312 insertions(+), 1 deletions(-)
create mode 100644 arch/arm/mach-omap2/board-n8x0.c
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index bf54686..75b1c7e 100644
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -73,6 +73,10 @@ config MACH_OMAP_3430SDP
bool OMAP 3430 SDP board
depends on ARCH_OMAP3 ARCH_OMAP34XX
+config MACH_NOKIA_N8X0
+ bool Nokia N800/N810
+ depends on ARCH_OMAP2420
+
config MACH_NOKIA_RX51
bool Nokia RX-51 board
depends on ARCH_OMAP3 ARCH_OMAP34XX
diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile
index 757c84b..8850a24 100644
--- a/arch/arm/mach-omap2/Makefile
+++ b/arch/arm/mach-omap2/Makefile
@@ -62,7 +62,7 @@ obj-$(CONFIG_MACH_OMAP3_PANDORA) += board-omap3pandora.o
\
mmc-twl4030.o
obj-$(CONFIG_MACH_OMAP_3430SDP)+= board-3430sdp.o \
mmc-twl4030.o
-
+obj-$(CONFIG_MACH_NOKIA_N8X0) += board-n8x0.o
obj-$(CONFIG_MACH_NOKIA_RX51) += board-rx51.o \
board-rx51-peripherals.o \
mmc-twl4030.o
diff --git a/arch/arm/mach-omap2/board-n8x0.c b/arch/arm/mach-omap2/board-n8x0.c
new file mode 100644
index 000..ed0a457
--- /dev/null
+++ b/arch/arm/mach-omap2/board-n8x0.c
@@ -0,0 +1,307 @@
+/*
+ * linux/arch/arm/mach-omap2/board-n8x0.c
+ *
+ * Copyright (C) 2005-2009 Nokia Corporation
+ * Author: Juha Yrjola juha.yrj...@nokia.com
+ *
+ * Modified from mach-omap2/board-generic.c
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+#include linux/clk.h
+#include linux/delay.h
+#include linux/init.h
+#include linux/stddef.h
+#include linux/spi/spi.h
+#include linux/usb/musb.h
+
+#include asm/mach/arch.h
+#include asm/mach-types.h
+
+#include mach/board.h
+#include mach/common.h
+#include mach/gpio.h
+#include mach/io.h
+#include mach/irqs.h
+#include mach/mcspi.h
+#include mach/onenand.h
+#include mach/serial.h
+
+#define TUSB_ASYNC_CS 1
+#define TUSB_SYNC_CS 4
+#define GPIO_TUSB_INT 58
+#define GPIO_TUSB_ENABLE 0
+
+#if defined(CONFIG_USB_MUSB_OTG)
+#define BOARD_MODE MUSB_OTG
+#elif defined(CONFIG_USB_MUSB_PERIPHERAL)
+#define BOARD_MODE MUSB_PERIPHERAL
+#else /* defined(CONFIG_USB_MUSB_HOST) */
+#define BOARD_MODE MUSB_HOST
+#endif
+
+/*
+ * Enable or disable power to TUSB6010. When enabling, turn on 3.3 V and
+ * 1.5 V voltage regulators of PM companion chip. Companion chip will then
+ * provide then PGOOD signal to TUSB6010 which will release it from reset.
+ */
+static int tusb_set_power(int state)
+{
+ int i, retval = 0;
+
+ if (state) {
+ gpio_set_value(GPIO_TUSB_ENABLE, 1);
+ msleep(1);
+
+ /* Wait until TUSB6010 pulls INT pin down */
+ i = 100;
+ while (i gpio_get_value(GPIO_TUSB_INT)) {
+ msleep(1);
+ i--;
+ }
+
+ if (!i) {
+ printk(KERN_ERR tusb: powerup failed\n);
+ retval = -ENODEV;
+ }
+ } else {
+ gpio_set_value(GPIO_TUSB_ENABLE, 0);
+ msleep(10);
+ }
+
+ return retval;
+}
+
+static int osc_ck_on;
+
+static int tusb_set_clock(struct clk *osc_ck, int state)
+{
+ if (state) {
+ if (osc_ck_on 0)
+ return -ENODEV;
+
+ clk_enable(osc_ck);
+ osc_ck_on = 1;
+ } else {
+ if (osc_ck_on == 0)
+ return -ENODEV;
+
+ clk_disable(osc_ck);
+ osc_ck_on = 0;
+ }
+
+ return 0;
+}
+
+static struct musb_hdrc_eps_bits musb_eps[] = {
+ { ep1_tx, 5,},
+ { ep1_rx, 5,},
+ { ep2_tx, 5,},
+ { ep2_rx, 5,},
+ { ep3_tx, 3,},
+ { ep3_rx, 3,},
+ { ep4_tx, 3,},
+ { ep4_rx, 3,},
+ { ep5_tx, 2,},
+ { ep5_rx, 2,},
+ { ep6_tx, 2,},
+ { ep6_rx, 2,},
+ { ep7_tx, 2,},
+ { ep7_rx, 2,},
+ { ep8_tx, 2,},
+ { ep8_rx, 2,},
+ { ep9_tx, 2
[PATCH v2 2/2] OMAP2: n8x0: add n8x0_defconfig
Add defconfig file for OMAP2 N800 and N810 devices. Signed-off-by: Kalle Valo kalle.v...@iki.fi --- arch/arm/configs/n8x0_defconfig | 1104 +++ 1 files changed, 1104 insertions(+), 0 deletions(-) create mode 100644 arch/arm/configs/n8x0_defconfig diff --git a/arch/arm/configs/n8x0_defconfig b/arch/arm/configs/n8x0_defconfig new file mode 100644 index 000..8da75de --- /dev/null +++ b/arch/arm/configs/n8x0_defconfig @@ -0,0 +1,1104 @@ +# +# Automatically generated make config: don't edit +# Linux kernel version: 2.6.31-rc5 +# Thu Aug 6 22:17:23 2009 +# +CONFIG_ARM=y +CONFIG_SYS_SUPPORTS_APM_EMULATION=y +CONFIG_GENERIC_GPIO=y +CONFIG_GENERIC_TIME=y +CONFIG_GENERIC_CLOCKEVENTS=y +CONFIG_MMU=y +CONFIG_GENERIC_HARDIRQS=y +CONFIG_STACKTRACE_SUPPORT=y +CONFIG_HAVE_LATENCYTOP_SUPPORT=y +CONFIG_LOCKDEP_SUPPORT=y +CONFIG_TRACE_IRQFLAGS_SUPPORT=y +CONFIG_HARDIRQS_SW_RESEND=y +CONFIG_GENERIC_IRQ_PROBE=y +CONFIG_RWSEM_GENERIC_SPINLOCK=y +CONFIG_GENERIC_HWEIGHT=y +CONFIG_GENERIC_CALIBRATE_DELAY=y +CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y +CONFIG_VECTORS_BASE=0x +CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config +CONFIG_CONSTRUCTORS=y + +# +# General setup +# +CONFIG_EXPERIMENTAL=y +CONFIG_BROKEN_ON_SMP=y +CONFIG_INIT_ENV_ARG_LIMIT=32 +CONFIG_LOCALVERSION= +CONFIG_LOCALVERSION_AUTO=y +CONFIG_SWAP=y +CONFIG_SYSVIPC=y +CONFIG_SYSVIPC_SYSCTL=y +# CONFIG_POSIX_MQUEUE is not set +# CONFIG_BSD_PROCESS_ACCT is not set +# CONFIG_TASKSTATS is not set +# CONFIG_AUDIT is not set + +# +# RCU Subsystem +# +# CONFIG_CLASSIC_RCU is not set +CONFIG_TREE_RCU=y +# CONFIG_PREEMPT_RCU is not set +# CONFIG_RCU_TRACE is not set +CONFIG_RCU_FANOUT=32 +# CONFIG_RCU_FANOUT_EXACT is not set +# CONFIG_TREE_RCU_TRACE is not set +# CONFIG_PREEMPT_RCU_TRACE is not set +# CONFIG_IKCONFIG is not set +CONFIG_LOG_BUF_SHIFT=14 +# CONFIG_GROUP_SCHED is not set +# CONFIG_CGROUPS is not set +# CONFIG_SYSFS_DEPRECATED_V2 is not set +# CONFIG_RELAY is not set +CONFIG_NAMESPACES=y +# CONFIG_UTS_NS is not set +# CONFIG_IPC_NS is not set +# CONFIG_USER_NS is not set +# CONFIG_PID_NS is not set +# CONFIG_NET_NS is not set +CONFIG_BLK_DEV_INITRD=y +CONFIG_INITRAMFS_SOURCE= +CONFIG_RD_GZIP=y +CONFIG_RD_BZIP2=y +CONFIG_RD_LZMA=y +CONFIG_CC_OPTIMIZE_FOR_SIZE=y +CONFIG_SYSCTL=y +CONFIG_ANON_INODES=y +# CONFIG_EMBEDDED is not set +CONFIG_UID16=y +CONFIG_SYSCTL_SYSCALL=y +CONFIG_KALLSYMS=y +# CONFIG_KALLSYMS_ALL is not set +# CONFIG_KALLSYMS_EXTRA_PASS is not set +CONFIG_HOTPLUG=y +CONFIG_PRINTK=y +CONFIG_BUG=y +CONFIG_ELF_CORE=y +CONFIG_BASE_FULL=y +CONFIG_FUTEX=y +CONFIG_EPOLL=y +CONFIG_SIGNALFD=y +CONFIG_TIMERFD=y +CONFIG_EVENTFD=y +CONFIG_SHMEM=y +CONFIG_AIO=y + +# +# Performance Counters +# +CONFIG_VM_EVENT_COUNTERS=y +CONFIG_SLUB_DEBUG=y +# CONFIG_STRIP_ASM_SYMS is not set +CONFIG_COMPAT_BRK=y +# CONFIG_SLAB is not set +CONFIG_SLUB=y +# CONFIG_SLOB is not set +# CONFIG_PROFILING is not set +# CONFIG_MARKERS is not set +CONFIG_HAVE_OPROFILE=y +# CONFIG_KPROBES is not set +CONFIG_HAVE_KPROBES=y +CONFIG_HAVE_KRETPROBES=y +CONFIG_HAVE_CLK=y + +# +# GCOV-based kernel profiling +# +# CONFIG_SLOW_WORK is not set +CONFIG_HAVE_GENERIC_DMA_COHERENT=y +CONFIG_SLABINFO=y +CONFIG_RT_MUTEXES=y +CONFIG_BASE_SMALL=0 +CONFIG_MODULES=y +# CONFIG_MODULE_FORCE_LOAD is not set +CONFIG_MODULE_UNLOAD=y +# CONFIG_MODULE_FORCE_UNLOAD is not set +# CONFIG_MODVERSIONS is not set +# CONFIG_MODULE_SRCVERSION_ALL is not set +CONFIG_BLOCK=y +# CONFIG_LBDAF is not set +# CONFIG_BLK_DEV_BSG is not set +# CONFIG_BLK_DEV_INTEGRITY is not set + +# +# IO Schedulers +# +CONFIG_IOSCHED_NOOP=y +# CONFIG_IOSCHED_AS is not set +# CONFIG_IOSCHED_DEADLINE is not set +CONFIG_IOSCHED_CFQ=y +# CONFIG_DEFAULT_AS is not set +# CONFIG_DEFAULT_DEADLINE is not set +CONFIG_DEFAULT_CFQ=y +# CONFIG_DEFAULT_NOOP is not set +CONFIG_DEFAULT_IOSCHED=cfq +# CONFIG_FREEZER is not set + +# +# System Type +# +# CONFIG_ARCH_AAEC2000 is not set +# CONFIG_ARCH_INTEGRATOR is not set +# CONFIG_ARCH_REALVIEW is not set +# CONFIG_ARCH_VERSATILE is not set +# CONFIG_ARCH_AT91 is not set +# CONFIG_ARCH_CLPS711X is not set +# CONFIG_ARCH_GEMINI is not set +# CONFIG_ARCH_EBSA110 is not set +# CONFIG_ARCH_EP93XX is not set +# CONFIG_ARCH_FOOTBRIDGE is not set +# CONFIG_ARCH_MXC is not set +# CONFIG_ARCH_STMP3XXX is not set +# CONFIG_ARCH_NETX is not set +# CONFIG_ARCH_H720X is not set +# CONFIG_ARCH_IOP13XX is not set +# CONFIG_ARCH_IOP32X is not set +# CONFIG_ARCH_IOP33X is not set +# CONFIG_ARCH_IXP23XX is not set +# CONFIG_ARCH_IXP2000 is not set +# CONFIG_ARCH_IXP4XX is not set +# CONFIG_ARCH_L7200 is not set +# CONFIG_ARCH_KIRKWOOD is not set +# CONFIG_ARCH_LOKI is not set +# CONFIG_ARCH_MV78XX0 is not set +# CONFIG_ARCH_ORION5X is not set +# CONFIG_ARCH_MMP is not set +# CONFIG_ARCH_KS8695 is not set +# CONFIG_ARCH_NS9XXX is not set +# CONFIG_ARCH_W90X900 is not set +# CONFIG_ARCH_PNX4008 is not set +# CONFIG_ARCH_PXA is not set +# CONFIG_ARCH_MSM is not set
Re: [PATCH 2/2] OMAP: remove OMAP_TAG_UART
Pandita, Vikram vikram.pand...@ti.com writes: Omap tags are deprecrated and convert all OMAP_TAG_UART cases to use omap_uart_platform_data instead. Tested on rx51 and n8x0. Compile tested on omap_osk_5912. Signed-off-by: Kalle Valo kalle.v...@iki.fi Any plans to remove OMAP_TAG_LCD I don't have any plans, but I don't know about others. -- Kalle Valo -- 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/majordomo-info.html
Re: N8x0 to mainline patches
Tony Lindgren t...@atomide.com writes: 2. finins and send tusb6010 patch + omap2-add-usb-tusb6010-c The tusb6010 could be added later on as a fix too if you want to cut down dependencies. Good point, I'll send that separately. Current n8x0 patches are here: http://www.valot.fi/kalle/n8x0/patches/n8x0-add/2009-08-06-19:21/ They are just pending final testing and I'll send them after I have done that, hopefully tonight. Tony, on which tree should I base the patches? They are now against linus's tree. -- Kalle Valo -- 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/majordomo-info.html
[PATCH] omap2: compile usb-tusb6010.c
For some reason usb-tusb6010.c was't compiled, add it to Makefile and Kconfig. This is prepraration for upcoming n8x0 support. Signed-off-by: Kalle Valo kalle.v...@iki.fi --- arch/arm/mach-omap2/Kconfig |5 + arch/arm/mach-omap2/Makefile |1 + 2 files changed, 6 insertions(+), 0 deletions(-) diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig index a755eb5..bf54686 100644 --- a/arch/arm/mach-omap2/Kconfig +++ b/arch/arm/mach-omap2/Kconfig @@ -31,6 +31,11 @@ config MACH_OMAP_GENERIC bool Generic OMAP board depends on ARCH_OMAP2 ARCH_OMAP24XX +config MACH_OMAP2_TUSB6010 + bool + depends on ARCH_OMAP2 ARCH_OMAP2420 + default y if MACH_NOKIA_N8X0 + config MACH_OMAP_H4 bool OMAP 2420 H4 board depends on ARCH_OMAP2 ARCH_OMAP24XX diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile index 735bae5..757c84b 100644 --- a/arch/arm/mach-omap2/Makefile +++ b/arch/arm/mach-omap2/Makefile @@ -74,6 +74,7 @@ obj-$(CONFIG_MACH_OMAP_4430SDP) += board-4430sdp.o # Platform specific device init code obj-y += usb-musb.o +obj-$(CONFIG_MACH_OMAP2_TUSB6010) += usb-tusb6010.o onenand-$(CONFIG_MTD_ONENAND_OMAP2):= gpmc-onenand.o obj-y += $(onenand-m) $(onenand-y) -- 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/majordomo-info.html
[PATCH 0/2] Nokia n8x0 support for mainline
Here are patches for mainline to support Nokia N800 and N810. Tested on Nokia N800. Lots of stuff still missing, but we have to start from somewhere. --- Kalle Valo (2): n8x0: add n8x0_defconfig Add support for Nokia N800 arch/arm/configs/n8x0_defconfig | 1104 ++ arch/arm/mach-omap2/Kconfig |4 arch/arm/mach-omap2/Makefile |2 arch/arm/mach-omap2/board-n8x0.c | 307 +++ 4 files changed, 1416 insertions(+), 1 deletions(-) create mode 100644 arch/arm/configs/n8x0_defconfig create mode 100644 arch/arm/mach-omap2/board-n8x0.c -- 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/majordomo-info.html
[PATCH 1/2] Add support for Nokia N800
Signed-off-by: Kalle Valo kalle.v...@iki.fi
---
arch/arm/mach-omap2/Kconfig |4
arch/arm/mach-omap2/Makefile |2
arch/arm/mach-omap2/board-n8x0.c | 307 ++
3 files changed, 312 insertions(+), 1 deletions(-)
create mode 100644 arch/arm/mach-omap2/board-n8x0.c
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index bf54686..75b1c7e 100644
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -73,6 +73,10 @@ config MACH_OMAP_3430SDP
bool OMAP 3430 SDP board
depends on ARCH_OMAP3 ARCH_OMAP34XX
+config MACH_NOKIA_N8X0
+ bool Nokia N800/N810
+ depends on ARCH_OMAP2420
+
config MACH_NOKIA_RX51
bool Nokia RX-51 board
depends on ARCH_OMAP3 ARCH_OMAP34XX
diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile
index 757c84b..8850a24 100644
--- a/arch/arm/mach-omap2/Makefile
+++ b/arch/arm/mach-omap2/Makefile
@@ -62,7 +62,7 @@ obj-$(CONFIG_MACH_OMAP3_PANDORA) += board-omap3pandora.o
\
mmc-twl4030.o
obj-$(CONFIG_MACH_OMAP_3430SDP)+= board-3430sdp.o \
mmc-twl4030.o
-
+obj-$(CONFIG_MACH_NOKIA_N8X0) += board-n8x0.o
obj-$(CONFIG_MACH_NOKIA_RX51) += board-rx51.o \
board-rx51-peripherals.o \
mmc-twl4030.o
diff --git a/arch/arm/mach-omap2/board-n8x0.c b/arch/arm/mach-omap2/board-n8x0.c
new file mode 100644
index 000..08d1c11
--- /dev/null
+++ b/arch/arm/mach-omap2/board-n8x0.c
@@ -0,0 +1,307 @@
+/*
+ * linux/arch/arm/mach-omap2/board-n8x0.c
+ *
+ * Copyright (C) 2005-2007 Nokia Corporation
+ * Author: Juha Yrjola juha.yrj...@nokia.com
+ *
+ * Modified from mach-omap2/board-generic.c
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+#include linux/clk.h
+#include linux/delay.h
+#include linux/init.h
+#include linux/stddef.h
+#include linux/spi/spi.h
+#include linux/usb/musb.h
+
+#include asm/mach/arch.h
+#include asm/mach-types.h
+
+#include mach/board.h
+#include mach/common.h
+#include mach/gpio.h
+#include mach/io.h
+#include mach/irqs.h
+#include mach/mcspi.h
+#include mach/onenand.h
+#include mach/serial.h
+
+#define TUSB_ASYNC_CS 1
+#define TUSB_SYNC_CS 4
+#define GPIO_TUSB_INT 58
+#define GPIO_TUSB_ENABLE 0
+
+#if defined(CONFIG_USB_MUSB_OTG)
+#define BOARD_MODE MUSB_OTG
+#elif defined(CONFIG_USB_MUSB_PERIPHERAL)
+#define BOARD_MODE MUSB_PERIPHERAL
+#else /* defined(CONFIG_USB_MUSB_HOST) */
+#define BOARD_MODE MUSB_HOST
+#endif
+
+/*
+ * Enable or disable power to TUSB6010. When enabling, turn on 3.3 V and
+ * 1.5 V voltage regulators of PM companion chip. Companion chip will then
+ * provide then PGOOD signal to TUSB6010 which will release it from reset.
+ */
+static int tusb_set_power(int state)
+{
+ int i, retval = 0;
+
+ if (state) {
+ gpio_set_value(GPIO_TUSB_ENABLE, 1);
+ msleep(1);
+
+ /* Wait until TUSB6010 pulls INT pin down */
+ i = 100;
+ while (i gpio_get_value(GPIO_TUSB_INT)) {
+ msleep(1);
+ i--;
+ }
+
+ if (!i) {
+ printk(KERN_ERR tusb: powerup failed\n);
+ retval = -ENODEV;
+ }
+ } else {
+ gpio_set_value(GPIO_TUSB_ENABLE, 0);
+ msleep(10);
+ }
+
+ return retval;
+}
+
+static int osc_ck_on;
+
+static int tusb_set_clock(struct clk *osc_ck, int state)
+{
+ if (state) {
+ if (osc_ck_on 0)
+ return -ENODEV;
+
+ clk_enable(osc_ck);
+ osc_ck_on = 1;
+ } else {
+ if (osc_ck_on == 0)
+ return -ENODEV;
+
+ clk_disable(osc_ck);
+ osc_ck_on = 0;
+ }
+
+ return 0;
+}
+
+static struct musb_hdrc_eps_bits musb_eps[] = {
+ { ep1_tx, 5,},
+ { ep1_rx, 5,},
+ { ep2_tx, 5,},
+ { ep2_rx, 5,},
+ { ep3_tx, 3,},
+ { ep3_rx, 3,},
+ { ep4_tx, 3,},
+ { ep4_rx, 3,},
+ { ep5_tx, 2,},
+ { ep5_rx, 2,},
+ { ep6_tx, 2,},
+ { ep6_rx, 2,},
+ { ep7_tx, 2,},
+ { ep7_rx, 2,},
+ { ep8_tx, 2,},
+ { ep8_rx, 2,},
+ { ep9_tx, 2,},
+ { ep9_rx, 2,},
+ { ep10_tx, 2, },
+ { ep10_rx, 2, },
+ { ep11_tx, 2, },
+ { ep11_rx, 2
[PATCH 2/2] n8x0: add n8x0_defconfig
Signed-off-by: Kalle Valo kalle.v...@iki.fi --- arch/arm/configs/n8x0_defconfig | 1104 +++ 1 files changed, 1104 insertions(+), 0 deletions(-) create mode 100644 arch/arm/configs/n8x0_defconfig diff --git a/arch/arm/configs/n8x0_defconfig b/arch/arm/configs/n8x0_defconfig new file mode 100644 index 000..8da75de --- /dev/null +++ b/arch/arm/configs/n8x0_defconfig @@ -0,0 +1,1104 @@ +# +# Automatically generated make config: don't edit +# Linux kernel version: 2.6.31-rc5 +# Thu Aug 6 22:17:23 2009 +# +CONFIG_ARM=y +CONFIG_SYS_SUPPORTS_APM_EMULATION=y +CONFIG_GENERIC_GPIO=y +CONFIG_GENERIC_TIME=y +CONFIG_GENERIC_CLOCKEVENTS=y +CONFIG_MMU=y +CONFIG_GENERIC_HARDIRQS=y +CONFIG_STACKTRACE_SUPPORT=y +CONFIG_HAVE_LATENCYTOP_SUPPORT=y +CONFIG_LOCKDEP_SUPPORT=y +CONFIG_TRACE_IRQFLAGS_SUPPORT=y +CONFIG_HARDIRQS_SW_RESEND=y +CONFIG_GENERIC_IRQ_PROBE=y +CONFIG_RWSEM_GENERIC_SPINLOCK=y +CONFIG_GENERIC_HWEIGHT=y +CONFIG_GENERIC_CALIBRATE_DELAY=y +CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y +CONFIG_VECTORS_BASE=0x +CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config +CONFIG_CONSTRUCTORS=y + +# +# General setup +# +CONFIG_EXPERIMENTAL=y +CONFIG_BROKEN_ON_SMP=y +CONFIG_INIT_ENV_ARG_LIMIT=32 +CONFIG_LOCALVERSION= +CONFIG_LOCALVERSION_AUTO=y +CONFIG_SWAP=y +CONFIG_SYSVIPC=y +CONFIG_SYSVIPC_SYSCTL=y +# CONFIG_POSIX_MQUEUE is not set +# CONFIG_BSD_PROCESS_ACCT is not set +# CONFIG_TASKSTATS is not set +# CONFIG_AUDIT is not set + +# +# RCU Subsystem +# +# CONFIG_CLASSIC_RCU is not set +CONFIG_TREE_RCU=y +# CONFIG_PREEMPT_RCU is not set +# CONFIG_RCU_TRACE is not set +CONFIG_RCU_FANOUT=32 +# CONFIG_RCU_FANOUT_EXACT is not set +# CONFIG_TREE_RCU_TRACE is not set +# CONFIG_PREEMPT_RCU_TRACE is not set +# CONFIG_IKCONFIG is not set +CONFIG_LOG_BUF_SHIFT=14 +# CONFIG_GROUP_SCHED is not set +# CONFIG_CGROUPS is not set +# CONFIG_SYSFS_DEPRECATED_V2 is not set +# CONFIG_RELAY is not set +CONFIG_NAMESPACES=y +# CONFIG_UTS_NS is not set +# CONFIG_IPC_NS is not set +# CONFIG_USER_NS is not set +# CONFIG_PID_NS is not set +# CONFIG_NET_NS is not set +CONFIG_BLK_DEV_INITRD=y +CONFIG_INITRAMFS_SOURCE= +CONFIG_RD_GZIP=y +CONFIG_RD_BZIP2=y +CONFIG_RD_LZMA=y +CONFIG_CC_OPTIMIZE_FOR_SIZE=y +CONFIG_SYSCTL=y +CONFIG_ANON_INODES=y +# CONFIG_EMBEDDED is not set +CONFIG_UID16=y +CONFIG_SYSCTL_SYSCALL=y +CONFIG_KALLSYMS=y +# CONFIG_KALLSYMS_ALL is not set +# CONFIG_KALLSYMS_EXTRA_PASS is not set +CONFIG_HOTPLUG=y +CONFIG_PRINTK=y +CONFIG_BUG=y +CONFIG_ELF_CORE=y +CONFIG_BASE_FULL=y +CONFIG_FUTEX=y +CONFIG_EPOLL=y +CONFIG_SIGNALFD=y +CONFIG_TIMERFD=y +CONFIG_EVENTFD=y +CONFIG_SHMEM=y +CONFIG_AIO=y + +# +# Performance Counters +# +CONFIG_VM_EVENT_COUNTERS=y +CONFIG_SLUB_DEBUG=y +# CONFIG_STRIP_ASM_SYMS is not set +CONFIG_COMPAT_BRK=y +# CONFIG_SLAB is not set +CONFIG_SLUB=y +# CONFIG_SLOB is not set +# CONFIG_PROFILING is not set +# CONFIG_MARKERS is not set +CONFIG_HAVE_OPROFILE=y +# CONFIG_KPROBES is not set +CONFIG_HAVE_KPROBES=y +CONFIG_HAVE_KRETPROBES=y +CONFIG_HAVE_CLK=y + +# +# GCOV-based kernel profiling +# +# CONFIG_SLOW_WORK is not set +CONFIG_HAVE_GENERIC_DMA_COHERENT=y +CONFIG_SLABINFO=y +CONFIG_RT_MUTEXES=y +CONFIG_BASE_SMALL=0 +CONFIG_MODULES=y +# CONFIG_MODULE_FORCE_LOAD is not set +CONFIG_MODULE_UNLOAD=y +# CONFIG_MODULE_FORCE_UNLOAD is not set +# CONFIG_MODVERSIONS is not set +# CONFIG_MODULE_SRCVERSION_ALL is not set +CONFIG_BLOCK=y +# CONFIG_LBDAF is not set +# CONFIG_BLK_DEV_BSG is not set +# CONFIG_BLK_DEV_INTEGRITY is not set + +# +# IO Schedulers +# +CONFIG_IOSCHED_NOOP=y +# CONFIG_IOSCHED_AS is not set +# CONFIG_IOSCHED_DEADLINE is not set +CONFIG_IOSCHED_CFQ=y +# CONFIG_DEFAULT_AS is not set +# CONFIG_DEFAULT_DEADLINE is not set +CONFIG_DEFAULT_CFQ=y +# CONFIG_DEFAULT_NOOP is not set +CONFIG_DEFAULT_IOSCHED=cfq +# CONFIG_FREEZER is not set + +# +# System Type +# +# CONFIG_ARCH_AAEC2000 is not set +# CONFIG_ARCH_INTEGRATOR is not set +# CONFIG_ARCH_REALVIEW is not set +# CONFIG_ARCH_VERSATILE is not set +# CONFIG_ARCH_AT91 is not set +# CONFIG_ARCH_CLPS711X is not set +# CONFIG_ARCH_GEMINI is not set +# CONFIG_ARCH_EBSA110 is not set +# CONFIG_ARCH_EP93XX is not set +# CONFIG_ARCH_FOOTBRIDGE is not set +# CONFIG_ARCH_MXC is not set +# CONFIG_ARCH_STMP3XXX is not set +# CONFIG_ARCH_NETX is not set +# CONFIG_ARCH_H720X is not set +# CONFIG_ARCH_IOP13XX is not set +# CONFIG_ARCH_IOP32X is not set +# CONFIG_ARCH_IOP33X is not set +# CONFIG_ARCH_IXP23XX is not set +# CONFIG_ARCH_IXP2000 is not set +# CONFIG_ARCH_IXP4XX is not set +# CONFIG_ARCH_L7200 is not set +# CONFIG_ARCH_KIRKWOOD is not set +# CONFIG_ARCH_LOKI is not set +# CONFIG_ARCH_MV78XX0 is not set +# CONFIG_ARCH_ORION5X is not set +# CONFIG_ARCH_MMP is not set +# CONFIG_ARCH_KS8695 is not set +# CONFIG_ARCH_NS9XXX is not set +# CONFIG_ARCH_W90X900 is not set +# CONFIG_ARCH_PNX4008 is not set +# CONFIG_ARCH_PXA is not set +# CONFIG_ARCH_MSM is not set +# CONFIG_ARCH_RPC is not set +# CONFIG_ARCH_SA1100 is not set
Re: [PATCH 1/2] Add support for Nokia N800
Felipe Balbi felipe.ba...@nokia.com writes: +/* + * linux/arch/arm/mach-omap2/board-n8x0.c + * + * Copyright (C) 2005-2007 Nokia Corporation 2005-2009 Thanks, I'll fix that in v2. I also noticed that patch description was missing in both n8x0 patches, I'll write something. -- Kalle Valo -- 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/majordomo-info.html
Re: N8x0 to mainline patches
Tony Lindgren t...@atomide.com writes: Hey, nice job cleaning up the n8x0 board support! Let's get those into l-o master and queued up for the next merge window. (Except for the hacks that is). What did you think of the file layout? I decided to go with one file approach (against your advice, sorry) because I didn't see any benefit from having separate files. My plan is this: 1. first finish OMAP_TAG_UART removal patch and send it for review 2. finins and send tusb6010 patch + omap2-add-usb-tusb6010-c 2. fold these n8x0 board file patches into one and send it for review: + n8x0-add-board-file + n8x0-onenand-support + n8x0-add-spi-support + n8x0-add-usb-support Because the merge window is getting close, I'll do this ASAP. There's a lot of to do still, but it's to get basic support to mainline already now, makes it easier for us to implement the missing pieces. -- Kalle Valo -- 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/majordomo-info.html
Re: N8x0 to mainline patches
On Thu, Aug 6, 2009 at 7:21 PM, Kalle Valokalle.v...@iki.fi wrote: My plan is this: 1. first finish OMAP_TAG_UART removal patch and send it for review 2. finins and send tusb6010 patch + omap2-add-usb-tusb6010-c 2. fold these n8x0 board file patches into one and send it for review: + n8x0-add-board-file + n8x0-onenand-support + n8x0-add-spi-support + n8x0-add-usb-support This was item 3, of course. And I forget n8x0_defconfig, I'll send that as a separate patch. Tony, does this look ok to you? Kalle -- 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/majordomo-info.html
[PATCH 0/2] Remove omap serial tags
Here are patches which remove OMAP_TAG_SERIAL_CONSOLE and OMAP_TAG_UART. The patches are based on linus' tree commit 90bc1a658. If I need to rebase it some other tree, please let me know. Please review. --- Kalle Valo (2): OMAP: remove OMAP_TAG_UART OMAP: remove OMAP_TAG_SERIAL_CONSOLE arch/arm/mach-omap1/board-ams-delta.c|5 +-- arch/arm/mach-omap1/board-fsample.c |5 +-- arch/arm/mach-omap1/board-generic.c |5 +-- arch/arm/mach-omap1/board-h2.c |5 +-- arch/arm/mach-omap1/board-h3.c |5 +-- arch/arm/mach-omap1/board-innovator.c|5 +-- arch/arm/mach-omap1/board-nokia770.c |5 +++ arch/arm/mach-omap1/board-osk.c |5 +-- arch/arm/mach-omap1/board-palmte.c |5 +-- arch/arm/mach-omap1/board-palmtt.c |5 +-- arch/arm/mach-omap1/board-palmz71.c |5 +-- arch/arm/mach-omap1/board-perseus2.c |5 +-- arch/arm/mach-omap1/board-sx1.c |5 +-- arch/arm/mach-omap1/board-voiceblue.c|5 +-- arch/arm/mach-omap1/serial.c |8 ++--- arch/arm/mach-omap2/board-2430sdp.c |5 +-- arch/arm/mach-omap2/board-3430sdp.c |5 +-- arch/arm/mach-omap2/board-4430sdp.c |5 +-- arch/arm/mach-omap2/board-apollon.c |5 +-- arch/arm/mach-omap2/board-generic.c |5 +-- arch/arm/mach-omap2/board-h4.c |5 +-- arch/arm/mach-omap2/board-ldp.c |5 +-- arch/arm/mach-omap2/board-omap3beagle.c |5 +-- arch/arm/mach-omap2/board-omap3evm.c |5 +-- arch/arm/mach-omap2/board-omap3pandora.c |5 +-- arch/arm/mach-omap2/board-overo.c|5 +-- arch/arm/mach-omap2/board-rx51.c |5 +-- arch/arm/mach-omap2/board-zoom2.c|5 +-- arch/arm/mach-omap2/serial.c |9 ++ arch/arm/plat-omap/common.c | 44 -- arch/arm/plat-omap/include/mach/board.h |4 +-- arch/arm/plat-omap/include/mach/serial.h |4 ++- 32 files changed, 66 insertions(+), 138 deletions(-) -- 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/majordomo-info.html
[PATCH 1/2] OMAP: remove OMAP_TAG_SERIAL_CONSOLE
Omap tags are deprecated and remove OMAP_TAG_SERIAL_CONSOLE. Console must be
enabled with the console boot parameter instead.
Signed-off-by: Kalle Valo kalle.v...@iki.fi
---
arch/arm/plat-omap/common.c | 44 ---
arch/arm/plat-omap/include/mach/board.h |1 -
2 files changed, 0 insertions(+), 45 deletions(-)
diff --git a/arch/arm/plat-omap/common.c b/arch/arm/plat-omap/common.c
index ebcf006..f37a29a 100644
--- a/arch/arm/plat-omap/common.c
+++ b/arch/arm/plat-omap/common.c
@@ -127,50 +127,6 @@ const void *omap_get_var_config(u16 tag, size_t *len)
}
EXPORT_SYMBOL(omap_get_var_config);
-static int __init omap_add_serial_console(void)
-{
- const struct omap_serial_console_config *con_info;
- const struct omap_uart_config *uart_info;
- static char speed[11], *opt = NULL;
- int line, i, uart_idx;
-
- uart_info = omap_get_config(OMAP_TAG_UART, struct omap_uart_config);
- con_info = omap_get_config(OMAP_TAG_SERIAL_CONSOLE,
- struct omap_serial_console_config);
- if (uart_info == NULL || con_info == NULL)
- return 0;
-
- if (con_info-console_uart == 0)
- return 0;
-
- if (con_info-console_speed) {
- snprintf(speed, sizeof(speed), %u, con_info-console_speed);
- opt = speed;
- }
-
- uart_idx = con_info-console_uart - 1;
- if (uart_idx = OMAP_MAX_NR_PORTS) {
- printk(KERN_INFO Console: external UART#%d.
- Not adding it as console this time.\n,
- uart_idx + 1);
- return 0;
- }
- if (!(uart_info-enabled_uarts (1 uart_idx))) {
- printk(KERN_ERR Console: Selected UART#%d is
- not enabled for this platform\n,
- uart_idx + 1);
- return -1;
- }
- line = 0;
- for (i = 0; i uart_idx; i++) {
- if (uart_info-enabled_uarts (1 i))
- line++;
- }
- return add_preferred_console(ttyS, line, opt);
-}
-console_initcall(omap_add_serial_console);
-
-
/*
* 32KHz clocksource ... always available, on pretty most chips except
* OMAP 730 and 1510. Other timers could be used as clocksources, with
diff --git a/arch/arm/plat-omap/include/mach/board.h
b/arch/arm/plat-omap/include/mach/board.h
index 50ea79a..0d12586 100644
--- a/arch/arm/plat-omap/include/mach/board.h
+++ b/arch/arm/plat-omap/include/mach/board.h
@@ -16,7 +16,6 @@
/* Different peripheral ids */
#define OMAP_TAG_CLOCK 0x4f01
-#define OMAP_TAG_SERIAL_CONSOLE 0x4f03
#define OMAP_TAG_LCD 0x4f05
#define OMAP_TAG_GPIO_SWITCH 0x4f06
#define OMAP_TAG_UART 0x4f07
--
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/majordomo-info.html
[PATCH 2/2] OMAP: remove OMAP_TAG_UART
Omap tags are deprecrated and convert all OMAP_TAG_UART cases to use
omap_uart_platform_data instead.
Tested on rx51 and n8x0. Compile tested on omap_osk_5912.
Signed-off-by: Kalle Valo kalle.v...@iki.fi
---
arch/arm/mach-omap1/board-ams-delta.c|5 ++---
arch/arm/mach-omap1/board-fsample.c |5 ++---
arch/arm/mach-omap1/board-generic.c |5 ++---
arch/arm/mach-omap1/board-h2.c |5 ++---
arch/arm/mach-omap1/board-h3.c |5 ++---
arch/arm/mach-omap1/board-innovator.c|5 ++---
arch/arm/mach-omap1/board-nokia770.c |5 -
arch/arm/mach-omap1/board-osk.c |5 ++---
arch/arm/mach-omap1/board-palmte.c |5 ++---
arch/arm/mach-omap1/board-palmtt.c |5 ++---
arch/arm/mach-omap1/board-palmz71.c |5 ++---
arch/arm/mach-omap1/board-perseus2.c |5 ++---
arch/arm/mach-omap1/board-sx1.c |5 ++---
arch/arm/mach-omap1/board-voiceblue.c|5 ++---
arch/arm/mach-omap1/serial.c |8 +++-
arch/arm/mach-omap2/board-2430sdp.c |5 ++---
arch/arm/mach-omap2/board-3430sdp.c |5 ++---
arch/arm/mach-omap2/board-4430sdp.c |5 ++---
arch/arm/mach-omap2/board-apollon.c |5 ++---
arch/arm/mach-omap2/board-generic.c |5 ++---
arch/arm/mach-omap2/board-h4.c |5 ++---
arch/arm/mach-omap2/board-ldp.c |5 ++---
arch/arm/mach-omap2/board-omap3beagle.c |5 ++---
arch/arm/mach-omap2/board-omap3evm.c |5 ++---
arch/arm/mach-omap2/board-omap3pandora.c |5 ++---
arch/arm/mach-omap2/board-overo.c|5 ++---
arch/arm/mach-omap2/board-rx51.c |5 ++---
arch/arm/mach-omap2/board-zoom2.c|5 ++---
arch/arm/mach-omap2/serial.c |9 +++--
arch/arm/plat-omap/include/mach/board.h |3 +--
arch/arm/plat-omap/include/mach/serial.h |4 +++-
31 files changed, 66 insertions(+), 93 deletions(-)
diff --git a/arch/arm/mach-omap1/board-ams-delta.c
b/arch/arm/mach-omap1/board-ams-delta.c
index 8b40aac..db4d9a4 100644
--- a/arch/arm/mach-omap1/board-ams-delta.c
+++ b/arch/arm/mach-omap1/board-ams-delta.c
@@ -162,7 +162,7 @@ static struct omap_lcd_config ams_delta_lcd_config
__initdata = {
.ctrl_name = internal,
};
-static struct omap_uart_config ams_delta_uart_config __initdata = {
+static struct omap_uart_platform_data ams_delta_uart_config __initdata = {
.enabled_uarts = 1,
};
@@ -174,7 +174,6 @@ static struct omap_usb_config ams_delta_usb_config
__initdata = {
static struct omap_board_config_kernel ams_delta_config[] = {
{ OMAP_TAG_LCD, ams_delta_lcd_config },
- { OMAP_TAG_UART,ams_delta_uart_config },
};
static struct resource ams_delta_kp_resources[] = {
@@ -225,7 +224,7 @@ static void __init ams_delta_init(void)
omap_board_config = ams_delta_config;
omap_board_config_size = ARRAY_SIZE(ams_delta_config);
- omap_serial_init();
+ omap_serial_init(ams_delta_uart_config);
omap_register_i2c_bus(1, 100, NULL, 0);
/* Clear latch2 (NAND, LCD, modem enable) */
diff --git a/arch/arm/mach-omap1/board-fsample.c
b/arch/arm/mach-omap1/board-fsample.c
index 19e0e92..3eda799 100644
--- a/arch/arm/mach-omap1/board-fsample.c
+++ b/arch/arm/mach-omap1/board-fsample.c
@@ -240,7 +240,7 @@ static int nand_dev_ready(struct omap_nand_platform_data
*data)
return gpio_get_value(P2_NAND_RB_GPIO_PIN);
}
-static struct omap_uart_config fsample_uart_config __initdata = {
+static struct omap_uart_platform_data fsample_uart_config __initdata = {
.enabled_uarts = ((1 0) | (1 1)),
};
@@ -249,7 +249,6 @@ static struct omap_lcd_config fsample_lcd_config __initdata
= {
};
static struct omap_board_config_kernel fsample_config[] = {
- { OMAP_TAG_UART,fsample_uart_config },
{ OMAP_TAG_LCD, fsample_lcd_config },
};
@@ -266,7 +265,7 @@ static void __init omap_fsample_init(void)
omap_board_config = fsample_config;
omap_board_config_size = ARRAY_SIZE(fsample_config);
- omap_serial_init();
+ omap_serial_init(fsample_uart_config);
omap_register_i2c_bus(1, 100, NULL, 0);
}
diff --git a/arch/arm/mach-omap1/board-generic.c
b/arch/arm/mach-omap1/board-generic.c
index e724940..d700277 100644
--- a/arch/arm/mach-omap1/board-generic.c
+++ b/arch/arm/mach-omap1/board-generic.c
@@ -57,12 +57,11 @@ static struct omap_usb_config generic1610_usb_config
__initdata = {
};
#endif
-static struct omap_uart_config generic_uart_config __initdata = {
+static struct omap_uart_platform_data generic_uart_config __initdata = {
.enabled_uarts = ((1 0) | (1 1) | (1 2)),
};
static struct omap_board_config_kernel generic_config[] __initdata = {
- { OMAP_TAG_UART,generic_uart_config },
};
static void __init omap_generic_init(void)
@@ -80,7 +79,7 @@ static void __init
Re: N8x0 to mainline patches
Felipe Balbi felipe.ba...@nokia.com writes: Hi, On Mon, Jul 13, 2009 at 07:51:10AM +0200, ext Kalle Valo wrote: Hello, I started working on adding N8x0 support to mainline, currently serial console works and I can mount initfs and rootfs on N800. The patches are available here: http://www.valot.fi/kalle/n8x0/patches/n8x0-add/ I'd say at least patch #2 should be sent for to l-o right now since it gets rid of another OMAP_TAG. I didn't implement omap1 part yet. As soon as I have done that, I'll send it. All the other patches (besides #1) Yeah, patch #1 is some weird linker magic which I need to look at more. The patch is in the set just to get things started and I'll remove it from the final patchset. look fine and I guess you could send all of them here for people to take a look at. Ok, I'll do that soon but I'll try to implement a bit more to the board file first. But patch #2 clearly doesn't belong to that series and should be integrated I agree. But isn't Tony on vacation the whole July and there is nobody to push it to linux-omap? Thanks for looking at the patches! -- Kalle Valo -- 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/majordomo-info.html
Re: N8x0 to mainline patches
Luke-Jr l...@dashjr.org writes: I noticed that the patch adding board-n8x0.c seems to be much smaller than the older one used in Linux-OMAP. In particular, it lacks the keymaps and such. Are those somewhere else now? It's just not implemented yet. If you look at the plan, you see lots of things we need to implement: http://www.elinux.org/N800#The_Plan Was the Linux-OMAP keyboard bug taken into consideration for the new keyboard config struct? I'm not familiar with the issue. But if it makes sense, sure, we want to include the fix. -- Kalle Valo -- 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/majordomo-info.html
N8x0 to mainline patches
Hello, I started working on adding N8x0 support to mainline, currently serial console works and I can mount initfs and rootfs on N800. The patches are available here: http://www.valot.fi/kalle/n8x0/patches/n8x0-add/ To get all this coordinated, I created a wiki page for this: http://elinux.org/N800 If there's something wrong or missing, please update it or send me an email so that I can update it. -- Kalle Valo -- 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/majordomo-info.html
mainline: misc.o uses VFP instructions error
Hello, I'm trying to compile omap_generic_2420_defconfig in mainline and I get this error: Kernel: arch/arm/boot/Image is ready LD arch/arm/boot/compressed/vmlinux arm-linux-ld: ERROR: arch/arm/boot/compressed/misc.o uses VFP instructions, whereas arch/arm/boot/compressed/vmlinux does not arm-linux-ld: failed to merge target specific data of file arch/arm/boot/compressed/misc.o Here are the exact commands I used: make ARCH=arm CROSS_COMPILE=arm-linux- clean make ARCH=arm CROSS_COMPILE=arm-linux- mrproper make ARCH=arm CROSS_COMPILE=arm-linux- omap_generic_2420_defconfig make ARCH=arm CROSS_COMPILE=arm-linux- -j 2 The compiler and linker used: $ arm-linux-gcc -v Using built-in specs. Target: arm-none-eabi Configured with: /scratch/julian/lite-respin/eabi/src/gcc-4.3/configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=arm-none-eabi --enable-threads --disable-libmudflap --disable-libssp --disable-libstdcxx-pch --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --disable-shared --with-newlib --with-pkgversion='Sourcery G++ Lite 2008q3-66' --with-bugurl=https://support.codesourcery.com/GNUToolchain/ --disable-nls --prefix=/opt/codesourcery --with-headers=yes --with-sysroot=/opt/codesourcery/arm-none-eabi --with-build-sysroot=/scratch/julian/lite-respin/eabi/install/arm-none-eabi --with-gmp=/scratch/julian/lite-respin/eabi/obj/host-libs-2008q3-66-arm-none-eabi-i686-pc-linux-gnu/usr --with-mpfr=/scratch/julian/lite-respin/eabi/obj/host-libs-2008q3-66-arm-none-eabi-i686-pc-linux-gnu/usr --disable-libgomp --enable-poison-system-directories --with-build-time-tools=/scratch/julian/lite-respin/eabi/install/arm-none-eabi/bin --with-build-time-tools=/scratch/julian/lite-respin/eabi/install/arm-none-eabi/bin Thread model: single gcc version 4.3.2 (Sourcery G++ Lite 2008q3-66) $ arm-linux-ld -v GNU ld (Sourcery G++ Lite 2008q3-66) 2.18.50.20080215 $ The commit in question is 746a99a5af6 (2.6.31-rc1 plus something on top) from Linus' tree. Any ideas why this is happening? The same toolchain has worked fine with n800 code in linux-omap. -- Kalle Valo -- 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/majordomo-info.html
Re: mainline: misc.o uses VFP instructions error
On Sat, Jul 4, 2009 at 6:12 PM, Kalle Valokalle.v...@iki.fi wrote: I'm trying to compile omap_generic_2420_defconfig in mainline and I get this error: Kernel: arch/arm/boot/Image is ready LD arch/arm/boot/compressed/vmlinux arm-linux-ld: ERROR: arch/arm/boot/compressed/misc.o uses VFP instructions, whereas arch/arm/boot/compressed/vmlinux does not arm-linux-ld: failed to merge target specific data of file arch/arm/boot/compressed/misc.o I tried omap3_beagle_defconfig and it compiled without errors. I found discussion about the error here: http://www.spinics.net/lists/arm-kernel/msg59073.html And reverting this commit fixed the issue with omap_generic_2420_defconfig: commit 80cec14a83ad0ad109d822b3f3482a379bc481ba Author: Russell King r...@dyn-67.arm.linux.org.uk Date: Tue Sep 9 13:56:45 2008 +0100 [ARM] Add -march=all to assembly file build in arch/arm/boot/compressed This allows assembly files to be crafted to cover all ARM CPU types rather than erroring out on instructions only in later CPUs. We are careful in these files to only execute CPU specific code when the CPU ID says we can. Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk -- 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/majordomo-info.html
Re: [PATCH] OMAP: McSPI: Fix RX DMA transfer path
Tony Lindgren t...@atomide.com writes:
I will test this patch as soon as I get N800 boot with latest
linux-omap, now I only get this:
6JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
6JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red H
6msgmni has been set to 247
6io scheduler noop registered (default)
6omapfb: ls041y3 rev 87 LCD detected, 0 data lines d
6serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
6serial8250.0: ttyS1 at MMIO 0x4806e000 (irq = 74) is a ST16654
óF:5 #!*$Õó¬#05 #!*$Õór%
µ²² æ2Õó$¶ #®*#5##¹'%Õó#62°$¶ ¹)K!¥º¹'Õó¬¹5 K#z 0«²)Ñ%f¡T:6æ0ªÿó¯
ó
%°ö2Õ³#²©T ô#.#É ,#2¬#£µ0V³/5 V§Í#%Ríó00¢F ô- ¹##£$¶ +3Síó
0
·#
# V60±:)¥#
,#µ¥Õ46 V#Õ#
¬é)¶.¹ªÿóµ£É%²:©F%V$®º ¹##£$¶
Í#É¡*ªÿóµ ©#0Á:£µ.#µ¥Õ4#Ô#Kªÿ#ó#Í!Ä)
%
³3{%°ö2±9±SíóÕ {/+#í#ó#Í!Ä)4?+#í#ó#Í!Ä)4ó ö£U4¬¹ ¹)K!)ºªÿóÕ%{/C:³ô
Ù¯s
®Ñ ®®Ò 335#U2,°®!Ä) ô2V#ö/ë¢#4/##®#%!V C%!
Might be related to the omap specific ATAGs now gone, sorry but that
just had to go to get things in sync. And it should not come as a
surprise as it's been discussed over past few years :)
Yeah, I understand. Better do it properly, it will get easier soon.
The missing data needs to be initialized in platform_data, cmdline,
ARM generic ATAGs, upcoming device tree.. I suggest using platform_data
where possible. The GPIO values etc coming from nolo can be dumped
with some earlier kernel using CONFIG_ATAGS_PROC.
Thanks for the help, all hints are greatly appreciated. And as soon as I
manage to finish a personal project of mine I'll start looking at this
in detail.
BTW, I'll move the n8x0 board-*.c files around a bit to have just
board-n800.c, board-n810.c and board-n8x0-peripherals.c.
Sounds good.
--
Kalle Valo
--
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/majordomo-info.html
Re: [PATCH] TWL4030: Reset header file to mainline
Mark Brown broo...@opensource.wolfsonmicro.com writes: On Wed, Jun 17, 2009 at 06:20:24PM +0400, Eugeny S. Mints wrote: Tony Lindgren wrote: Anything touching arch/arm/*omap*. I'm not sure how many non-omap based boards out there are using twl4030 chip and if a separate mfd mail list exists. But until any of the above is true I personally feel that twl4030 related discussions naturally fall into omap mail list. While the overwhelming majority of TWL4030 specifics will only actually be seen on OMAP systems (so CCing the OMAP list makes sense) the code also exists in the context of the rest of the kernel. It needs review by subsystem maintainers and people working on non-OMAP systems may have useful input based on their general experience of working on simiar parts - in general Linux terms the fact that you've got, for example, a keyboard controller is at least as relevant as the fact that it's likely to be used on an OMAP system. Many subsystems don't have a separate list and just use linux-kernel. Yes, and nobody will blame if you CCed linux-omap list twl4030, quite the opposite. Even if all omap code is in mainline, it doesn't mean that this list will fade away. I would anticipate even the opposite, more people might get interested. -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH] OMAP: McSPI: Fix RX DMA transfer path
Aaro Koskinen aaro.koski...@nokia.com writes:
From: Eero Nurkkala ext-eero.nurkk...@nokia.com
When data is read through DMA, the last element must be read separately
through the RX register. It cannot be transferred by the DMA. For further
details see e.g. OMAP3430 TRM.
Without the fix the driver causes extra clocks to be clocked to the
bus after DMA RX operations. This can cause interesting behaviour with
some devices.
I was hit by this with stlc45xx and earlier versions of Juuso's patch at
least fixed the problem.
I will test this patch as soon as I get N800 boot with latest
linux-omap, now I only get this:
6JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
6JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red H
6msgmni has been set to 247
6io scheduler noop registered (default)
6omapfb: ls041y3 rev 87 LCD detected, 0 data lines d
6serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
6serial8250.0: ttyS1 at MMIO 0x4806e000 (irq = 74) is a ST16654
óF:5 #!*$Õó¬#05 #!*$Õór%
µ²² æ2Õó$¶ #®*#5##¹'%Õó#62°$¶ ¹)K!¥º¹'Õó¬¹5 K#z 0«²)Ñ%f¡T:6æ0ªÿó¯
ó
%°ö2Õ³#²©T ô#.#É ,#2¬#£µ0V³/5 V§Í#%Ríó00¢F ô- ¹##£$¶ +3Síó
0
·#
# V60±:)¥#
,#µ¥Õ46 V#Õ#
¬é)¶.¹ªÿóµ£É%²:©F%V$®º ¹##£$¶
Í#É¡*ªÿóµ ©#0Á:£µ.#µ¥Õ4#Ô#Kªÿ#ó#Í!Ä)
%
³3{%°ö2±9±SíóÕ {/+#í#ó#Í!Ä)4?+#í#ó#Í!Ä)4ó ö£U4¬¹ ¹)K!)ºªÿóÕ%{/C:³ô
Ù¯s
®Ñ ®®Ò 335#U2,°®!Ä) ô2V#ö/ë¢#4/##®#%!V C%!
--
Kalle Valo
--
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/majordomo-info.html
n800 can't mount rootfs
] (mount_block_root+0x25c/0x2ac) from [c0009020] (prepare_namespace+0x164/0x1bc) [5.578125] [c0009020] (prepare_namespace+0x164/0x1bc) from [c0008400] (kernel_init+0xb8/0xe4) [5.587249] [c0008400] (kernel_init+0xb8/0xe4) from [c004d498] (do_exit+0x0/0x580) [5.595306] [c004d498] (do_exit+0x0/0x580) from [0001] (0x1) -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH 05/10] ARM: OMAP1: Make 770 LCD work
Andrew de Quincey adq_...@lidskialf.net writes:
Out of interest, what is the best practice way to pass platform
specific GPIOs around? There are a number of other n770 related
drivers I'm intending on cleaning up, several of which have GPIO
numbers hardcoded in them. Should these be passed in platform
structures, or is there something analogous to the clk_alias for
GPIOs?
I was told that platform structures are the preferred way. For wl12xx (a
wi-fi driver) I created a set_power function pointer which will control
the power gpio line:
27 struct wl12xx_platform_data {
28 void (*set_power)(bool enable);
29 };
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=blob;f=include/linux/spi/wl12xx.h;h=11430cab2aad71242946ebfc7c0ce778d8bf26a1;hb=HEAD
And the irq is configured in the board file and provided to wl12xx with
struct spi_device.irq. So wl12xx doesn't use gpio code at all, it's all
done in the board file.
Please comment if this isn't the correct way to do this.
--
Kalle Valo
--
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/majordomo-info.html
Re: N810: latest linux-omap-2.6.git master
Tony Lindgren t...@atomide.com writes: Is anyone actually trying to work on or maintain N8x0 support? I think N8x0 support is a little bit behind from other boards. Lot of active development is going around on newer and more open platforms like Beagle and not all patches are necessary tested on N8x0 (or other boards too!). Of course active hacker base helps to point out breakages. We should try to get the board-n8x0 stuff in shape for mainline maybe the next merge window after this, anybody willing to spend some cycles on preparing the patches against the mainline tree? So that's something like three months from now? Hmm. If someone else doesn't volunteer I can try to spend some time on this. I would love to see n800 and n810 supported in mainline. But I cannot make any promises, though. It would be great if someone else can step up. -- Kalle Valo -- 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/majordomo-info.html
Re: N810: latest linux-omap-2.6.git master
Tony Lindgren t...@atomide.com writes: OK, I can help a bit too. Here's what I have in mind we should do: - Rename the board-*c files to board-n8x0-*.c. I can do this assuming people are OK with this. - Get the gpio-switch replacement completed and into mainline. Jani, any news on that? There's a threaad about that at: http://thread.gmane.org/gmane.linux.kernel/809866 - Stop using omap specific ATAGs and pass all the gpio etc info from platform_data. This should be easy with CONFIG_ATAGS_PROC that shows the passed ATAGs in /proc. I can work on this too. - Get drivers/cbus into mainline. Kalle, do you want to do this? Sure, I can work with cbus. I can't give any promises how long it will take, so don't have your hopes up :) I guess there's some other clean-up needed too that we can all work once we have the initial patches working against the mainline. Yes, I agree. For reference, we discussed a bit about this last September: http://www.spinics.net/lists/linux-omap/msg05505.html -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH] OMAP_LDP: Support LCD display as a FB device on ZOOM MDK (Re: LDP support)
Russell King - ARM Linux li...@arm.linux.org.uk writes: On Fri, May 08, 2009 at 07:47:09PM +0300, Kalle Valo wrote: stanley.miao stanley.m...@windriver.com writes: Looks like you used the CodeSourcery 2007q3 toolchain. This had been reported earlier. Switching to 2008q3 works. Yeah, Now the kernel booted. it's compiler's problem. I was bitten by the same problem few weeks ago. Any chance of getting a warning/error if using 2007q3 compiler until the problem is fixed? Is there any way of detecting the 2007q3 compiler? With normal GCC versions, you can use __GNUC__, __GNUC_MINOR__ and __GNUC_PATCHLEVEL__ to identify the three digit version number. I don't know, most probably not. But Jon Hunter investigated the issue and he found the issue was related to CONFIG_ARCH_WANT_FRAME_POINTERS: http://www.mail-archive.com/linux-omap@vger.kernel.org/msg12403.html So maybe we can fix or workaround this. -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH] OMAP_LDP: Support LCD display as a FB device on ZOOM MDK (Re: LDP support)
stanley.miao stanley.m...@windriver.com writes: Looks like you used the CodeSourcery 2007q3 toolchain. This had been reported earlier. Switching to 2008q3 works. Yeah, Now the kernel booted. it's compiler's problem. I was bitten by the same problem few weeks ago. Any chance of getting a warning/error if using 2007q3 compiler until the problem is fixed? -- Kalle Valo -- 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/majordomo-info.html
Re: No 2.6.29 omap tag?
Felipe Contreras felipe.contre...@gmail.com writes: Hi, Hello, Is there a reason why there is no v2.6.29-omap1 tag? I don't know. But at least there's a branch named omap-2.6.29 and I used that. -- Kalle Valo -- 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/majordomo-info.html
Re: n800 high idle power consumption
Kevin Hilman khil...@deeprootsystems.com writes: Kalle Valo kalle.v...@iki.fi writes: Hello all, I was testing 2.6.30-rc3-omap1 on n800 and noticed that idle power consumption is very high, ten times compared to a 2.6.29 I tested few weeks back. I'm guessing that CPU doesn't sleep at all. Is this a regression? How should I debug this further? Between .29 and .30, the PM code in l-o was dropped and re-sync'd to kernel.org code. This is so that PM can be separated out into a separate branch and submitted upstream independently. Ah, of course. I read about this but didn't understand the implications :) Thanks for pointing this out to me. The current PM branch is in the process of being re-based onto 2.6.30. When it's ready, I'd appreciate any testing on n800. Ok. Please let me know when it's ready. -- Kalle Valo -- 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/majordomo-info.html
Re: n800 build error in clock24xx.c: 'secure_32k_ck' undeclared
Paul Walmsley p...@pwsan.com writes: Hi Kalle, Hi Paul, sorry for a late answer. On Fri, 17 Apr 2009, Kalle Valo wrote: arch/arm/mach-omap2/clock24xx.h:1801: error: 'secure_32k_ck' undeclared here (not in a function) Any hints? This is a bug in the version of fa9ef57a1efdd4e7c41a42db71d99b9b69e9b356 I pushed. The new clock definition in clock24xx.h for secure_32k_fck should be for secure_32k_ck. Just talked with Tony about this; he's going to re-pull a fixed version of that patch today. I updated to latest linux-omap (commit 55b1274c). It now compiles and boots on N800. Thank you for fixing this. -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH] ARM: OMAP: Fix tusb6010 init error and compilation warning
Jarkko Nikula jarkko.nik...@nokia.com writes: Fix tusb6010 init error 5, -19 and compilation warning from function tusb6010_platform_retime warning: 'sysclk_ps' is used uninitialized in this function. I suppose commit c094ba34b8f780885d029ce3c2715a194b780e5d was meant to test for zero fclk_ps instead of sysclk_ps. I was suffering exactly this problem and this patch fixed it. Now usb network works again, thanks a lot for fixing this! Signed-off-by: Jarkko Nikula jarkko.nik...@nokia.com Cc: Roel Kluin roel.kl...@gmail.com Tested-by: Kalle Valo kalle.v...@iki.fi -- Kalle Valo -- 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/majordomo-info.html
stlc45xx in 2.6.30-rc1
Hello, I just want to inform that stlc45xx (wi-fi driver for n800/n810) is now in 2.6.30-rc1 staging directory. I just tried with latest linux-omap and I was able to associate to an AP and ping. Here's the config entry: config STLC45XX tristate stlc4550/4560 support depends on MAC80211 WLAN_80211 SPI_MASTER ---help--- This is a driver for stlc4550 and stlc4560 chipsets. To compile this driver as a module, choose M here: the module will be called stlc45xx. If unsure, say N. There is ongoing work to add spi support to p54 by the community. stlc45xx will be just an interim solution and it will be removed as soon as p54 catches up. The stlc45xx git repo at gitorius.org will phase out soon. -- Kalle Valo -- 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/majordomo-info.html
n800 high idle power consumption
Hello all, I was testing 2.6.30-rc3-omap1 on n800 and noticed that idle power consumption is very high, ten times compared to a 2.6.29 I tested few weeks back. I'm guessing that CPU doesn't sleep at all. Is this a regression? How should I debug this further? -- Kalle Valo -- 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/majordomo-info.html
Re: n800 high idle power consumption
Kalle Valo kalle.v...@iki.fi writes: Hello all, Hello again, I was testing 2.6.30-rc3-omap1 on n800 and noticed that idle power consumption is very high, ten times compared to a 2.6.29 I tested few weeks back. I'm guessing that CPU doesn't sleep at all. Is this a regression? How should I debug this further? Oh yeah, I forgot to mention that I have included Jarkko's patch ARM: OMAP: Fix tusb6010 init error and compilation warning in my builds. Otherwise usb won't work. -- Kalle Valo -- 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/majordomo-info.html
Re: n800 build error in clock24xx.c: 'secure_32k_ck' undeclared
green greenfreedo...@gmail.com writes: Kalle Valo wrote at 2009-04-17 14:44 -0600: arch/arm/kernel/sys_oabi-compat.c: In function 'sys_oabi_epoll_wait': arch/arm/kernel/sys_oabi-compat.c:289: error: implicit declaration of function 'kmalloc' arch/arm/kernel/sys_oabi-compat.c:289: warning: assignment makes pointer from integer without a cast arch/arm/kernel/sys_oabi-compat.c:302: error: implicit declaration of function 'kfree' arch/arm/kernel/sys_oabi-compat.c: In function 'sys_oabi_semtimedop': arch/arm/kernel/sys_oabi-compat.c:325: warning: assignment makes pointer from integer without a cast I see nearly the same: arch/arm/kernel/sys_oabi-compat.c: In function ‘sys_oabi_epoll_wait’: arch/arm/kernel/sys_oabi-compat.c:288: error: implicit declaration of function ‘kmalloc’ arch/arm/kernel/sys_oabi-compat.c:288: error: ‘GFP_KERNEL’ undeclared (first use in this function) I think that's the same error. Most probably my tree was dirty and that's the line numbers are different. -- Kalle Valo -- 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/majordomo-info.html
Re: controlling CPU speed on N800/N810
Igor Stoppa igor.sto...@nokia.com writes: Hi, On Sat, 2009-04-04 at 09:58 +0200, ext Kalle Valo wrote: Is it possible to change CPU speed in latest linux-omap kernels? afaik, no, but that makes your job easier, the ARM clock should be 330MHz - at least that's what TI supports and recommends when also the DSP is in use Ok, thanks for the info. I got better wi-fi throughput with nokia 2.6.21 kernel compared to linux-omap kernels, but the CPU speed difference will most likely explain that. I'm assuming that DVFS increased the CPU speed over 400 MHz when running throughtput tests on nokia 2.6.21 kernel. If anyone have hints or pointers how to overclock linux-omap kernels, I'm all ears :) -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH 3/3] Disable linux-omap version of menelaus
Tony Lindgren t...@atomide.com writes: diff --git a/drivers/i2c/chips/Makefile b/drivers/i2c/chips/Makefile index b451369..d8bef8c 100644 --- a/drivers/i2c/chips/Makefile +++ b/drivers/i2c/chips/Makefile @@ -18,7 +18,6 @@ obj-$(CONFIG_SENSORS_PCA9539)+= pca9539.o obj-$(CONFIG_SENSORS_PCF8574) += pcf8574.o obj-$(CONFIG_PCF8575) += pcf8575.o obj-$(CONFIG_SENSORS_PCF8591) += pcf8591.o -obj-$(CONFIG_MENELAUS)+= menelaus.o I'll also remove drivers/i2c/chips/menelaus.c. Thanks. It's nice to see drivers going to upstream. -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH 2/3] tsub6010: fix omap compile
Felipe Balbi felipe.ba...@nokia.com writes: On Thu, Jan 22, 2009 at 06:10:52PM -0800, Tony Lindgren wrote: * Kalle Valo kalle.v...@nokia.com [090122 05:21]: drivers/usb/musb/tusb6010_omap.c:18:26: error: asm/arch/dma.h: No such file or directory drivers/usb/musb/tusb6010_omap.c:19:26: error: asm/arch/mux.h: No such file or directory Not touching this, Felipe needs to queue this up via linux-usb list. sure, kalle, could you resend to linux-...@vger.kernel.org ?? Ok, I will. also, sure to Cc me Tá bom :) -- Kalle Valo -- 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/majordomo-info.html
[PATCH] musb: fix tusb6010_omap compilation errors
drivers/usb/musb/tusb6010_omap.c:18:26: error: asm/arch/dma.h: No such file or directory drivers/usb/musb/tusb6010_omap.c:19:26: error: asm/arch/mux.h: No such file or directory Signed-off-by: Kalle Valo kalle.v...@nokia.com --- drivers/usb/musb/tusb6010_omap.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/usb/musb/tusb6010_omap.c b/drivers/usb/musb/tusb6010_omap.c index 52f7f29..7e073a0 100644 --- a/drivers/usb/musb/tusb6010_omap.c +++ b/drivers/usb/musb/tusb6010_omap.c @@ -15,8 +15,8 @@ #include linux/usb.h #include linux/platform_device.h #include linux/dma-mapping.h -#include asm/arch/dma.h -#include asm/arch/mux.h +#include mach/dma.h +#include mach/mux.h #include musb_core.h -- 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/majordomo-info.html
[PATCH 0/3] Hacks to make Nokia N800 compile
In currently linux-omap tree n800_defconfig doesn't compile because of few compiler and linker errors. Here are the fixes/hacks which I use. I'll send them in case anyone else is interested them. --- Kalle Valo (3): Disable linux-omap version of menelaus tsub6010: fix omap compile n800-bt: include board-nokia.h arch/arm/mach-omap2/board-n800-bt.c |1 + drivers/i2c/chips/Makefile |1 - drivers/usb/musb/tusb6010_omap.c|4 ++-- 3 files changed, 3 insertions(+), 3 deletions(-) -- 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/majordomo-info.html
[PATCH 2/3] tsub6010: fix omap compile
drivers/usb/musb/tusb6010_omap.c:18:26: error: asm/arch/dma.h: No such file or directory drivers/usb/musb/tusb6010_omap.c:19:26: error: asm/arch/mux.h: No such file or directory Signed-off-by: Kalle Valo kalle.v...@nokia.com --- drivers/usb/musb/tusb6010_omap.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/usb/musb/tusb6010_omap.c b/drivers/usb/musb/tusb6010_omap.c index 52f7f29..7e073a0 100644 --- a/drivers/usb/musb/tusb6010_omap.c +++ b/drivers/usb/musb/tusb6010_omap.c @@ -15,8 +15,8 @@ #include linux/usb.h #include linux/platform_device.h #include linux/dma-mapping.h -#include asm/arch/dma.h -#include asm/arch/mux.h +#include mach/dma.h +#include mach/mux.h #include musb_core.h -- 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/majordomo-info.html
[PATCH] n800-bt: include board-nokia.h
Fixes compilation error:
arch/arm/mach-omap2/board-n800-bt.c: In function 'n800_bt_init':
arch/arm/mach-omap2/board-n800-bt.c:36: error: 'OMAP_TAG_NOKIA_BT' undeclared
(first use in this function)
arch/arm/mach-omap2/board-n800-bt.c:36: error: (Each undeclared identifier is
reported only once
arch/arm/mach-omap2/board-n800-bt.c:36: error: for each function it appears in.)
arch/arm/mach-omap2/board-n800-bt.c:36: error: invalid application of 'sizeof'
to incomplete type 'struct omap_bluetooth_config'
Signed-off-by: Kalle Valo kalle.v...@nokia.com
---
arch/arm/mach-omap2/board-n800-bt.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-n800-bt.c
b/arch/arm/mach-omap2/board-n800-bt.c
index 61afd2b..da3a7bb 100644
--- a/arch/arm/mach-omap2/board-n800-bt.c
+++ b/arch/arm/mach-omap2/board-n800-bt.c
@@ -22,6 +22,7 @@
#include linux/kernel.h
#include linux/platform_device.h
#include mach/board.h
+#include mach/board-nokia.h
static struct platform_device n800_bt_device = {
.name = hci_h4p,
--
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/majordomo-info.html
Re: Nokia Internet Tablets
ext Felipe Balbi felipe.ba...@nokia.com writes: On Mon, Dec 22, 2008 at 04:34:22AM -0600, ext Otto Solares wrote: Hi all! I want to resurrect missing support for the Nokia Internet Tablets starting with the N8x0s for my NITdroid project, which uses just standard Linux kernel APIs. So first I would like to ask some very newbie questions: -Is there any ongoing effort to support these devices in latest kernels at the same level as the latest Nokia production kernel (2.6.21-omap)? n8x0 devices should boot fine with current linux-omap and I'd say we have all the drivers here as well, besides audio, camera and wifi (me thinks) For wifi there is stlc45xx: http://stlc45xx.garage.maemo.org/ Also Christian Lamparter is adding stlc4550 support to p54, check linux-wireless list archives for more (search for p54spi). -- Kalle Valo -- 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/majordomo-info.html
Re: N810 suspend
ext Paul Walmsley p...@pwsan.com writes: N810 didn't went and think reason is that bootloader enables UART3 for the GPS chip. I noticed this as well. Any hacks to workaround this? Or do I really need to start searching for N800? :) hey Kevin, did your serial port idle code ever work out? I wonder if that would work for the N810s... Any patches anywhere? I would gladly test something. -- Kalle Valo -- 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/majordomo-info.html
Re: [PATCH] Add stlc45xx, wi-fi driver for stlc4550/4560
Johannes Berg [EMAIL PROTECTED] writes:
On Sat, 2008-12-06 at 19:32 +0200, Kalle Valo wrote:
+static const u8 default_cal_channels[] = {
+0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
+0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x6c, 0x09,
[...]
+0x00 };
+
+static const u8 default_cal_rssi[] = {
+0x0a, 0x01, 0x72, 0xfe, 0x1a, 0x00, 0x00, 0x00, 0x0a, 0x01, 0x72,
[...]
+0x00, 0x00, 0x00, 0x00, 0x00 };
Is this data actually usable?
Yes, it is. I tested it yesterday and it works ok.
The static data in cx3110x didn't even parse correctly iirc.
I don't even remember cx3110x having any static calibration data,
wlan-cal provided it always. But then again I haven't looked at
cx3110x for a long time, I might remember wrong.
+static void stlc45xx_tx_edcf(struct stlc45xx *stlc);
+static void stlc45xx_tx_setup(struct stlc45xx *stlc);
+static void stlc45xx_tx_scan(struct stlc45xx *stlc);
+static void stlc45xx_tx_psm(struct stlc45xx *stlc, bool enable);
+static int stlc45xx_tx_nullfunc(struct stlc45xx *stlc, bool powersave);
+static int stlc45xx_tx_pspoll(struct stlc45xx *stlc, bool powersave);
Can you reorder the file?
Sure.
And I think you must be basing this on top of your PS patches, so
could you not put Vivek's in the middle too?
Actually I didn't use my PS patches when I tested this patch. But
true, I should try Vivek's patch also with stlc45xx.
+static ssize_t stlc45xx_sysfs_store_cal_rssi(struct device *dev,
+ struct device_attribute *attr,
+ const char *buf, size_t count)
I still think it would be better to use the firmware framework with a
custom helper for this. At least it should provide a uevent like crda
does so userspace knows automatically when to upload the files after you
reload the module for example, I think?
Yeah, you talked about this already and I liked it. I haven't
implemented it just because a lack of time. I'll add it to the todo
list.
+static ssize_t stlc45xx_sysfs_show_tx_buf(struct device *dev,
+ struct device_attribute *attr,
+ char *buf)
+{
That should be in debugfs, I think?
I think I should even remove it.
+static int stlc45xx_request_firmware(struct stlc45xx *stlc)
+{
+const struct firmware *fw;
+int ret;
+
+/* FIXME: should driver use it's own struct device? */
+ret = request_firmware(fw, 3826.arm, stlc-spi-dev);
own struct device? I don't see why it should? It doesn't have one
anyway, does it?
There is stlc45xx_device:
ret = platform_device_register(stlc45xx_device);
All this device class stuff is not yet fully clear to me, that's why I
added that comment. I guess I should study this more on a boring train
ride.
+static int stlc45xx_upload_firmware(struct stlc45xx *stlc)
+fw_addr = FIRMWARE_ADDRESS;
+fw_len = stlc-fw_len;
+stlc45xx_spi_write(stlc, SPI_ADRS_DMA_DATA, stlc-fw, _fw_len);
+
+/* FIXME: I think this doesn't work if firmware is large,
+ * this loop goes to second round. fw-data is not
+ * increased at all! */
+}
Indeed, the last _spi_write above needs to have something like
stlc-fw + fw_addr - FIRMWARE_ADDRESS
Thanks, I'll fix it at some point.
+/*
+ * FIXME: this gives warning from __ieee80211_rx()
+ *
+ * status.rate_idx = data-rate;
+ */
That works on p54, afaik?
Yes, I haven't looked at this yet.
+edcf-queues[0].aifs = 2;
+edcf-queues[0].pad0 = 1;
+edcf-queues[0].cwmin = 3;
+edcf-queues[0].cwmax = 7;
+edcf-queues[0].txop = 47;
+edcf-queues[1].aifs = 2;
+edcf-queues[1].pad0 = 0;
+edcf-queues[1].cwmin = 7;
+edcf-queues[1].cwmax = 15;
+edcf-queues[1].txop = 94;
+edcf-queues[2].aifs = 3;
+edcf-queues[2].pad0 = 0;
+edcf-queues[2].cwmin = 15;
+edcf-queues[2].cwmax = 1023;
+edcf-queues[2].txop = 0;
+edcf-queues[3].aifs = 7;
+edcf-queues[3].pad0 = 0;
+edcf-queues[3].cwmin = 15;
+edcf-queues[3].cwmax = 1023;
+edcf-queues[3].txop = 0;
Shouldn't that be taking values from mac80211?
Definitely, just has been pending on my todo list.
+setup-bratemask = 0x;
That should also take values from the BSS config.
Will fix.
+scan-flags = LM_SCAN_EXIT;
+scan-bratemask = 0x15f;
or that? not sure
Me neither :)
+static int stlc45xx_op_tx(struct ieee80211_hw *hw, struct sk_buff *skb)
+{
+entry = stlc45xx_txbuffer_alloc(stlc, skb-len);
+if (!entry) {
+/* the queue should be stopped before the firmware buffer
+ * is full, so firmware buffer should always have enough
+ * space */
+if (net_ratelimit())
+stlc45xx_warning(firmware buffer full);
+spin_unlock_bh(stlc
[PATCH] stlc45xx: wi-fi driver for stlc4550/4560 chipset
I would like to submit stlc45xx for inclusion to wireless-testing tree. Currently the main users are Nokia N800 and N810 products. Even though this driver has similarities with p54, I still think it would be a good idea to have the driver in Linux mainline. Linux omap community would benefit from this, having a wi-fi driver in the kernel would make the use of N800 and N810 a lot easier. p54 support for these chipsets is not finished yet. There is still some work to do, for example, add necessary client power save support to mac80211 and modify stlc45xx to use it. Also stlc45xx does not yet use platform data to get all board specific settings, but I will fix that later. And countless others which I don't list here. Please consider including this driver to the wireless-testing tree. --- Kalle Valo (1): Add stlc45xx, wi-fi driver for stlc4550/4560 MAINTAINERS |8 drivers/net/wireless/Kconfig |9 drivers/net/wireless/Makefile|2 drivers/net/wireless/stlc45xx.c | 2594 ++ drivers/net/wireless/stlc45xx.h | 285 drivers/net/wireless/stlc45xx_lmac.h | 434 ++ 6 files changed, 3332 insertions(+), 0 deletions(-) create mode 100644 drivers/net/wireless/stlc45xx.c create mode 100644 drivers/net/wireless/stlc45xx.h create mode 100644 drivers/net/wireless/stlc45xx_lmac.h -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Add stlc45xx, wi-fi driver for stlc4550/4560
Kalle Valo [EMAIL PROTECTED] writes: This patch adds a new driver called stlc45xx, which supports wi-fi chipsets stlc4550 and stlc4560 from ST-NXP Wireless. The chipset can be found, for example, from Nokia N800 and N810 products. The driver is implemented based on the firmware interface information published by ST-NXP Wireless here: http://wireless.kernel.org/en/developers/Documentation/specs#STMicroelectronicshardware Currently only SPI interface is supported. Crap, just now I realised to try to compile this with pristine wireless-testing tree: In file included from drivers/net/wireless/stlc45xx.c:24: drivers/net/wireless/stlc45xx.h:27:24: error: mach/board.h: No such file or directory drivers/net/wireless/stlc45xx.c: In function 'stlc45xx_power_off': drivers/net/wireless/stlc45xx.c:958: error: dereferencing pointer to incomplete type drivers/net/wireless/stlc45xx.c:959: error: dereferencing pointer to incomplete type I usually merge linux-omap to wireless-testing and that's why I didn't notice this. I will implement the platform data solution in v2 which should fix this compile error. But I would still love to hear any comments people have about v1. -- Kalle Valo -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
stlc45xx: open source WLAN driver for N800 and N810
We have just announced an open source WLAN driver for N800 and N810: http://www.gossamer-threads.com/lists/maemo/developers/40474#40474 The web page is here: http://stlc45xx.garage.maemo.org/ Hopefully in the future it will be easier to use latest linux-omap kernel on N800 and N810. -- Kalle Valo -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: stlc45xx: open source WLAN driver for N800 and N810
ext Felipe Balbi [EMAIL PROTECTED] writes: On Fri, Sep 19, 2008 at 12:27:36AM +0300, Kalle Valo wrote: We have just announced an open source WLAN driver for N800 and N810: http://www.gossamer-threads.com/lists/maemo/developers/40474#40474 The web page is here: http://stlc45xx.garage.maemo.org/ Hopefully in the future it will be easier to use latest linux-omap kernel on N800 and N810. Cool, would be nice to get it merged on mainline via linux-wireless ;-) That's what I'll try to do. It might take some time, but I try to get in as early as possible. -- Kalle Valo -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Android on N810 File System Problem
Brian Swetland [EMAIL PROTECTED] writes: [Kalle Valo [EMAIL PROTECTED]] Brian Swetland [EMAIL PROTECTED] writes: This was the show-stopper for me. When I last got things hobbling along on n8x0, the binary-only wlan module was incompatible with newer kernels than 2.6.21 (changes in some network data structures). That's exactly the problem. I have written something about it here: https://garage.maemo.org/pipermail/cx3110x-devel/2007-December/07.html Just did a quick diff between v2.6.21 and v2.6.24 and the skbuff changes are pretty daunting. Doesn't look like there's an easy hack here... Currently there's nothing I can do to resolve the issue, unfortunately. Pity. It'd be nice to get newer kernels running on the n8x0 -- it's nice hardware. Trust me, I share the pain. If a solution comes up, I'll let you know. It's also a good idea to follow cx3110x-devel: https://garage.maemo.org/mailman/listinfo/cx3110x-devel -- Kalle Valo -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Android on N810 File System Problem
ext Tony Lindgren [EMAIL PROTECTED] writes: * Felipe Balbi [EMAIL PROTECTED] [080427 15:31]: On Sun, Apr 27, 2008 at 12:43:19PM +0300, Kalle Valo wrote: ext Felipe Balbi [EMAIL PROTECTED] writes: Current linux-omap's head has all the necessary pieces to get n810 working. Touchscreen, keypad, ambient light sensor, led, usb, everything is there. What about sound? I'm sure it'll come from alsa-devel soon. I've merged Jarkko's asoc patch to linux-omap for testing. Have not gotten any sound out of it on my n810 though.. Maybe some alsamixer settings issue? Kalle, do you have any tips on getting WLAN to work on n8x0? Unfortunately no. It's not a big task, but proprietary umac.ko is the biggest problem. It needs to be recompiled. Don't know if there's anything new there to you, but I posted some info on getting things to work with current linux-omap kernel at: http://www.muru.com/linux/n8x0/ That's really handy, thanks. -- Kalle Valo -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Android on N810 File System Problem
ext Felipe Balbi [EMAIL PROTECTED] writes: Current linux-omap's head has all the necessary pieces to get n810 working. Touchscreen, keypad, ambient light sensor, led, usb, everything is there. What about sound? -- Kalle Valo -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
