linaro-dev August 2011

linaro-dev@lists.linaro.org

126 participants
239 discussions

[Patch v1 08/11] Touch: DA9052 touchscreen driver

by ashishj3

This driver add support for DA9052 4-wire resistive ADC interfaced touchscreen controller. DA9052 is a MFD therefore this driver depends on DA9052 core driver for core functionalities. Signed-off-by: David Dajun Chen <dchen(a)diasemi.com> Signed-off-by: Ashish Jangam <ashish.jangam(a)kpitcummins.com> --- drivers/input/touchscreen/Kconfig | 7 + drivers/input/touchscreen/Makefile | 1 + drivers/input/touchscreen/da9052_tsi.c | 489 ++++++++++++++++++++++++++++++++ 3 files changed, 497 insertions(+), 0 deletions(-) create mode 100755 drivers/input/touchscreen/da9052_tsi.c diff --git a/drivers/input/touchscreen/Kconfig b/drivers/input/touchscreen/Kconfig index cabd9e5..a5d2e7b 100644 --- a/drivers/input/touchscreen/Kconfig +++ b/drivers/input/touchscreen/Kconfig @@ -144,6 +144,13 @@ config TOUCHSCREEN_DA9034 Say Y here to enable the support for the touchscreen found on Dialog Semiconductor DA9034 PMIC. +config TOUCHSCREEN_DA9052 + tristate "Dialog DA9052 TSI" + depends on PMIC_DA9052 + help + Say y here to support the touchscreen found on + Dialog Semiconductor DA9052 PMIC + config TOUCHSCREEN_DYNAPRO tristate "Dynapro serial touchscreen" select SERIO diff --git a/drivers/input/touchscreen/Makefile b/drivers/input/touchscreen/Makefile index 282d6f7..a4aeb25 100644 --- a/drivers/input/touchscreen/Makefile +++ b/drivers/input/touchscreen/Makefile @@ -18,6 +18,7 @@ obj-$(CONFIG_TOUCHSCREEN_BITSY) += h3600_ts_input.o obj-$(CONFIG_TOUCHSCREEN_BU21013) += bu21013_ts.o obj-$(CONFIG_TOUCHSCREEN_CY8CTMG110) += cy8ctmg110_ts.o obj-$(CONFIG_TOUCHSCREEN_DA9034) += da9034-ts.o +obj-$(CONFIG_TOUCHSCREEN_DA9052) += da9052_tsi.o obj-$(CONFIG_TOUCHSCREEN_DYNAPRO) += dynapro.o obj-$(CONFIG_TOUCHSCREEN_HAMPSHIRE) += hampshire.o obj-$(CONFIG_TOUCHSCREEN_GUNZE) += gunze.o diff --git a/drivers/input/touchscreen/da9052_tsi.c b/drivers/input/touchscreen/da9052_tsi.c new file mode 100755 index 0000000..dade0a9 --- /dev/null +++ b/drivers/input/touchscreen/da9052_tsi.c @@ -0,0 +1,489 @@ +/* + * TSI driver for Dialog DA9052 + * + * Copyright(c) 2011 Dialog Semiconductor Ltd. + * + * Author: David Dajun Chen <dchen(a)diasemi.com> + * + * This program is free software; you can redistribute it and/or modify it + * under the terms of the GNU General Public License as published by the + * Free Software Foundation; either version 2 of the License, or (at your + * option) any later version. + * + */ +#include <linux/module.h> +#include <linux/input.h> +#include <linux/delay.h> +#include <linux/platform_device.h> +#include <linux/freezer.h> +#include <linux/kthread.h> +#include <linux/kfifo.h> + +#include <linux/mfd/da9052/reg.h> +#include <linux/mfd/da9052/da9052.h> + +#define DA9052_ACTIVE 1 +#define DA9052_INACTIVE 0 + +#define DA9052_TSI_FIFOSIZE 640 + +enum { + DA9052_PEN_IDLE, + DA9052_PEN_DOWN, + DA9052_PEN_UP +}; + +struct da9052_tsi_reg { + u16 x; + u16 y; +}; + +struct tsi_thread_type { + u8 pid; + u8 state; + struct completion notifier; + struct task_struct *thread_task; +}; + +struct da9052_tsi { + struct da9052 *da9052; + struct input_dev *dev; + struct tsi_thread_type tsi_pen_state_thread; + struct tsi_thread_type tsi_filter_thread; + struct kfifo fifo; + struct kfifo fifo_buf; + u8 pen_up_detect_interval; + u32 zero_data_cnt; + u32 valid_penup_count; + u8 pen_state; + int irq_pendwn; + int irq_datardy; +}; + +static inline int da9052_ts_start(struct da9052_tsi *tsi) +{ + return da9052_reg_update(tsi->da9052, DA9052_TSI_CONT_A_REG, + 1 << 0, 1 << 0); +} + +static inline int da9052_ts_stop(struct da9052_tsi *tsi) +{ + return da9052_clear_bits(tsi->da9052, DA9052_TSI_CONT_A_REG, 1 << 0); +} + +static irqreturn_t da9052_ts_pendwn_irq(int irq, void *data) +{ + struct da9052_tsi *tsi = (struct da9052_tsi *)data; + struct da9052 *da9052 = tsi->da9052; + int ret; + + da9052->events_mask |= DA9052_E_PEN_DOWN; + da9052->events_mask &= ~DA9052_E_TSI_READY; + + /* Mask PEN_DOWN event and unmask TSI_READY event*/ + ret = da9052_reg_update(da9052, DA9052_IRQ_MASK_B_REG, 0x80, 0x40); + if (ret < 0) + return IRQ_NONE; + + da9052_ts_start(tsi); + tsi->pen_state = DA9052_PEN_DOWN; + + return IRQ_HANDLED; +} + +static int da9052_ts_read(struct da9052_tsi *tsi) +{ + struct da9052_tsi_reg co_ord = {0, 0}; + int ret; + uint8_t _x, _y, _v; + + ret = da9052_reg_read(tsi->da9052, DA9052_TSI_X_MSB_REG); + if (ret < 0) + return ret; + + _x = (uint8_t) ret; + + ret = da9052_reg_read(tsi->da9052, DA9052_TSI_Y_MSB_REG); + if (ret < 0) + return ret; + + _y = (uint8_t) ret; + + ret = da9052_reg_read(tsi->da9052, DA9052_TSI_LSB_REG); + if (ret < 0) + return ret; + + _v = (uint8_t) ret; + + co_ord.x = ((_x << 2) & 0x3fc) | (_v & 0x3); + co_ord.y = ((_y << 2) & 0x3fc) | ((_v & 0xc) >> 2); + + ret = kfifo_in(&tsi->fifo, &co_ord, sizeof(struct da9052_tsi_reg)); + + return 0; +} + +static irqreturn_t da9052_ts_datardy_irq(int irq, void *data) +{ + struct da9052_tsi *tsi = (struct da9052_tsi *)data; + int ret; + + ret = da9052_ts_read(tsi); + if (ret) { + dev_err(tsi->da9052->dev, + "Failed to read TSI co-ordinate, %d\n", ret); + return IRQ_NONE; + } + + return IRQ_HANDLED; +} + +/* +* Two FIFO are been used. FIFO1 is used for detecting pen up and +* FIFO2 for reporting pen down co-ordinate. +*/ +void da9052_ts_process_reg_data(struct da9052_tsi *tsi) +{ + struct da9052_tsi_reg tmp_raw_data; + u32 reg_data_cnt; + int ret; + + reg_data_cnt = kfifo_len(&tsi->fifo); + + while (reg_data_cnt-- > 0) { + ret = kfifo_out(&tsi->fifo, &tmp_raw_data, + sizeof(struct da9052_tsi_reg)); + if (ret < 0) + continue; + kfifo_in(&tsi->fifo_buf, &tmp_raw_data, + sizeof(struct da9052_tsi_reg)); + } + return; +} + +static void da9052_ts_report_penup(struct da9052_tsi *tsi) +{ + struct input_dev *ip_dev = tsi->dev; + struct da9052 *da9052 = tsi->da9052; + ssize_t ret; + + ret = da9052_ts_stop(tsi); + if (ret < 0) + return; + + da9052->events_mask |= DA9052_E_TSI_READY; + da9052->events_mask &= ~DA9052_E_PEN_DOWN; + + /* Mask TSI_READY event and unmask PEN_DOWN event*/ + ret = da9052_reg_update(da9052, DA9052_IRQ_MASK_B_REG, 0x40, 0x80); + if (ret < 0) + return; + + input_report_abs(ip_dev, BTN_TOUCH, 0); + input_sync(ip_dev); + + tsi->zero_data_cnt = 0; +} + +/* +* This function detects the pen up state using the kfifo len. +* If kfifo len is zero for some interval then pen up is reported. +* Else pen co-ordinate are reported. +*/ +static int da9052_ts_monitor_pen_state(void *data) +{ + struct da9052_tsi *tsi = (struct da9052_tsi *) data; + u32 data_cnt; + + set_freezable(); + + while (tsi->tsi_pen_state_thread.state == DA9052_ACTIVE) { + try_to_freeze(); + + set_current_state(TASK_INTERRUPTIBLE); + schedule_timeout(msecs_to_jiffies(10)); + + if (tsi->pen_state != DA9052_PEN_DOWN) + continue; + + data_cnt = kfifo_len(&tsi->fifo); + if (data_cnt < 0) + continue; + + da9052_ts_process_reg_data(tsi); + + if (data_cnt) + tsi->zero_data_cnt = 0; + else { + if ((++(tsi->zero_data_cnt)) > + tsi->valid_penup_count) { + tsi->pen_state = DA9052_PEN_UP; + da9052_ts_report_penup(tsi); + } + } + } + + complete_and_exit(&tsi->tsi_pen_state_thread.notifier, 0); + return 0; +} + +static int da9052_ts_process_thread(void *ptr) +{ + struct da9052_tsi_reg co_ord; + int cnt = 0, ret; + struct da9052_tsi *tsi = (struct da9052_tsi *)ptr; + + set_freezable(); + + while (tsi->tsi_filter_thread.state == DA9052_ACTIVE) { + + try_to_freeze(); + + set_current_state(TASK_INTERRUPTIBLE); + schedule_timeout(msecs_to_jiffies(10)); + cnt = kfifo_len(&tsi->fifo_buf); + if (cnt <= 0) + continue; + + ret = kfifo_out(&tsi->fifo_buf, &co_ord, + sizeof(struct da9052_tsi_reg)); + if (ret < 0) + continue; + + input_report_abs(tsi->dev, BTN_TOUCH, 1); + input_report_abs(tsi->dev, ABS_X, co_ord.x); + input_report_abs(tsi->dev, ABS_Y, co_ord.y); + input_sync(tsi->dev); + } + + tsi->tsi_filter_thread.thread_task = NULL; + complete_and_exit(&tsi->tsi_filter_thread.notifier, 0); + + return 0; +} + +static int da9052_ts_configure_gpio(struct da9052 *da9052) +{ + int ret; + + ret = da9052_clear_bits(da9052, DA9052_GPIO_2_3_REG, 0x30); + if (ret < 0) + return -EIO; + + ret = da9052_clear_bits(da9052, DA9052_GPIO_4_5_REG, 0x33); + if (ret < 0) + return -EIO; + + ret = da9052_clear_bits(da9052, DA9052_GPIO_6_7_REG, 0x33); + if (ret < 0) + return -EIO; + + return ret; +} + +static int __init da9052_ts_enable_device(struct da9052_tsi *tsi) +{ + ssize_t ret; + struct da9052 *da9052 = tsi->da9052; + + ret = da9052_ts_configure_gpio(tsi->da9052); + if (ret < 0) + return ret; + + ret = da9052_reg_update(tsi->da9052, DA9052_TSI_CONT_A_REG, 0xFC, 0xC0); + if (ret < 0) + return ret; + + tsi->valid_penup_count = 5; + + init_completion(&tsi->tsi_pen_state_thread.notifier); + tsi->tsi_pen_state_thread.state = DA9052_ACTIVE; + tsi->tsi_pen_state_thread.pid = kernel_thread(da9052_ts_monitor_pen_state, tsi, + CLONE_KERNEL | SIGCHLD); + + init_completion(&tsi->tsi_filter_thread.notifier); + tsi->tsi_filter_thread.state = DA9052_ACTIVE; + tsi->tsi_filter_thread.pid = kernel_thread(da9052_ts_process_thread, tsi, + CLONE_KERNEL | SIGCHLD); + + tsi->zero_data_cnt = 0; + + /* Measure TSI sample every 1ms */ + ret = da9052_reg_update(tsi->da9052, DA9052_ADC_CONT_REG, + 1 << 6, 1 << 6); + if (ret < 0) + return ret; + + /* TSI_DELAY: 4 slots, TSI_SKIP: 0 slots, TSI_MODE: XYZP */ + ret = da9052_reg_update(tsi->da9052, DA9052_TSI_CONT_A_REG, + 1 << 1, 1 << 1); + if (ret < 0) + return ret; + + da9052->events_mask |= DA9052_E_TSI_READY; + + /* Mask TSI_READY event*/ + ret = da9052_reg_update(da9052, DA9052_IRQ_MASK_B_REG, 0, 0x80); + if (ret < 0) + return ret; + + /*Supply TSIRef thru LD09 */ + ret = da9052_reg_write(tsi->da9052, DA9052_LDO9_REG, 0x59); + + return ret; +} + +static s32 __devinit da9052_ts_probe(struct platform_device *pdev) +{ + struct da9052_tsi *tsi; + struct input_dev *input_dev; + struct da9052 *da9052; + int ret; + + da9052 = dev_get_drvdata(pdev->dev.parent); + + tsi = kzalloc(sizeof(struct da9052_tsi), GFP_KERNEL); + if (!tsi) + return -ENOMEM; + + input_dev = input_allocate_device(); + if (!input_dev) { + dev_err(tsi->da9052->dev, + "failed to allocate input device\n"); + ret = -ENOMEM; + goto err_mem; + } + + ret = kfifo_alloc(&tsi->fifo, DA9052_TSI_FIFOSIZE, GFP_KERNEL); + if (ret < 0) + goto err_input; + + ret = kfifo_alloc(&tsi->fifo_buf, DA9052_TSI_FIFOSIZE, GFP_KERNEL); + if (ret < 0) + goto err_fifo; + + tsi->da9052 = da9052; + tsi->pen_up_detect_interval = 5; + platform_set_drvdata(pdev, tsi); + + input_dev->id.version = 0x0101; + input_dev->id.vendor = 0x15B6; + input_dev->id.product = 0x9052; + input_dev->id.bustype = BUS_RS232; + input_dev->name = "Dialog DA9052 TouchScreen Driver"; + input_dev->dev.parent = &pdev->dev; + __set_bit(EV_ABS, input_dev->evbit); + __set_bit(EV_KEY, input_dev->evbit); + __set_bit(BTN_TOUCH, input_dev->keybit); + __set_bit(ABS_X, input_dev->absbit); + __set_bit(ABS_Y, input_dev->absbit); + + input_set_abs_params(input_dev, ABS_X, 0, 1023, 0, 0); + input_set_abs_params(input_dev, ABS_Y, 0, 1023, 0, 0); + input_set_abs_params(input_dev, ABS_PRESSURE, 0, 1023, 0, 0); + + tsi->dev = input_dev; + input_set_drvdata(input_dev, tsi); + ret = input_register_device(tsi->dev); + if (ret) + goto err_mem; + + tsi->irq_pendwn = platform_get_irq_byname(pdev, "PENDWN"); + ret = request_threaded_irq(tsi->da9052->irq_base + tsi->irq_pendwn, + NULL, da9052_ts_pendwn_irq, + IRQF_TRIGGER_LOW | IRQF_ONESHOT, + "PENDWN", tsi); + if (ret < 0) { + dev_err(tsi->da9052->dev, + "Failed to register %s IRQ %d, error = %d\n", "PENDWN", + tsi->da9052->irq_base + tsi->irq_pendwn, ret); + goto err_fifo_buf; + } + + tsi->irq_datardy = platform_get_irq_byname(pdev, "TSIRDY"); + ret = request_threaded_irq(tsi->da9052->irq_base + tsi->irq_datardy, + NULL, da9052_ts_datardy_irq, + IRQF_TRIGGER_LOW | IRQF_ONESHOT, + "TSIRDY", tsi); + if (ret < 0) { + dev_err(tsi->da9052->dev, + "Failed to register %s IRQ %d, error = %d\n", "TSIRDY", + tsi->da9052->irq_base + tsi->irq_datardy, ret); + goto err_fifo_buf; + } + + ret = da9052_ts_enable_device(tsi); + if (ret < 0) + goto err_fifo_buf; + + return 0; + +err_fifo_buf: + kfifo_free(&tsi->fifo_buf); +err_fifo: + kfifo_free(&tsi->fifo); +err_input: + input_free_device(input_dev); +err_mem: + kfree(tsi); + return ret; +} + +static int __devexit da9052_ts_remove(struct platform_device *pdev) +{ + struct da9052_tsi *tsi = platform_get_drvdata(pdev); + s32 ret; + + ret = da9052_clear_bits(tsi->da9052, DA9052_TSI_CONT_A_REG, 1 << 0); + if (ret < 0) + return ret; + + ret = da9052_reg_write(tsi->da9052, DA9052_LDO9_REG, 0x19); + if (ret < 0) + return ret; + + free_irq(tsi->da9052->irq_base + tsi->irq_pendwn, NULL); + free_irq(tsi->da9052->irq_base + tsi->irq_datardy, NULL); + + tsi->tsi_pen_state_thread.state = DA9052_INACTIVE; + wait_for_completion(&tsi->tsi_pen_state_thread.notifier); + + tsi->tsi_filter_thread.state = DA9052_INACTIVE; + wait_for_completion(&tsi->tsi_filter_thread.notifier); + + input_unregister_device(tsi->dev); + + platform_set_drvdata(pdev, NULL); + + kfifo_free(&tsi->fifo); + kfifo_free(&tsi->fifo_buf); + kfree(tsi); + + return 0; +} + +static struct platform_driver da9052_tsi_driver = { + .probe = da9052_ts_probe, + .remove = __devexit_p(da9052_ts_remove), + .driver = { + .name = "da9052-tsi", + .owner = THIS_MODULE, + }, +}; + +static int __init da9052_ts_init(void) +{ + return platform_driver_register(&da9052_tsi_driver); +} +module_init(da9052_ts_init); + +static void __exit da9052_ts_exit(void) +{ + platform_driver_unregister(&da9052_tsi_driver); +} +module_exit(da9052_ts_exit); + +MODULE_DESCRIPTION("Touchscreen driver for Dialog Semiconductor DA9052"); +MODULE_AUTHOR("David Dajun Chen <dchen(a)diasemi.com>"); +MODULE_LICENSE("GPL"); +MODULE_ALIAS("platform:da9052-tsi");

12 years, 9 months

[PATCH] ARM: do not mark CPU 0 as hotpluggable

by Mike Turquette

A quick poll of the ARM platforms that implement CPU Hotplug support shows that every platform treats CPU 0 as a special case that cannot be hotplugged. In fact every platform has identical code for platform_cpu_die which returns -EPERM in the case of CPU 0. The user-facing sysfs interfaces should reflect this by not populating an 'online' entry for CPU 0 at all. This better reflects reality by making it clear to users that CPU 0 cannot be hotplugged. This patch prevents CPU 0 from being marked as hotpluggable on all ARM platforms during CPU registration. This in turn prevents the creation of an 'online' sysfs interface for that CPU. Signed-off-by: Mike Turquette <mturquette(a)ti.com> --- arch/arm/kernel/setup.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/arch/arm/kernel/setup.c b/arch/arm/kernel/setup.c index ed11fb0..a5fc969 100644 --- a/arch/arm/kernel/setup.c +++ b/arch/arm/kernel/setup.c @@ -940,7 +940,8 @@ static int __init topology_init(void) for_each_possible_cpu(cpu) { struct cpuinfo_arm *cpuinfo = &per_cpu(cpu_data, cpu); - cpuinfo->cpu.hotpluggable = 1; + if (cpu) + cpuinfo->cpu.hotpluggable = 1; register_cpu(&cpuinfo->cpu, cpu); } -- 1.7.4.1

12 years, 9 months

[PATCH v2 0/2] new cpumask for hotpluggable CPUs

by Mike Turquette

This patch series introduces a new cpumask which tracks CPUs that support hotplugging. The purpose of this patch series is to provide a simple method for kernel code to know which CPUs can be hotplugged and which ones cannot. Potential users of this code might be a thermal mitigation technique which uses hotplug to lower temperature, or a power capping mechanism which uses hotplug to lower power consumption. All the of usual cpumask helper functions are created for this new mask. The second patch in this series simply sets the bit for elligible CPUs while they are being registered. The cpumask itself is static after boot and should not change (like the possbile mask). Mike Turquette (2): cpumask: introduce cpumask for hotpluggable CPUs cpu: update cpu_hotpluggable_mask in register_cpu drivers/base/cpu.c | 4 +++- include/linux/cpumask.h | 27 ++++++++++++++++++++++----- kernel/cpu.c | 18 ++++++++++++++++++ 3 files changed, 43 insertions(+), 6 deletions(-) -- 1.7.4.1

12 years, 9 months

Linaro 11.08 weekly testing 2011-08-11

by Fathi Boudra

Hi, This is a message sent out once per week to call on our community to encourage all Linux/ARM enthusiasts to try out the latest preview images of our Linaro Evaluation Builds (LEBs) for Android Handset and Ubuntu Desktop/Netbook. These images showcase the current state of development on our LEBs images on their way to the next release: 11.08. * Android for PandaBoard: http://snapshots.linaro.org/11.05-daily/linaro-android/leb-panda/20110811/ * Android for Snowball: http://snapshots.linaro.org/11.05-daily/linaro-android/leb-snowball/2011081… * Ubuntu: http://snapshots.linaro.org/11.05-daily/linaro-ubuntu-desktop/20110811/0/im… http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/panda-x11-base/20110… On top of the official Linaro Evaluation Builds, the Platform Team hosts a set of functional images and board support packages that are typically released by Linaro engineers for developers that have different images requirements. These images are not officially supported release artifacts and are provided on a best-effort basis in the hope that they can be useful for the Linux/ARM enthusiasts community. The download locations for these so called "Developers and Community Builds" can be found below. Developer and Experimental Images based on Android (vanilla AOSP experience using linux-linaro mainline kernel): * Android Mainline for BeagleBoardr-xM: http://snapshots.linaro.org/11.05-daily/linaro-android/beaglexm/20110811/ * Android Mainline for PandaBoard: http://snapshots.linaro.org/11.05-daily/linaro-android/panda/20110811/ Developer Images based on Ubuntu: Note: Ubuntu images are distributed in two parts: 1. a SoC independent userspace rootfs (the image) 2. a Soc specific BSP (the hwpack) * Nano (think small): http://snapshots.linaro.org/11.05-daily/linaro-nano/20110811/0/images/tar/ * ALIP (Xfce desktop): http://snapshots.linaro.org/11.05-daily/linaro-alip/20110811/0/images/tar/ * Developer (text user interface + developer tools): http://snapshots.linaro.org/11.05-daily/linaro-developer/20110811/0/images/… Not officially supported community board support packages are also provided for either boards that don't meet our Linaro Evaluation Builds criterias. The idea is that you can combine them freely (e.g. combine an imx51 hwpack with Nano or Developer); though in practice UI images might not work. A list of all hardware packs hosted by Linaro Platform can be found below: http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/ Make your way to the installation instructions: https://wiki.linaro.org/Platform/Android/ImageInstallation https://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation For an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker -- Fathi Boudra Linaro Release Manager | Platform Project Manager Linaro.org | Open source software for ARM SoCs

12 years, 9 months

[PATCH] add a test description for each test

by Daniel Lezcano

Signed-off-by: Daniel Lezcano <daniel.lezcano(a)linaro.org> --- cpufreq/Makefile | 2 ++ cpufreq/cpufreq_01.txt | 1 + cpufreq/cpufreq_02.txt | 1 + cpufreq/cpufreq_03.txt | 1 + cpufreq/cpufreq_04.txt | 1 + cpufreq/cpufreq_05.txt | 1 + cpufreq/cpufreq_06.txt | 1 + cpufreq/cpufreq_07.txt | 1 + cpufreq/cpufreq_08.txt | 1 + cpufreq/cpufreq_09.txt | 1 + sched_mc/Makefile | 2 ++ sched_mc/sched_01.txt | 1 + sched_mc/sched_02.txt | 1 + sched_mc/sched_03.txt | 1 + sched_mc/sched_04.txt | 1 + 15 files changed, 17 insertions(+), 0 deletions(-) create mode 100644 cpufreq/cpufreq_01.txt create mode 100644 cpufreq/cpufreq_02.txt create mode 100644 cpufreq/cpufreq_03.txt create mode 100644 cpufreq/cpufreq_04.txt create mode 100644 cpufreq/cpufreq_05.txt create mode 100644 cpufreq/cpufreq_06.txt create mode 100644 cpufreq/cpufreq_07.txt create mode 100644 cpufreq/cpufreq_08.txt create mode 100644 cpufreq/cpufreq_09.txt create mode 100644 sched_mc/sched_01.txt create mode 100644 sched_mc/sched_02.txt create mode 100644 sched_mc/sched_03.txt create mode 100644 sched_mc/sched_04.txt diff --git a/cpufreq/Makefile b/cpufreq/Makefile index f52a1f4..9c9133e 100644 --- a/cpufreq/Makefile +++ b/cpufreq/Makefile @@ -28,6 +28,8 @@ LOG=$(TST:.sh=.log) check: uncheck $(LOG) %.log: %.sh + @echo -e "###\n### $(<:.sh=):" + @echo -n "### "; cat $(<:.sh=.txt); echo "###" @./$< 2> $@ clean: diff --git a/cpufreq/cpufreq_01.txt b/cpufreq/cpufreq_01.txt new file mode 100644 index 0000000..c40a620 --- /dev/null +++ b/cpufreq/cpufreq_01.txt @@ -0,0 +1 @@ +test the cpufreq framework is available for frequency diff --git a/cpufreq/cpufreq_02.txt b/cpufreq/cpufreq_02.txt new file mode 100644 index 0000000..4123148 --- /dev/null +++ b/cpufreq/cpufreq_02.txt @@ -0,0 +1 @@ +test the cpufreq framework is available for governor diff --git a/cpufreq/cpufreq_03.txt b/cpufreq/cpufreq_03.txt new file mode 100644 index 0000000..a979614 --- /dev/null +++ b/cpufreq/cpufreq_03.txt @@ -0,0 +1 @@ +test the governor change is effective diff --git a/cpufreq/cpufreq_04.txt b/cpufreq/cpufreq_04.txt new file mode 100644 index 0000000..0d70931 --- /dev/null +++ b/cpufreq/cpufreq_04.txt @@ -0,0 +1 @@ +test the change of the frequency is effective in 'userspace' mode diff --git a/cpufreq/cpufreq_05.txt b/cpufreq/cpufreq_05.txt new file mode 100644 index 0000000..37e6061 --- /dev/null +++ b/cpufreq/cpufreq_05.txt @@ -0,0 +1 @@ +test 'ondemand' and 'conservative' trigger correctly the configuration directory diff --git a/cpufreq/cpufreq_06.txt b/cpufreq/cpufreq_06.txt new file mode 100644 index 0000000..c3e41cb --- /dev/null +++ b/cpufreq/cpufreq_06.txt @@ -0,0 +1 @@ +test the change of the frequencies affect the performances of a test program diff --git a/cpufreq/cpufreq_07.txt b/cpufreq/cpufreq_07.txt new file mode 100644 index 0000000..805173b --- /dev/null +++ b/cpufreq/cpufreq_07.txt @@ -0,0 +1 @@ +test the load of the cpu affects the frequency with 'ondemand' diff --git a/cpufreq/cpufreq_08.txt b/cpufreq/cpufreq_08.txt new file mode 100644 index 0000000..2a218e2 --- /dev/null +++ b/cpufreq/cpufreq_08.txt @@ -0,0 +1 @@ +test the load of the cpu does not affect the frequency with 'userspace' diff --git a/cpufreq/cpufreq_09.txt b/cpufreq/cpufreq_09.txt new file mode 100644 index 0000000..547749b --- /dev/null +++ b/cpufreq/cpufreq_09.txt @@ -0,0 +1 @@ +test the load of the cpu does not affect the frequency with 'powersave' diff --git a/sched_mc/Makefile b/sched_mc/Makefile index f52a1f4..9c9133e 100644 --- a/sched_mc/Makefile +++ b/sched_mc/Makefile @@ -28,6 +28,8 @@ LOG=$(TST:.sh=.log) check: uncheck $(LOG) %.log: %.sh + @echo -e "###\n### $(<:.sh=):" + @echo -n "### "; cat $(<:.sh=.txt); echo "###" @./$< 2> $@ clean: diff --git a/sched_mc/sched_01.txt b/sched_mc/sched_01.txt new file mode 100644 index 0000000..6783a3a --- /dev/null +++ b/sched_mc/sched_01.txt @@ -0,0 +1 @@ +test the presence of the 'sched_mc_power_savings' file diff --git a/sched_mc/sched_02.txt b/sched_mc/sched_02.txt new file mode 100644 index 0000000..5493610 --- /dev/null +++ b/sched_mc/sched_02.txt @@ -0,0 +1 @@ +test the topology is implemented in the kernel diff --git a/sched_mc/sched_03.txt b/sched_mc/sched_03.txt new file mode 100644 index 0000000..b9e8d6f --- /dev/null +++ b/sched_mc/sched_03.txt @@ -0,0 +1 @@ +test the topology files are present diff --git a/sched_mc/sched_04.txt b/sched_mc/sched_04.txt new file mode 100644 index 0000000..7f5ed4a --- /dev/null +++ b/sched_mc/sched_04.txt @@ -0,0 +1 @@ +test the change are effective for the 'sched_mc_power_savings' file -- 1.7.4.1

12 years, 9 months

[ACTIVITY] Android Platform Team 2011-07-31 to 2011-08-06

by Tony Mansson

Key Points for wider discussion ======================= JPEG pictures now can be viewed on Android platform with libjpeg-turbo successfully. Toolchain now supports CLooG-ISL and OpenMP. Team Highlights ======================= Move to Android 2.3.5 is proceeding good. libvpx 0.9.6, x264, ffmpeg is building for Android. Linaro Android for Samsung Origen board is building (but not booting yet). ADB and androidscreencast is working on Snowball. Miscellaneous ======================= Mathieu Poirier is with us! Zach on vacation from 21st-24th, Tony on 11:th. Code complete planned for the 18:th.

12 years, 9 months

Hacking Android from a Toolchain perspective

by Michael Hope

Hi there. One of our goals in toolchain is to give good support to the Android group. I've written a page from the toolchain perspective on what is Android, how do you build it, and how you do common toolchainy tasks like reproduce a compiler fault: https://wiki.linaro.org/MichaelHope/Sandbox/AndroidAndToolchain Comments are welcome. It needs sections on how the compiler is configured, running a program using adb, and basic debugging. -- Michael

12 years, 9 months

Why are our Android toolchains 32bit?

by Bernhard Rosenkranzer

Hi, while working on some improvements, I noticed that our Android toolchain binaries are built as 32-bit x86. Is there any reason for this (other than "we inherited it from AOSP")? While it doesn't matter much, it doesn't make much sense to me - Android can't currently be built on 32-bit machines (so it's not about having one binary that will work for mostly everyone - but I suspect that's exactly where it started back in the times of Android 1.0), so why introduce dependencies on a 32-bit libc and slow things down slightly? If nobody complains, I'll remove the "-m32" flag from the Android toolchain builds - let's see how much we can speed up the build process itself without putting any real work into it... ttyl bero

12 years, 9 months

pm-qa test output

by Daniel Lezcano

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Amit, Here is the example output with the test description. The email wraps the lines, actually each test are one line output. Let me know if it is ok for you. Thanks -- Daniel [ ... ] ### ### cpufreq_04: ### test the change of the frequency is effective in 'userspace' mode ### cpufreq_04.0/cpu0 checking setting frequency '2.6 GHz'... PASS cpufreq_04.1/cpu0 checking setting frequency '2.6 GHz'... PASS cpufreq_04.2/cpu0 checking setting frequency '2.0 GHz'... PASS cpufreq_04.3/cpu0 checking setting frequency '1.6 GHz'... PASS cpufreq_04.4/cpu0 checking setting frequency '1.2 GHz'... PASS cpufreq_04.5/cpu0 checking setting frequency '800.0 MHz'... PASS cpufreq_04.0/cpu1 checking setting frequency '2.6 GHz'... PASS cpufreq_04.1/cpu1 checking setting frequency '2.6 GHz'... PASS cpufreq_04.2/cpu1 checking setting frequency '2.0 GHz'... PASS cpufreq_04.3/cpu1 checking setting frequency '1.6 GHz'... PASS cpufreq_04.4/cpu1 checking setting frequency '1.2 GHz'... PASS cpufreq_04.5/cpu1 checking setting frequency '800.0 MHz'... PASS ### ### cpufreq_05: ### test 'ondemand' and 'conservative' trigger correctly the configuration directory ### cpufreq_05.0/cpu1 checking 'ondemand' directory exists... PASS cpufreq_05.0/cpu1 checking 'conservative' directory exists... PASS cpufreq_05.0/cpu1 checking 'ondemand' directory is not there... PASS cpufreq_05.1/cpu1 checking 'conservative' directory is not there... PASS cpufreq_05.2/cpu1 checking 'ondemand' directory exists... PASS cpufreq_05.3/cpu1 checking 'conservative' directory exists... PASS ### ### cpufreq_06: ### test the change of the frequencies affect the performances of a test program ### cpufreq_06.0/cpu0 checking deviation for frequency 2.6 GHz... PASS cpufreq_06.1/cpu0 checking deviation for frequency 2.6 GHz... FAIL cpufreq_06.2/cpu0 checking deviation for frequency 2.0 GHz... FAIL cpufreq_06.3/cpu0 checking deviation for frequency 1.6 GHz... PASS cpufreq_06.4/cpu0 checking deviation for frequency 1.2 GHz... FAIL cpufreq_06.5/cpu0 checking deviation for frequency 800.0 MHz... FAIL cpufreq_06.0/cpu1 checking deviation for frequency 2.6 GHz... PASS cpufreq_06.1/cpu1 checking deviation for frequency 2.6 GHz... FAIL cpufreq_06.2/cpu1 checking deviation for frequency 2.0 GHz... FAIL cpufreq_06.3/cpu1 checking deviation for frequency 1.6 GHz... PASS cpufreq_06.4/cpu1 checking deviation for frequency 1.2 GHz... FAIL cpufreq_06.5/cpu1 checking deviation for frequency 800.0 MHz... FAIL ### ### cpufreq_07: ### test the load of the cpu affects the frequency with 'ondemand' ### cpufreq_07.0/cpu0 checking 'ondemand' increase frequency on load... PASS cpufreq_07.1/cpu0 checking 'ondemand' decrease frequency on idle... FAIL cpufreq_07.0/cpu1 checking 'ondemand' increase frequency on load... PASS cpufreq_07.1/cpu1 checking 'ondemand' decrease frequency on idle... PASS ### ### cpufreq_08: ### test the load of the cpu does not affect the frequency with 'userspace' ### <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOQu00AAoJEAKBbMCpUGYAK70IAJMaNajxLrAR4tLlv4aFyFHl DB9M0pX4OgLmxVJ18zGR5oOr/IzjXXMZTrJrfQJre0DLzCi/yur0wJntJFEUbUy/ M/xHJFBEEY8GX7wxws5LGaR9b/ASGfax4LZVo85CAldaHCl6QzTXolsj/IRvB/r+ uVoCToUMWQT2oaOwW7q9U1ItBPgFb0yTrqTcz1jgC3IMFPNh867sRH/z+UFfHzF6 yBaZ34E5bNO/VGQuGOmWp5vEl//KlvGmGAKPWb/KxHD0gEwVoF+2gf+fWvdOf9sD CC23Hc5FnqrP5SaRLwHRuO7NcxIX2ooUADn6ojN3SJm0nN/qx3qMyTMqakfkxgk= =4oGS -----END PGP SIGNATURE-----

12 years, 9 months

[PATCH v4 0/2] ORIGEN Board Support

by Chander Kashyap

Adds support for ORIGEN board with MMC Booting. Chander Kashyap (2): ARMV7: Add support for Samsung ORIGEN board ORIGEN: Add MMC SPL support MAINTAINERS | 1 + board/samsung/origen/Makefile | 46 ++ board/samsung/origen/lowlevel_init.S | 464 +++++++++++++++++++++ board/samsung/origen/mem_setup.S | 359 ++++++++++++++++ board/samsung/origen/origen.c | 105 +++++ boards.cfg | 1 + include/configs/origen.h | 166 ++++++++ mmc_spl/board/samsung/origen/Makefile | 106 +++++ mmc_spl/board/samsung/origen/mmc_boot.c | 57 +++ mmc_spl/board/samsung/origen/tools/mkv310_image.c | 140 +++++++ mmc_spl/board/samsung/origen/u-boot.lds | 88 ++++ 11 files changed, 1533 insertions(+), 0 deletions(-) create mode 100644 board/samsung/origen/Makefile create mode 100644 board/samsung/origen/lowlevel_init.S create mode 100644 board/samsung/origen/mem_setup.S create mode 100644 board/samsung/origen/origen.c create mode 100644 include/configs/origen.h create mode 100644 mmc_spl/board/samsung/origen/Makefile create mode 100644 mmc_spl/board/samsung/origen/mmc_boot.c create mode 100644 mmc_spl/board/samsung/origen/tools/mkv310_image.c create mode 100644 mmc_spl/board/samsung/origen/u-boot.lds -- 1.7.4.1

12 years, 9 months

← Newer
1
...
17
18
19
20
21
22
23
24
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev August 2011