linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

[Maverick][PATCH] UBUNTU : SAUCE - ARM: Support for vbus, overcurrent and LEDs on IGEPv2

by Mathieu Poirier

>From 210c9482650eb6cb24488303e50e3c49babb3d3a Mon Sep 17 00:00:00 2001 From: Enric Balletbo i Serra <eballetbo(a)gmail.com> Date: Fri, 1 Oct 2010 15:23:31 -0600 Subject: [PATCH] Support for vbus, overcurrent and LEDs on IGEPv2 This patch adds support for the VBUS and over current GPIOs along with the four LEDs present on the IGEPv2 board. Initialisation of the LEDs is done with the LED class if CONFIG_LEDS_GPIO is selected or the General Purpose Input/Output (GPIO) interface if CONFIG_LEDS_GPIO is not selected. https://bugs.launchpad.net/bugs/651589 Signed-off-by: <eballetbo(a)gmail.com> Signed-off-by: <mathieu.poirier(a)canonical.com> --- arch/arm/mach-omap2/board-igep0020.c | 170 ++++++++++++++++++++-------------- 1 files changed, 101 insertions(+), 69 deletions(-) diff --git a/arch/arm/mach-omap2/board-igep0020.c b/arch/arm/mach-omap2/board-igep0020.c index d55c57b..21bb77f 100644 --- a/arch/arm/mach-omap2/board-igep0020.c +++ b/arch/arm/mach-omap2/board-igep0020.c @@ -261,6 +261,77 @@ static struct omap2_hsmmc_info mmc[] = { {} /* Terminator */ }; +#if defined(CONFIG_LEDS_GPIO) || defined(CONFIG_LEDS_GPIO_MODULE) +#include <linux/leds.h> + +static struct gpio_led igep2_gpio_leds[] = { + [0] = { + .name = "gpio-led:red:d0", + .gpio = IGEP2_GPIO_LED0_RED, + .default_trigger = "default-off" + }, + [1] = { + .name = "gpio-led:green:d0", + .gpio = IGEP2_GPIO_LED0_GREEN, + .default_trigger = "default-off", + }, + [2] = { + .name = "gpio-led:red:d1", + .gpio = IGEP2_GPIO_LED1_RED, + .default_trigger = "default-off", + }, + [3] = { + .name = "gpio-led:green:d1", + .default_trigger = "heartbeat", + .gpio = -EINVAL, /* gets replaced */ + }, +}; + +static struct gpio_led_platform_data igep2_led_pdata = { + .leds = igep2_gpio_leds, + .num_leds = ARRAY_SIZE(igep2_gpio_leds), +}; + +static struct platform_device igep2_led_device = { + .name = "leds-gpio", + .id = -1, + .dev = { + .platform_data = &igep2_led_pdata, + }, +}; + +static void __init igep2_leds_init(void) +{ + platform_device_register(&igep2_led_device); +} + +#else +static inline void igep2_leds_init(void) +{ + if ((gpio_request(IGEP2_GPIO_LED0_RED, "gpio-led:red:d0") == 0) && + (gpio_direction_output(IGEP2_GPIO_LED0_RED, 1) == 0)) { + gpio_export(IGEP2_GPIO_LED0_RED, 0); + gpio_set_value(IGEP2_GPIO_LED0_RED, 0); + } else + pr_warning("IGEP v2: Could not obtain gpio GPIO_LED0_RED\n"); + + if ((gpio_request(IGEP2_GPIO_LED0_GREEN, "gpio-led:green:d0") == 0) && + (gpio_direction_output(IGEP2_GPIO_LED0_GREEN, 1) == 0)) { + gpio_export(IGEP2_GPIO_LED0_GREEN, 0); + gpio_set_value(IGEP2_GPIO_LED0_GREEN, 0); + } else + pr_warning("IGEP v2: Could not obtain gpio GPIO_LED0_GREEN\n"); + + if ((gpio_request(IGEP2_GPIO_LED1_RED, "gpio-led:red:d1") == 0) && + (gpio_direction_output(IGEP2_GPIO_LED1_RED, 1) == 0)) { + gpio_export(IGEP2_GPIO_LED1_RED, 0); + gpio_set_value(IGEP2_GPIO_LED1_RED, 0); + } else + pr_warning("IGEP v2: Could not obtain gpio GPIO_LED1_RED\n"); + +} +#endif + static int igep2_twl_gpio_setup(struct device *dev, unsigned gpio, unsigned ngpio) { @@ -274,14 +345,40 @@ static int igep2_twl_gpio_setup(struct device *dev, igep2_vmmc1_supply.dev = mmc[0].dev; igep2_vmmc2_supply.dev = mmc[1].dev; + /* + * REVISIT: need ehci-omap hooks for external VBUS + * power switch and overcurrent detect + */ + gpio_request(gpio + 1, "GPIO_EHCI_NOC"); + gpio_direction_input(gpio + 1); + + /* + * TWL4030_GPIO_MAX + 0 == ledA, GPIO_USBH_CPEN + * (out, active low) + */ + gpio_request(gpio + TWL4030_GPIO_MAX, 0); + gpio_direction_output(gpio + TWL4030_GPIO_MAX, 0); + + /* TWL4030_GPIO_MAX + 1 == ledB (out, active low LED) */ +#if !defined(CONFIG_LEDS_GPIO) && !defined(CONFIG_LEDS_GPIO_MODULE) + if ((gpio_request(gpio+TWL4030_GPIO_MAX+1, "gpio-led:green:d1") == 0) + && (gpio_direction_output(gpio + TWL4030_GPIO_MAX + 1, 1) == 0)) { + gpio_export(gpio + TWL4030_GPIO_MAX + 1, 0); + gpio_set_value(gpio + TWL4030_GPIO_MAX + 1, 0); + } else + pr_warning("IGEP v2: Could not obtain gpio GPIO_LED1_GREEN\n"); +#else + igep2_gpio_leds[3].gpio = gpio + TWL4030_GPIO_MAX + 1; +#endif + return 0; }; -static struct twl4030_gpio_platform_data igep2_gpio_data = { +static struct twl4030_gpio_platform_data igep2_twl4030_gpio_pdata = { .gpio_base = OMAP_MAX_GPIO_LINES, .irq_base = TWL4030_GPIO_IRQ_BASE, .irq_end = TWL4030_GPIO_IRQ_END, - .use_leds = false, + .use_leds = true, .setup = igep2_twl_gpio_setup, }; @@ -355,47 +452,6 @@ static void __init igep2_display_init(void) pr_err("IGEP v2: Could not obtain gpio GPIO_DVI_PUP\n"); } -#if defined(CONFIG_LEDS_GPIO) || defined(CONFIG_LEDS_GPIO_MODULE) -#include <linux/leds.h> - -static struct gpio_led igep2_gpio_leds[] = { - { - .name = "led0:red", - .gpio = IGEP2_GPIO_LED0_RED, - }, - { - .name = "led0:green", - .default_trigger = "heartbeat", - .gpio = IGEP2_GPIO_LED0_GREEN, - }, - { - .name = "led1:red", - .gpio = IGEP2_GPIO_LED1_RED, - }, -}; - -static struct gpio_led_platform_data igep2_led_pdata = { - .leds = igep2_gpio_leds, - .num_leds = ARRAY_SIZE(igep2_gpio_leds), -}; - -static struct platform_device igep2_led_device = { - .name = "leds-gpio", - .id = -1, - .dev = { - .platform_data = &igep2_led_pdata, - }, -}; - -static void __init igep2_init_led(void) -{ - platform_device_register(&igep2_led_device); -} - -#else -static inline void igep2_init_led(void) {} -#endif - static struct platform_device *igep2_devices[] __initdata = { &igep2_dss_device, }; @@ -425,7 +481,7 @@ static struct twl4030_platform_data igep2_twldata = { /* platform_data for children goes here */ .usb = &igep2_usb_data, .codec = &igep2_codec_data, - .gpio = &igep2_gpio_data, + .gpio = &igep2_twl4030_gpio_pdata, .vmmc1 = &igep2_vmmc1, .vmmc2 = &igep2_vmmc2, .vpll2 = &igep2_vpll2, @@ -486,34 +542,10 @@ static void __init igep2_init(void) usb_ehci_init(&ehci_pdata); igep2_flash_init(); - igep2_init_led(); + igep2_leds_init(); igep2_display_init(); igep2_init_smsc911x(); - /* GPIO userspace leds */ -#if !defined(CONFIG_LEDS_GPIO) && !defined(CONFIG_LEDS_GPIO_MODULE) - if ((gpio_request(IGEP2_GPIO_LED0_RED, "led0:red") == 0) && - (gpio_direction_output(IGEP2_GPIO_LED0_RED, 1) == 0)) { - gpio_export(IGEP2_GPIO_LED0_RED, 0); - gpio_set_value(IGEP2_GPIO_LED0_RED, 0); - } else - pr_warning("IGEP v2: Could not obtain gpio GPIO_LED0_RED\n"); - - if ((gpio_request(IGEP2_GPIO_LED0_GREEN, "led0:green") == 0) && - (gpio_direction_output(IGEP2_GPIO_LED0_GREEN, 1) == 0)) { - gpio_export(IGEP2_GPIO_LED0_GREEN, 0); - gpio_set_value(IGEP2_GPIO_LED0_GREEN, 0); - } else - pr_warning("IGEP v2: Could not obtain gpio GPIO_LED0_GREEN\n"); - - if ((gpio_request(IGEP2_GPIO_LED1_RED, "led1:red") == 0) && - (gpio_direction_output(IGEP2_GPIO_LED1_RED, 1) == 0)) { - gpio_export(IGEP2_GPIO_LED1_RED, 0); - gpio_set_value(IGEP2_GPIO_LED1_RED, 0); - } else - pr_warning("IGEP v2: Could not obtain gpio GPIO_LED1_RED\n"); -#endif - /* GPIO W-LAN + Bluetooth combo module */ if ((gpio_request(IGEP2_GPIO_WIFI_NPD, "GPIO_WIFI_NPD") == 0) && (gpio_direction_output(IGEP2_GPIO_WIFI_NPD, 1) == 0)) { -- 1.7.0.4

15 years, 1 month

Proposal: linaro-testdrive script...

by Scott Bambrough

Official proposal for stakeholder process for the following idea. Anyone can contribute. Summary ---------- Amit Kucheria has suggested we create a script called linaro-testdrive to ease the knowledge required to download images and create bootable media. In his opinion as we continuously add support for more platforms and even more boards, it will become untenable to maintain the wiki pages describing. Something similar to 'testdrive' for Ubuntu is required for the next cycle. This script should ask some basic questions and just do the right thing. This should be a separate script from linaro-media-create. Questions would be: - What SoC? - What board? - What release (milestone)? - Image type (headless, alip, qemu, etc.) Each of these would be a multiple choice question. This should get rid of the several levels of indirection required just to download all the right components before trying to prepare an image. The should be easily data driven. A data file could contain all of the information required for the questions above. And with the right packaging, upgrades to linaro-testdrive will continually add support for new platforms and boards. StakeHolders --------------- Amit Kucheria <amit.kucheria(a)linaro.org> Scott Bambrough <scott.bambrough(a)linaro.org> Deadline: ASAP Time estimate: Likely two-three weeks in all. -- Scott Bambrough <scott.bambrough(a)linaro.org> Linaro Infrastructure Team Lead

15 years, 1 month

Introduction

by Kurt Taylor

Hello, I have been lurking here and on irc for a while and felt like it was time to introduce myself. I have a BB-C4 with all the trimmings and have been booting SD flash with the daily builds and trying different configurations. I have also signed up for weekly testing on the BB. >From the wiki, it looks like I would be most interested in either the Platform Engineering or Working Groups Engineering Units. Specifically, I'd really like to start playing with sound/multimedia, but really anywhere that I can help. Is there any interest in a Middleware:Audio working group? Or does this fit better with the Platform Engineering User Platforms group? I helped form the Linux Foundation (OSDL at the time) Desktop Architects Sound and Multimedia workgroup and could help with that. Regards, Kurt Taylor (krtaylor irc)

15 years, 1 month

daily snapshot - udev not working?

by Robert Berger

Hi, I'm playing around with the daily snapshots. Currently I'm using the snapshot from 20100929 on an EBVBeagle C2. In order to see home exactly I'm cooking it you can look here: http://ebvbeagle.blogspot.com/2010/09/linaro-on-beagle.html It comes up more or less happily, but as soon as I connect either my mcs7830 based USB to ethernet adapter, my USB mouse, or my USB keyboard to the USB hub I don't see anything happening. No logs from the kernel buffer and no udev events with udevadm monitor. With some old Angstrom image I have lying around I can see the events. With Linaro it looks like udev is running. Either me or the image is missing something. Is it time to recompile the kernel and/or write some udev rules, or does this image try to use some other mechanism for hot plugging I'm not aware of? Regards, Robert

15 years, 1 month

Notes from Landing Teams call 2010/09/29

by Matt Waddel

Notes from today's Landing Team call: https://wiki.linaro.org/LandingTeams/Meetings/2010-09-29 --Matt === Attendees === * Loïc Minier * Matt Waddel * Torez Smith * Scott Bambrough === Agenda === * Action items from last meeting. * Achievements / progress reports * OMAP3 * Versatile Express * AOB === Action Items === * Torez * Bad LCD on IGeP - Patch posted - will investigate and try soon * Matt * u-boot merge window open - check status === Action Items from Previous Meeting === * Torez to talk to james_w to create an IGEP hwpack === Minutes === * Action items from last meeting. * Torez to talk to james_w to create an IGEP hwpack - Done * Achievements / progress reports * OMAP3 * Torez to work with hardware packs and james_w * Versatile Express * initrd status update * investigate - http://article.gmane.org/gmane.comp.boot-loaders.u-boot/84378 * minimal config project discussion * vexpress.config, ca9-tile.config, other.config * test development * MMC/USB bug * u-boot merge window open - check status of vexpress patches * Scott Bambrough to manage Landing Team efforts, Loic to attend when possible Status reports: Matt - == Last Week == * abrek setup and validation - ltp/stream - works * validate ALSA - working - wrote audio validation procedure * contacted Nicolas about a vexpress defconfig - make savedefconfig * Flash-kernel fixes and submit - accepted in Ubuntu * Validated new images and closed some outstanding bugs * LTP bug review - fixed some, posted list to linaro-dev * Minimal config

15 years, 1 month

Notes & Actions: Linaro User Platform Weekly Status Meeting 9/29

by Tom Gall

Enclosed you'll find a link to the agenda, notes and actions from the Linaro User Platforms Weekly Status meeting dated 9/29 held in #linaro-meeting on irc.freenode.net at 13:00 UTC. https://wiki.linaro.org/Platform/UserPlatforms/WeeklyStatus/2010-09-29 Regards, Tom (tgall_foo) User Platforms Team "We want great men who, when fortune frowns will not be discouraged." - Colonel Henry Knox w) tom.gall att linaro.org w) tom_gall att vnet.ibm.com h) tom_gall att mac.com

15 years, 1 month

Override dh_gencontrol architecture

by Tim Gardner

I'm working on building in ARM cross compile support to the Ubuntu kernel packaging. I am encountering the following error: fakeroot debian/rules binary-omap arch=armel ..... dh_gencontrol -plinux-image-2.6.35-22-omap dpkg-gencontrol: error: current host architecture 'amd64' does not appear in package's architecture list (armel) dh_gencontrol: dpkg-gencontrol -plinux-image-2.6.35-22-omap -ldebian/changelog -Tdebian/linux-image-2.6.35-22-omap.substvars -Pdebian/linux-image-2.6.35-22-omap returned exit code 255 make: *** [binary-omap] Error 9 I have not successfully found a way to override the architecture. Anyone have any ideas? I've tried the various forms of dh_gencontrol -p$(pkgimg) -a$(arch) dh_gencontrol -p$(pkgimg) -- -a$(arch) export DH_OPTIONS="-a$(arch)" && dh_gencontrol -p$(pkgimg) rtg -- Tim Gardner tim.gardner(a)canonical.com

15 years, 1 month

[PM] 29/09/10 - Minutes for the Power Management WG weekly call

by Amit Kucheria

Hi everyone, The minutes of the weekly call can be found at: https://wiki.linaro.org/WorkingGroups/PowerManagement/Meetings/2010-09-29 Attendees: Linaro: Amit Kucheria, Amit Arora, Vincent, Yong ARM: Srinivas Kalaga Highlight: Discussion on PM QA validation Regards, Amit

15 years, 1 month

Notes & Actions: Linaro graphics/multimedia - Sep 27, 2010

by Alexandros Frantzis

Hi, notes and actions from our Monday graphics and multimedia cross-vendor call are available on the wiki: + https://wiki.linaro.org/Platform/UserPlatforms/2010-09-27 Details about when and where of this meeting can be found here: + https://wiki.linaro.org/WorkingGroups/Middleware/Graphics#Weekly%20Public%2… Thanks, -- - Alexandros

15 years, 1 month

Linaro Bug Tags

by Jamie Bennett

Hi, Tagging bugs is not only good practice but makes tracking and sorting so much easier. With this in mind I came up with a list of tags that can be consulted when reporting bugs. Please take a look at: http://wiki.linaro.org/Process/Bugs/Tags Ubuntu bug tags [1] also still apply, the Linaro specific ones are just to further classify bugs for Linaro. Please feel free to suggest changes/corrections. Regards, Jamie. [1] http://wiki.ubuntu.com/Bugs/Tags

15 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev