Hi Tang,
On Fri, Nov 23, 2012 at 6:44 PM, Tang Chen wrote:
> [What we are doing]
> This patchset provide a boot option for user to specify ZONE_MOVABLE memory
> map for each node in the system.
>
> movablecore_map=nn[KMG]@ss[KMG]
>
> This option make sure memory range from ss to ss+nn is movable
Add device tree based discovery support for max8997.
Cc: Karol Lewandowski
Cc: Rajendra Nayak
Cc: Rob Herring
Cc: Grant Likely
Signed-off-by: Thomas Abraham
Acked-by: MyungJoo Ham
Reviewed-by: Tomasz Figa
---
This patch is based on 'topic/max8997' branch of Mark Brown's
regulator tree.
..
On 11/27/2012 02:45 PM, Preeti U Murthy wrote:
> Hi,
> On 11/27/2012 11:44 AM, Alex Shi wrote:
>> On 11/27/2012 11:08 AM, Preeti U Murthy wrote:
>>> Hi everyone,
>>>
>>> On 11/27/2012 12:33 AM, Benjamin Segall wrote:
So, I've been trying out using the runnable averages for load balance in
Le Tue, 27 Nov 2012 08:42:09 +0100,
Sascha Hauer a écrit :
> On Sat, Nov 24, 2012 at 12:25:30AM -0800, Dmitry Torokhov wrote:
> > The default implementation matches exactly our custom one so we can switch
> > to using the default one. As a bonus the driver will take care of setting
> > GPIO line
On 27.11.2012 09:33, Dave Airlie wrote:
>> Third would be having a firewall in 2D driver checking the stream and
>> ensuring all registers that accept addresses are written by values
>> derived from dmabufs. I haven't tried implementing this, but it'd
>> involve a lookup table in kernel and CPU rea
On 11/27/2012 04:00 PM, Bob Liu wrote:
Hi Tang,
On Fri, Nov 23, 2012 at 6:44 PM, Tang Chen wrote:
[What we are doing]
This patchset provide a boot option for user to specify ZONE_MOVABLE memory
map for each node in the system.
movablecore_map=nn[KMG]@ss[KMG]
This option make sure memory rang
On Tue, Nov 27, 2012 at 8:16 AM, Terje Bergström wrote:
> On 27.11.2012 09:33, Dave Airlie wrote:
>>> Third would be having a firewall in 2D driver checking the stream and
>>> ensuring all registers that accept addresses are written by values
>>> derived from dmabufs. I haven't tried implementing
On Tuesday 27 November 2012, Stephen Rothwell wrote:
> @@@ -167,7 -184,9 +170,9 @@@ ehci_orion_conf_mbus_windows(struct usb
> }
> }
>
> + static u64 ehci_orion_dma_mask = DMA_BIT_MASK(32);
> +
> -static int __devinit ehci_orion_drv_probe(struct platform_device *pdev)
> +static int e
Hello,
I am implementing virtual CPU hotplug for the the ARM Cortex A-15 VExpress
motherboard.
This is mainly a QEMU feature, which allows dynamically changing the number
of CPUs in the guest.
I stumbled upon a limitation in the kernel support for plat-versatile,
which contains the secondary CP
On Tuesday 27 November 2012, Stephen Rothwell wrote:
>
> -config AB8500_BATTERY_THERM_ON_BATCTRL
> -bool "Thermistor connected on BATCTRL ADC"
> -depends on AB8500_BM
> -help
> - Say Y to enable battery temperature measurements using
> - thermistor connected on BATCT
On Tue, 27 Nov 2012, Viresh Kumar wrote:
> On 27 November 2012 08:10, Viresh Kumar wrote:
> > On 27 November 2012 00:10, Grant Likely wrote:
> >> It would actually be good to ask the interrupt controller driver what
> >> kind of interrupt signal it expects for a given interrupt line. That
> >> s
On 27.11.2012 10:32, Dave Airlie wrote:
> On Tue, Nov 27, 2012 at 8:16 AM, Terje Bergström
> wrote:
>> Thanks for the pointer, I looked at exynos code. It indeed checks the
>> registers written to, but it doesn't prevent overrun by checking sizes
>> of buffers and compare against requests.
> They
Using __CPUINIT instead of __INIT puts the secondary CPU startup code
into the "right" section: it will not be freed in hotplug configurations,
allowing hot-add of cpus, while still getting freed in non-hotplug configs.
Signed-off-by: Claudio Fontana
Tested-by: Claudio Fontana
diff --git a/arc
Hi Kent,
What's version of the kernel do you compiled?
I don't understand why you have some problem with formating, i have send you
the patch with no error and warning of code formating.
The tpm_continue_selftest_nocheck() (in kernel 3.x.x) and
tpm_continue_selftest() (in kernel 2.6.x) is calle
Hi Axel,
On Tue, Nov 27, 2012 at 03:15:17PM +0800, Axel Lin wrote:
> This fixes below build error:
>
> drivers/built-in.o: In function `tps65090_i2c_probe':
> drivers/mfd/tps65090.c:180: undefined reference to `regmap_add_irq_chip'
> drivers/mfd/tps65090.c:190: undefined reference to `regmap_irq_
Jens,
Limited access now at Incheon Airport. Will try the patch out when I arrived.
Thanks,
Jeff
On 11/27/12, Jens Axboe wrote:
> On 2012-11-27 08:38, Jens Axboe wrote:
>> On 2012-11-27 06:57, Jeff Chua wrote:
>>> On Sun, Nov 25, 2012 at 7:23 AM, Jeff Chua
>>> wrote:
On Sun, Nov 25, 2012
On 27 November 2012 14:10, Lee Jones wrote:
> On Tue, 27 Nov 2012, Viresh Kumar wrote:
>> Problem is with invert polarity, which the interrupt controller is not aware
>> of.
>> For example, suppose interrupt controller needs Rising edge interrupt, but
>> the board has inverted the line between st
On Tue 27-11-12 10:17:13, Jianguo Wu wrote:
> I enable CONFIG_DEBUG_VIRTUAL and CONFIG_SPARSEMEM_VMEMMAP, when doing memory
> hotremove,
> there is a kernel BUG at arch/x86/mm/physaddr.c:20.
>
> It is caused by free_section_usemap()->virt_to_page(),
> virt_to_page() is only used for kernel direct
Hi,
On 11/27/2012 12:36 AM, Michael Wolf wrote:
> In the case of where you have a system that is running in a
> capped or overcommitted environment the user may see steal time
> being reported in accounting tools such as top or vmstat. This can
> cause confusion for the end user. To ease the con
Hi
I have been trying to get the 3.7-rc6 kernel to compile for a beaglebone board
with device tree but it seems there are still bits missing. Especially it
seems as if the sd card reader and network is not working properly?
I would also like to combine the barebone with a recent 3.6 preempt rt
In AM33xx PWM sub modules like ECAP, EHRPWM & EQEP are integrated to
PWM subsystem. All these submodules shares the resources (clock) & has
a clock gating register in PWM Subsystem. This patch series creates a
parent PWM Subsystem driver to handle access synchronization of shared
resources & clock
In some platforms (like am33xx), PWM sub modules (ECAP, EHRPWM, EQEP)
are integrated to PWM subsystem. These PWM submodules has resources
shared and only one register bit-field is provided to control
module/clock enable/disable, makes it difficult to handle common
resources from independent PWMSS s
EQEP entry is HWMOD entry is not present in HWMOD entry. Also address
ranges specified for EACP & EHRPWM is not correct & HWMOD flags of
ADDR_TYPE_RT is added to PWM subsystem register address space. This
patch
1. Corrects register address mapping for ECAP & EHRPWM
2. Removes HWMOD flags in PWM su
As part of PWM subsystem integration, PWM subsystem are sharing
resources like clock across submodules (ECAP, EQEP & EHRPWM). To handle
resource sharing & IP integration rework on parent child relation
between PWMSS and ECAP, EQEP & EHRPWM child devices to support runtime PM.
Signed-off-by: Phili
Enable pinctrl for pwm-tiecap if pinctrl driver available, else
bail out with warning message.
Signed-off-by: Philip, Avinash
---
Changes since v4:
- Changes warning message.
drivers/pwm/pwm-tiecap.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/drivers/p
EHRPWM module requires explicit clock gating of TBCLK from control
module. Hence add TBCLK clock node in clock tree for EHRPWM modules.
Signed-off-by: Philip, Avinash
---
Changes since v4:
- Add dev_id field in clcok tree for TBCLK to remove support
for optional HWMOD clock supp
Some platforms (like AM33XX) requires clock gating from control module
explicitly for TBCLK. Enabling of this clock required for the
functioning of the time base sub module in EHRPWM module. Adding support
for handling by enabling the clock on PWM device enable & disable on PWM
device disable. Plat
This patch
1. Add support for device-tree binding for EHRWPM driver.
2. Set size of pwm-cells set to 3 to support PWM channel number, PWM
period & polarity configuration from device tree.
3. Add enable/disable clock gating in PWM subsystem common config space.
4. When here set .owner member in p
On 11/27/2012 12:29 AM, Tang Chen wrote:
> Another approach is like the following:
> movable_node = 1,3-5,8
> This could set all the memory on the nodes to be movable. And the rest
> of memory works as usual. But movablecore_map is more flexible.
... but *much* harder for users, so movable_node is
Enable pinctrl for pwm-tiehrpwm if pinctrl driver available, else
bail out with warning message.
Signed-off-by: Philip, Avinash
---
Changes since v4:
- Changes warning message.
drivers/pwm/pwm-tiehrpwm.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/drive
Add PWMSS device tree nodes in relation with ECAP & EHRPWM DT nodes to
AM33XX SoC family. Also populates device tree nodes for ECAP & EHRPWM by
adding necessary properties like pwm-cells, base reg & set disabled as
status.
Signed-off-by: Philip, Avinash
Reviewed-by: Thierry Reding
---
Changes si
This patch
1. Add support for device-tree binding for ECAP APWM driver.
2. Set size of pwm-cells set to 3 to support PWM channel number, PWM
period & polarity configuration from device tree.
3. Add enable/disable clock gating in PWM subsystem common config space.
4. When here set .owner member i
PWM output from ecap0 uses as backlight source. Also adds low threshold
value to have a uniform divisions in brightness-levels scales.
Signed-off-by: Philip, Avinash
Reviewed-by: Thierry Reding
---
Changes since v4:
- Replaced usage of tab with space in compatible field
Changes since v3
PWM output from ecap2 uses as backlight source. Also adds low threshold
value to have a uniform divisions in brightness-levels scales with
inverse polarity.
Signed-off-by: Philip, Avinash
Reviewed-by: Thierry Reding
---
Changes since v4:
- Replaced usage of tab with space in compatible f
As we are heading towards kernel charger manager soulutions and few
are already in mainaline and few are in pipeline. It makes sense have
uniform low level driver support independent of charger manager frameworks.
This patchset add the neccessary changes to power supply class
to make charger drive
This patch adds power supply charge control structure to power_supply struct
and add a Kconfig flag to use these controls by charger frameworks.
This patch also adds a helper function/API to return the charge control
struct to the charger frameworks.
Signed-off-by: Ramakrishna Pallala
---
drive
This patch enables the charger manager support for power supply drivers.
Note: this patch does change the variable/function names in charger
manager as it is just an enabling patch. I will submit incremental patches
to clean some of naming conventions to appeal more reasonable/logical to the
sourc
On Monday, November 26, 2012 5:30 PM Sebastian Andrzej Siewior wrote:
> On 11/26/2012 09:35 AM, Andrzej Pietrasiewicz wrote:
> > In some parts of the kernel (e.g. planned configfs integration into
> > usb
> > gadget) there is a need to programmatically create config groups
> > (directories) but it
On Monday 26 November 2012, gre...@linuxfoundation.org wrote:
> On Mon, Nov 26, 2012 at 08:38:32PM +, Arnd Bergmann wrote:
> > This is probably known and fixed already, but in case it's not, let me just
> > mention that I saw two new warnings with ARM allyesconfig about a
> > __devexit being re
As we are heading towards kernel charger manager soulutions and few
are already in mainaline and few are in pipeline. It makes sense have
uniform low level driver support independent of charger manager frameworks.
This patchset add the neccessary changes to power supply class
to make charger drive
This patch enables the charger manager support for power supply drivers.
Note: this patch does NOT change the variable/function names in charger
manager as it is just an enabling patch. I will submit incremental patches
to clean some of naming conventions to appeal more reasonable/logical to the
s
This patch adds power supply charge control structure to power_supply struct
and add a Kconfig flag to use these controls by charger frameworks.
This patch also adds a helper function/API to return the charge control
struct to the charger frameworks.
Signed-off-by: Ramakrishna Pallala
---
drive
The default implementation matches exactly our custom one so we can switch
to using the default one. As a bonus the driver will take care of setting
GPIO line for us.
Signed-off-by: Dmitry Torokhov
---
Adjusted to use IMX_GPIO_NR() macro.
arch/arm/mach-imx/eukrea_mbimx27-baseboard.c | 19 +--
On Mon, 26 Nov 2012, Dmitry Torokhov wrote:
> On Mon, Nov 26, 2012 at 12:16:18PM +, Lee Jones wrote:
> > On Wed, 14 Nov 2012, Lee Jones wrote:
> >
> > > Currently the BU21013 Touch Screen driver requests a regulator by the
> > > name of 'V-TOUCH', which doesn't exist anywhere in the kernel. T
On Mon, 26 Nov 2012, Dmitry Torokhov wrote:
> Hi Lee,
>
> On Mon, Nov 26, 2012 at 12:01:43PM +, Lee Jones wrote:
> > /**
> > + * bu21013_gpio_board_init() - configures the touch panel
> > + * @reset_pin: reset pin number
> > + *
> > + * This function is used to configure the voltage and
> >
On Thu, Nov 22, 2012 at 20:06:41, Philip, Avinash wrote:
> On Thu, Nov 22, 2012 at 16:13:52, Artem Bityutskiy wrote:
> > On Wed, 2012-11-21 at 07:01 +, Philip, Avinash wrote:
> > > > I am not sure how this dependency has to be handled for this series,
> > > > let me know whether you still want
On Thu, Nov 22, 2012 at 11:51:38PM -0800, Anton Vorontsov wrote:
> On Fri, Nov 23, 2012 at 11:36:01AM +0400, Alexander Shiyan wrote:
> [...]
> > got_no_fiq_insn also not initialized.
>
> It is static, so by definition it is initialized to 0.
>
> > I think as a whole on this issue requires additio
On 11/26/2012 11:40 PM, Sebastian Andrzej Siewior wrote:
On 11/26/2012 12:05 PM, Suzuki K. Poulose wrote:
diff --git a/arch/powerpc/include/asm/probes.h
b/arch/powerpc/include/asm/probes.h
index 5f1e15b..836e9b9 100644
--- a/arch/powerpc/include/asm/probes.h
+++ b/arch/powerpc/include/asm/probes
There is no point in having the sensor driver and F01 handler separate
from the RMI core since it is not useful without them and having them
all together simplifies initialization among other things.
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/Kconfig | 23 ++-
This saves on boilerplate code that is needed in individual modules
implementing function handlers.
Also converted bool bitfields back to u8.
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_bus.c| 189 ++
drivers/input/rmi4/rmi_driver.c | 2 +-
driver
This also allows us to cut down on the boilerplate code in the function
handler modules.
Signed-off-by: Dmitry Torokhov
---
drivers/input/rmi4/rmi_f11.c | 13 +
include/linux/rmi.h | 14 ++
2 files changed, 15 insertions(+), 12 deletions(-)
diff --git a/drivers/
Hi,
On Tue, Nov 27, 2012 at 1:21 PM, Marek Szyprowski
wrote:
> Hello,
>
>
> On 11/27/2012 8:39 AM, Prabhakar Lad wrote:
>>
>> Hi Marek,
>>
>> On Tue, Nov 27, 2012 at 12:53 PM, Marek Szyprowski
>> wrote:
>> > Hello,
>> >
>> >
>> > On 11/27/2012 6:59 AM, Prabhakar Lad wrote:
>> >>
>> >> From: Lad,
On Mon, Nov 26, 2012 at 02:31:27PM -0800, Christopher Heiny wrote:
> On 11/26/2012 01:40 AM, Dmitry Torokhov wrote:
> >Hi Christopher,
> >
> >On Fri, Nov 16, 2012 at 07:58:53PM -0800, Christopher Heiny wrote:
> >>RMI Function 01 implements basic device control and power management
> >>behaviors for
On Mon, Nov 26, 2012 at 11:54 PM, Christopher Heiny
wrote:
> On 11/26/2012 10:41 AM, Benjamin Tissoires wrote:
>>
>> Hi Christopher,
>>
>> On Sat, Nov 17, 2012 at 4:58 AM, Christopher Heiny
>> wrote:
>>>
>>> rmi_bus.c implements the basic functionality of the RMI bus. This file
>>> is
>>> greatl
The u9540 stopped booting after the v3.7 merge window due to
a lack of common clk support and early PRCMU initialisation.
In this patch we rectify these issues, placing the u9540
development board back into a successfully booting state.
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/cpu.c |
At 11/27/2012 04:49 PM, H. Peter Anvin Wrote:
> On 11/27/2012 12:29 AM, Tang Chen wrote:
>> Another approach is like the following:
>> movable_node = 1,3-5,8
>> This could set all the memory on the nodes to be movable. And the rest
>> of memory works as usual. But movablecore_map is more flexible.
Building ewrk3.o triggers this GCC warning:
drivers/net/ethernet/dec/ewrk3.c: In function '__check_irq':
drivers/net/ethernet/dec/ewrk3.c:1915:1: warning: return from incompatible
pointer type [enabled by default]
This can be trivially fixed by changing the 'irq' parameter from int to
byt
Remove an outdated comment, that should have been removed in the
patch named "MODULE_PARM conversions" from early 2005.
Signed-off-by: Paul Bolle
---
drivers/net/ethernet/dec/ewrk3.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/net/ethernet/dec/ewrk3.c b/drive
On Wed, Nov 21, 2012 at 02:04:26PM +, Alan Cox wrote:
> > I don't see any problems in my testcase.
>
> This looks fine to me as by the time we call tty_ldisc_release we have
> already set TTY_CLOSING on both sides.
Greg, can you push this into v3.7? This regression has been introduced in
v3.7
On 11/27/2012 01:47 AM, Wen Congyang wrote:
At 11/27/2012 04:49 PM, H. Peter Anvin Wrote:
On 11/27/2012 12:29 AM, Tang Chen wrote:
Another approach is like the following:
movable_node = 1,3-5,8
This could set all the memory on the nodes to be movable. And the rest
of memory works as usual. But
On Tue 27-11-12 09:05:30, KAMEZAWA Hiroyuki wrote:
[...]
> As a short term fix, I think this patch will work enough and seems simple
> enough.
> Acked-by: KAMEZAWA Hiroyuki
Thanks!
If Johannes is also ok with this for now I will resubmit the patch to
Andrew after I hear back from the reporter.
For removing memory, we need to remove page table. But it depends
on architecture. So the patch introduce arch_remove_memory() for
removing page table. Now it only calls __remove_pages().
Note: __remove_pages() for some archtecuture is not implemented
(I don't know how to implement it for s3
From: Yasuaki Ishimatsu
All pages of virtual mapping in removed memory cannot be freed, since some pages
used as PGD/PUD includes not only removed memory but also other memory. So the
patch checks whether page can be freed or not.
How to check whether page can be freed or not?
1. When removing
We call hotadd_new_pgdat() to allocate memory to store node_data. So we
should free it when removing a node.
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Benjamin Herrenschmidt
CC: Paul Mackerras
CC: Christoph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
CC: Yasuaki
This patch introduces a new function try_offline_node() to
remove sysfs file of node when all memory sections of this
node are removed. If some memory sections of this node are
not removed, this function does nothing.
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Christoph Lameter
Cc: Min
For hot removing memory, we sholud remove page table about the memory.
So the patch searches a page table about the removed memory, and clear
page table.
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Christoph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
CC: Yasuaki Is
From: Yasuaki Ishimatsu
Currently __remove_section for SPARSEMEM_VMEMMAP does nothing. But even if
we use SPARSEMEM_VMEMMAP, we can unregister the memory_section.
So the patch add unregister_memory_section() into __remove_section().
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Christop
Hi HPA and Tang,
2012/11/27 17:49, H. Peter Anvin wrote:
On 11/27/2012 12:29 AM, Tang Chen wrote:
Another approach is like the following:
movable_node = 1,3-5,8
This could set all the memory on the nodes to be movable. And the rest
of memory works as usual. But movablecore_map is more flexible.
From: Yasuaki Ishimatsu
When a memory is added, we update zone's and pgdat's start_pfn and
spanned_pages in the function __add_zone(). So we should revert them
when the memory is removed.
The patch adds a new function __remove_zone() to do this.
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
offlining memory blocks and checking whether memory blocks are offlined
are very similar. This patch introduces a new function to remove
redundant codes.
CC: David Rientjes
CC: Jiang Liu
CC: Len Brown
CC: Christoph Lameter
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
CC: Yasuaki Is
From: Yasuaki Ishimatsu
When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type}
sysfs files are created. But there is no code to remove these files. The patch
implements the function to remove them.
Note: The code does not free firmware_map_entry which is allocated by boot
memory can't be offlined when CONFIG_MEMCG is selected.
For example: there is a memory device on node 1. The address range
is [1G, 1.5G). You will find 4 new directories memory8, memory9, memory10,
and memory11 under the directory /sys/devices/system/memory/.
If CONFIG_MEMCG is selected, we will a
The patch-set was divided from following thread's patch-set.
https://lkml.org/lkml/2012/9/5/201
The last version of this patchset:
https://lkml.org/lkml/2012/11/1/93
If you want to know the reason, please read following thread.
https://lkml.org/lkml/2012/10/2/83
The patch-set has only t
From: Yasuaki Ishimatsu
For removing memmap region of sparse-vmemmap which is allocated bootmem,
memmap region of sparse-vmemmap needs to be registered by get_page_bootmem().
So the patch searches pages of virtual mapping and registers the pages by
get_page_bootmem().
Note: register_page_bootmem
From: Yasuaki Ishimatsu
We remove the memory like this:
1. lock memory hotplug
2. offline a memory block
3. unlock memory hotplug
4. repeat 1-3 to offline all memory blocks
5. lock memory hotplug
6. remove memory(TODO)
7. unlock memory hotplug
All memory blocks must be offlined before removing m
On Tue, Nov 27, 2012 at 3:38 PM, Jens Axboe wrote:
> On 2012-11-27 06:57, Jeff Chua wrote:
>> On Sun, Nov 25, 2012 at 7:23 AM, Jeff Chua wrote:
>>> On Sun, Nov 25, 2012 at 5:09 AM, Mikulas Patocka
>>> wrote:
So it's better to slow down mount.
>>>
>>> I am quite proud of the linux boot time
On 11/23/2012 04:41 PM, Haojian Zhuang wrote:
On Tue, Nov 6, 2012 at 3:38 PM, Qing Xu wrote:
From: Qing Xu
we encounter rtc/power/touch driver registry failure, root cause
it is resources confilict in insert_resouce, solved by changing
mfd_add_devices 5th parameter to NULL
Since resources a
This driver only supported the Charging indicator LED.
New set of drivers going to provide support for both PWMs and LEDs for twl4030
and twl6030 series of PMICs.
Signed-off-by: Peter Ujfalusi
---
drivers/pwm/Kconfig | 9 ---
drivers/pwm/Makefile | 1 -
drivers/pwm/pwm-twl6030.c |
Hello,
Changes since v3:
- pwm-twl-led driver's comment fix patch squashed to the original patch
- Documentation for the DT bindings of the PWM drivers
Comments from Thierry Reding addressed:
- pwm-twl6030 has been removed in the last patch
- macro for twl_pwm_chip/twl_pwmled_chip lookup
- locking
The driver supports the following LED outputs as generic PWM driver:
TWL4030 LEDA and LEDB (PWMA and PWMB)
TWL6030 Charging indicator LED (PWM LED)
On TWL6030 when the PWM requested LED is configured to be controlled by SW.
In this case the user can enable/disable and set the duty period freely.
W
The driver supports the following PWM outputs:
TWL4030 PWM0 and PWM1
TWL6030 PWM1 and PWM2
On TWL4030 the PWM signals are muxed. Upon requesting the PWM the driver
will select the correct mux so the PWM can be used. When the PWM has been
freed the original configuration is going to be restored.
S
This function allows to obtain a per-cpu variable, either of the current
or an explicitly specified CPU.
Note: sparc64 version is untested.
CC: "David S. Miller"
CC: sparcli...@vger.kernel.org
Signed-off-by: Jan Kiszka
---
scripts/gdb/percpu.py | 61 +
Provide an internal helper with container_of semantics. As type lookups
are very slow in gdb-python and we need a type "long" for this, cache
the reference to this type object. Then export the helper also as a
convenience function form use at the gdb command line.
Signed-off-by: Jan Kiszka
---
s
This provides the basic infrastructure to load kernel-specific python
helper scripts when debugging the kernel in gdb.
The loading mechanism is based on gdb loading for -gdb.py when
opening . Therefore, this places a corresponding link to the
main helper script into the output directory that conta
Here is version 3 of my gdb helper scripts. Changes in this release are
related to improving compatibility with older gdb versions (down to 7.1)
and the with latest one (7.5). Also, proper reloading of updated kernel
and module symbols was implemented.
Andrew, I got the suggestion to pass these pa
This is a shorthand for *$lx_per_cpu("current_task"), i.e. a convenience
function to retrieve the currently running task of the active context.
Signed-off-by: Jan Kiszka
---
scripts/gdb/percpu.py | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/scripts/gdb/
This helper probes the type of the gdb server. Supported are QEMU and
KGDB so far. Knowledge about the gdb server is required e.g. to retrieve
the current CPU or current task.
Signed-off-by: Jan Kiszka
---
scripts/gdb/utils.py | 35 +++
1 files changed, 35 inser
Add the internal helper get_thread_info that calculated the thread_info
from a given task variable. Also export this service as a convenience
function.
Note: ia64 version is untested.
CC: Tony Luck
CC: Fenghua Yu
CC: linux-i...@vger.kernel.org
Signed-off-by: Jan Kiszka
---
scripts/gdb/task.py
Parse the target endianness from the output of "show endian" and cache
the result to return it via the new helper get_target_endiannes. We will
need it for reading integers from buffers that contain target memory.
Signed-off-by: Jan Kiszka
---
scripts/gdb/utils.py | 17 +
1 fil
The internal helper for_each_task iterates over all tasks of the target,
calling the provided function on each. For performance reasons, we cache
a reference to the gdb type object of a task.
Signed-off-by: Jan Kiszka
---
scripts/gdb/task.py | 40
1 fil
Add the helper task_by_pid that can look up a task by its PID. Also
export it as a convenience function.
Signed-off-by: Jan Kiszka
---
scripts/gdb/task.py| 29 +
scripts/gdb/vmlinux-gdb.py |1 +
2 files changed, 30 insertions(+), 0 deletions(-)
diff --g
This is probably the most useful helper when debugging kernel modules:
lx-symbols will first reload vmlinux. Then it searches recursively for
*.ko files in the specified paths and the current directory. Finally it
walks the kernel's module list, issuing the necessary add-symbol-file
command for eac
This pokes into the log buffer of the debugged kernel, dumping it to the
gdb console. Helping in case the target should or can no longer execute
dmesg itself.
CC: Kay Sievers
Signed-off-by: Jan Kiszka
---
scripts/gdb/dmesg.py | 63
scripts/gd
Add helpers for reading integers from target memory buffers. Required
when caching the memory access is more efficient than reading individual
values via gdb.
Signed-off-by: Jan Kiszka
---
scripts/gdb/utils.py | 18 ++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --g
This helper caches to result of "show architecture" and matches the
provided arch (sub-)string against that output.
Signed-off-by: Jan Kiszka
---
scripts/gdb/utils.py |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/scripts/gdb/utils.py b/scripts/gdb/utils.py
inde
Am Dienstag, den 27.11.2012, 10:45 +0200 schrieb Terje Bergström:
> On 27.11.2012 10:32, Dave Airlie wrote:
> > On Tue, Nov 27, 2012 at 8:16 AM, Terje Bergström
> > wrote:
> >> Thanks for the pointer, I looked at exynos code. It indeed checks the
> >> registers written to, but it doesn't prevent
Hi all:
This series is an update version of multiqueue virtio-net driver based on
Krishna Kumar's work to let virtio-net use multiple rx/tx queues to do the
packets reception and transmission. Please review and comments.
A protype implementation of qemu-kvm support could by found in
git://github.
To support multiqueue transmitq/receiveq, the first step is to separate queue
related structure from virtnet_info. This patch introduce send_queue and
receive_queue structure and use the pointer to them as the parameter in
functions handling sending/receiving.
Signed-off-by: Krishna Kumar
Signed-
This addes multiqueue support to virtio_net driver. In multiple queue modes, the
driver expects the number of queue paris is equal to the number of vcpus. To
eliminate the contention bettwen vcpus and virtqueues, per-cpu virtqueue pairs
were implemented through:
- select the txq based on the smp p
This patch implement the {set|get}_channels method of ethool to allow user to
change the number of queues dymaically when the device is running. This would
let the user to configure it on demand.
Signed-off-by: Jason Wang
---
drivers/net/virtio_net.c | 41 ++
1 - 100 of 630 matches
Mail list logo
