Re: [PATCH 0/2] FTDI CBUS GPIO support

2015-06-20 Thread Philipp Hachtmann
Am 21.06.2015 um 00:12 schrieb Stefan Agner: There are three GPIO modes supported by FTDI devices: 1. Asynchronous Bit Bang Mode (used in Sacha's patch) 2. Synchronous Bit Bang Mode (used in Philipp's patch) 3. CBUS Bit Bang Mode (used in Philipp's patch and this patchset) 1. No idea, could be

Re: [PATCH V5 2/3] mm/memblock: Add support for excluded memory areas

2014-01-22 Thread Philipp Hachtmann
Hi again, I'd like to remind that the s390 development relies on this patch (and the next one, for cleanliness, of course) being added. It would be very good to see it being added to the -mm tree resp. linux-next. Kind regards Philipp -- To unsubscribe from this list: send the line "unsubscribe

[PATCH 0/2] Small fixes to memblock and nobootmem

2014-01-07 Thread Philipp Hachtmann
supported as well. Philipp Hachtmann (2): mm, nobootmem: Add return value check in __alloc_memory_core_early() mm: free memblock.memory in free_all_bootmem include/linux/memblock.h | 1 + mm/memblock.c| 12 mm/nobootmem.c | 11 +-- 3 files changed, 22

[PATCH 2/2] mm: free memblock.memory in free_all_bootmem

2014-01-07 Thread Philipp Hachtmann
When calling free_all_bootmem() the free areas under memblock's control are released to the buddy allocator. Additionally the reserved list is freed if it was reallocated by memblock. The same should apply for the memory list. Signed-off-by: Philipp Hachtmann --- include/linux/memblock.h

[PATCH 1/2] mm, nobootmem: Add return value check in __alloc_memory_core_early()

2014-01-07 Thread Philipp Hachtmann
memblock_reserve() in __alloc_memory_core(). Signed-off-by: Philipp Hachtmann --- mm/nobootmem.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/mm/nobootmem.c b/mm/nobootmem.c index 2c254d3..3a7e14d 100644 --- a/mm/nobootmem.c +++ b/mm/nobootmem.c @@ -45,7 +45,9 @@ static void * __init

Re: [PATCH 2/2] mm: free memblock.memory in free_all_bootmem

2014-01-08 Thread Philipp Hachtmann
o prevent memblock.memory from being freed when CONFIG_ARCH_DISCARD_MEMBLOCK is not set. Here is a replacement for the patch. Kind regards Philipp >From aca95bcb9d79388b68bf18e7bae4353259b6758f Mon Sep 17 00:00:00 2001 From: Philipp Hachtmann Date: Thu, 19 Dec 2013 15:53:46 +0100 Subject: [PATCH 2

[PATCH 0/2] mm/memblock: Excluded memory, free_all_bootmem

2014-01-13 Thread Philipp Hachtmann
information about the real full memory structure at a later time. Philipp Hachtmann (2): mm/nobootmem: free_all_bootmem again mm/memblock: Add support for excluded memory areas include/linux/memblock.h | 50 ++-- mm/memblock.c| 324 +++ mm

[PATCH 1/2] mm/nobootmem: free_all_bootmem again

2014-01-13 Thread Philipp Hachtmann
functions are called. Signed-off-by: Philipp Hachtmann --- mm/memblock.c | 17 ++--- mm/nobootmem.c | 4 ++-- 2 files changed, 4 insertions(+), 17 deletions(-) diff --git a/mm/memblock.c b/mm/memblock.c index 64ed243..9c0aeef 100644 --- a/mm/memblock.c +++ b/mm/memblock.c @@ -266,33

[PATCH 2/2] mm/memblock: Add support for excluded memory areas

2014-01-13 Thread Philipp Hachtmann
Add a new memory state "nomap" to memblock. This can be used to truncate the usable memory in the system without forgetting about what is really installed. Signed-off-by: Philipp Hachtmann --- include/linux/memblock.h | 50 ++-- mm/memblock.c

[PATCH V2 1/2] mm/nobootmem: free_all_bootmem again

2014-01-13 Thread Philipp Hachtmann
functions are called. Signed-off-by: Philipp Hachtmann --- mm/memblock.c | 17 ++--- mm/nobootmem.c | 4 ++-- 2 files changed, 4 insertions(+), 17 deletions(-) diff --git a/mm/memblock.c b/mm/memblock.c index 64ed243..9c0aeef 100644 --- a/mm/memblock.c +++ b/mm/memblock.c @@ -266,33

[PATCH V2 2/2] mm/memblock: Add support for excluded memory areas

2014-01-13 Thread Philipp Hachtmann
Add a new memory state "nomap" to memblock. This can be used to truncate the usable memory in the system without forgetting about what is really installed. Signed-off-by: Philipp Hachtmann --- include/linux/memblock.h | 50 +++-- mm/Kconfig | 3 + mm/

[PATCH V2 0/2] mm/memblock: Excluded memory, free_all_bootmem

2014-01-13 Thread Philipp Hachtmann
information about the real full memory structure at a later time. Philipp Hachtmann (2): mm/nobootmem: free_all_bootmem again mm/memblock: Add support for excluded memory areas include/linux/memblock.h | 50 +++-- mm/Kconfig | 3 + mm/memblock.c| 276

[PATCH V3 1/2] mm/nobootmem: free_all_bootmem again

2014-01-13 Thread Philipp Hachtmann
functions are called. Signed-off-by: Philipp Hachtmann --- mm/memblock.c | 17 ++--- mm/nobootmem.c | 4 ++-- 2 files changed, 4 insertions(+), 17 deletions(-) diff --git a/mm/memblock.c b/mm/memblock.c index 64ed243..9c0aeef 100644 --- a/mm/memblock.c +++ b/mm/memblock.c @@ -266,33

[PATCH V3 0/2] mm/memblock: Excluded memory, free_all_bootmem

2014-01-13 Thread Philipp Hachtmann
information about the real full memory structure at a later time. (sorry for the two too bad versions before) Philipp Hachtmann (2): mm/nobootmem: free_all_bootmem again mm/memblock: Add support for excluded memory areas arch/s390/Kconfig| 1 + include/linux/memblock.h | 50 +++-- mm

[PATCH V3 2/2] mm/memblock: Add support for excluded memory areas

2014-01-13 Thread Philipp Hachtmann
Add a new memory state "nomap" to memblock. This can be used to truncate the usable memory in the system without forgetting about what is really installed. Signed-off-by: Philipp Hachtmann --- arch/s390/Kconfig| 1 + include/linux/memblock.h | 50 +++--

Re: [PATCH V3 2/2] mm/memblock: Add support for excluded memory areas

2014-01-14 Thread Philipp Hachtmann
Am Mon, 13 Jan 2014 16:36:20 -0800 schrieb Andrew Morton : > Patch is big. I'll toss this in for some testing but it does look too > large and late for 3.14. How will this affect your s390 development? It is needed for s390 bootmem -> memblock transition. The s390 dump mechanisms cannot be swit

Re: [PATCH V3 2/2] mm/memblock: Add support for excluded memory areas

2014-01-14 Thread Philipp Hachtmann
p and refactoring. I will post a V4 patch set which will contain this patch. Kind regards Philipp >From eb1ad42c19c6f7bfdf3258a83dc54461c5f02d55 Mon Sep 17 00:00:00 2001 From: Philipp Hachtmann Date: Tue, 14 Jan 2014 19:49:39 +0100 Subject: [PATCH] mm/memblock: Add support for excluded memory areas A

Re: linux-next: build warning after merge of the final tree (akpm-current related)

2014-01-16 Thread Philipp Hachtmann
Hi Stephen, thanks for reminding me... Am Thu, 16 Jan 2014 17:36:38 +1100 schrieb Stephen Rothwell : > mm/nobootmem.c: In function 'free_low_memory_core_early': > mm/nobootmem.c:119:26: warning: unused variable > 'size' [-Wunused-variable] > Introduced by commit dd3ff251123c ("mm/nobootmem: free_

[PATCH V4 0/2] mm/memblock: Excluded memory

2014-01-16 Thread Philipp Hachtmann
Here is a new version of the memblock.nomap patch. This time without the first patch (that has already been taken by akpm). The second patch is now split into the functional part (Add support...) and the cleanup/refactoring part. This has been done for clarity as announced before. Philipp

[PATCH V4 2/2] mm/memblock: Cleanup and refactoring after addition of nomap

2014-01-16 Thread Philipp Hachtmann
Signed-off-by: Philipp Hachtmann --- include/linux/memblock.h | 50 ++- mm/memblock.c| 214 +-- 2 files changed, 107 insertions(+), 157 deletions(-) diff --git a/include/linux/memblock.h b/include/linux/memblock.h index be1c819

[PATCH V4 1/2] mm/memblock: Add support for excluded memory areas

2014-01-16 Thread Philipp Hachtmann
Add a new memory state "nomap" to memblock. This can be used to truncate the usable memory in the system without forgetting about what is really installed. Signed-off-by: Philipp Hachtmann --- include/linux/memblock.h | 25 +++ mm/Kconfig | 3 + mm/

[PATCH] mm/nobootmem: Fix unused variable

2014-01-16 Thread Philipp Hachtmann
This fixes an unused variable warning in nobootmem.c Signed-off-by: Philipp Hachtmann --- mm/nobootmem.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/mm/nobootmem.c b/mm/nobootmem.c index e2906a5..12cbb04 100644 --- a/mm/nobootmem.c +++ b/mm/nobootmem.c @@ -116,9

Re: [PATCH] mm/nobootmem: Fix unused variable

2014-01-16 Thread Philipp Hachtmann
Hi Robin, > Maybe you are working off a different repo than > Linus' latest? Your line 116 is my 114. Maybe the message needs to > be a bit more descriptive Ah, yes. This fits Andrew's linux-next. Regards Philipp -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" i

Re: [PATCH V4 0/2] mm/memblock: Excluded memory

2014-01-16 Thread Philipp Hachtmann
Patch fits Andrew's linux-next. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] mm/nobootmem: Fix unused variable

2014-01-16 Thread Philipp Hachtmann
> I would think you would be better off making > get_allocated_memblock_reserved_regions_info() and > get_allocated_memblock_memory_regions_info be static inline functions > when #ifdef CONFIG_ARCH_DISCARD_MEMBLOCK. Possible, of course. But the size variable has still to be #ifdef'd. And that's wh

Re: [PATCH V3 2/2] mm/memblock: Add support for excluded memory areas

2014-01-20 Thread Philipp Hachtmann
Am Fri, 17 Jan 2014 18:08:13 + schrieb "Strashko, Grygorii" : Hello Grygorii, > > The current patch seems to be overly complicated. > > The following patch contains only the nomap functionality without > > any cleanup and refactoring. I will post a V4 patch set which will > > contain this pat

Re: [PATCH] mm/nobootmem: Fix unused variable

2014-01-20 Thread Philipp Hachtmann
Am Fri, 17 Jan 2014 13:38:31 -0800 schrieb Andrew Morton : > Yes, that is a bit of an eyesore. We often approach the problem this > way, which is nicer: > [ ... ] > #ifdef CONFIG_ARCH_DISCARD_MEMBLOCK > { > phys_addr_t size; > > [ ... ] > } > #endif Thi

[PATCH V5 1/3] mm/nobootmem: Fix unused variable

2014-01-20 Thread Philipp Hachtmann
This fixes an unused variable warning in nobootmem.c Signed-off-by: Philipp Hachtmann --- mm/nobootmem.c | 28 +--- 1 file changed, 17 insertions(+), 11 deletions(-) diff --git a/mm/nobootmem.c b/mm/nobootmem.c index e2906a5..0215c77 100644 --- a/mm/nobootmem.c +++ b/mm

[PATCH V5 0/3] mm/memblock: Excluded memory

2014-01-20 Thread Philipp Hachtmann
API's behaviour. The third patch does some cleanup and refactoring to memblock. It removes the redundancies introduced by the patch before. It also is not intended to change or break any behaviour or API of memblock. Philipp Hachtmann (3): mm/nobootmem: Fix unused variable mm/memblock: A

[PATCH V5 3/3] mm/memblock: Cleanup and refactoring after addition of nomap

2014-01-20 Thread Philipp Hachtmann
Signed-off-by: Philipp Hachtmann --- include/linux/memblock.h | 50 ++- mm/memblock.c| 214 +-- 2 files changed, 107 insertions(+), 157 deletions(-) diff --git a/include/linux/memblock.h b/include/linux/memblock.h index be1c819

[PATCH V5 2/3] mm/memblock: Add support for excluded memory areas

2014-01-20 Thread Philipp Hachtmann
Add a new memory state "nomap" to memblock. This can be used to truncate the usable memory in the system without forgetting about what is really installed. Signed-off-by: Philipp Hachtmann --- include/linux/memblock.h | 25 +++ mm/Kconfig | 3 + mm/

Re: [PATCH V5 1/3] mm/nobootmem: Fix unused variable

2014-01-20 Thread Philipp Hachtmann
Am Mon, 20 Jan 2014 22:16:33 -0800 (PST) schrieb David Rientjes : > Not sure why you don't just do a one line patch: > > - phys_addr_t size; > + phys_addr_t size __maybe_unused; > to fix it. Just because I did not know that __maybe_unused thing. Discussion of this fix seems to be obso

[PATCH 2/2] usb/ftdi_sio: Add support for setting CBUS pins on FT232H

2014-05-31 Thread Philipp Hachtmann
This patch adds a sysfs attribute "cbus" which allows to set the four CBUS pins on the FT232H. CBUS support could probably extended to all supporting FTDI chips. Signed-off-by: Philipp Hachtmann --- drivers/usb/serial/ftdi_sio.c | 66 ++- d

[PATCH 1/2] usb/ftdi_sio: Add synchronous FIFO mode support for FT232H

2014-05-31 Thread Philipp Hachtmann
This patch adds support for the synchronous FIFO mode of the FT232H serial converter chip. This might also be extended to be usable with other FTDI chips. Signed-off-by: Philipp Hachtmann --- drivers/usb/serial/ftdi_sio.c | 65 +-- drivers/usb/serial

[PATCH 0/2] Add synchronous FIFO and CBUS support for FT232H

2014-05-31 Thread Philipp Hachtmann
d thing right. So I would appreciate any support getting this right. Kind regards Philipp Philipp Hachtmann (2): usb/ftdi_sio: Add synchronous FIFO mode support for FT232H usb/ftdi_sio: Add support for setting CBUS pins on FT232H drivers/usb/serial/ftdi_sio.c | 129 ++

Re: [PATCH 2/2] usb/ftdi_sio: Add support for setting CBUS pins on FT232H

2014-05-31 Thread Philipp Hachtmann
On 01.06.2014 01:31, Philipp Hachtmann wrote: This patch adds a sysfs attribute "cbus" which allows to set the four CBUS pins on the FT232H. The patch contains a *small* error that happened when splitting up my modifications. Next series will contain the clean variant. -- To u

Re: [PATCH 2/2] usb/ftdi_sio: Add support for setting CBUS pins on FT232H

2014-05-31 Thread Philipp Hachtmann
On 01.06.2014 02:00, Peter Stuge wrote: Philipp Hachtmann wrote: This patch adds a sysfs attribute "cbus" which allows to set the four CBUS pins on the FT232H. I think this should be implemented with the gpio subsystem instead. The GPIO subsystem seems to be made for GPIO pins

Re: [PATCH 2/2] usb/ftdi_sio: Add support for setting CBUS pins on FT232H

2014-06-01 Thread Philipp Hachtmann
On 01.06.2014 04:31, Greg KH wrote: As they are GPIO pins on this device, it should be the subsystem that controls it. That way, userspace programs that are used to talk to a GPIO device will "just work", and not have to be customized just for this specific device and sysfs file. So please us

Re: [PATCH 2/2] usb/ftdi_sio: Add support for setting CBUS pins on FT232H

2014-06-01 Thread Philipp Hachtmann
On 02.06.2014 03:38, Greg KH wrote: >> Yes but... I should have avoided the term "GPIO".> No, you used the right term :) Sorry for using the right term :) > No, I am not going to add custom ioctls to a single driver for this. I did neither request nor expect that - did it sound that way? > It

Re: [PATCH] USB: ftdi_sio: add GPIO support

2014-06-16 Thread Philipp Hachtmann
Hi, Would this patch interfere with adding support for using the CBUS pins as GPIOs while operating in normal UART mode? Most interesting question! Care was taken to prevent using GPIOs if the serial device is in use and vice versa. What about CBUS GPIO support? Ok, so we're not extendin

[PATCH 0/2] USB: symbolserial: Fix OOPS (regression) and data length

2015-08-17 Thread Philipp Hachtmann
801.896809] RIP [] _raw_spin_lock_irqsave+0xb/0x30 [ 3801.896811] RSP [ 3801.896812] CR2: [ 3801.896813] ---[ end trace 196415182e1cd411 ]--- Philipp Hachtmann (2): USB: symbolserial: Use usb_get_serial_port_data USB: symbolserial: Correct transferred data size dri

[PATCH 1/2] USB: symbolserial: Use usb_get_serial_port_data

2015-08-17 Thread Philipp Hachtmann
The driver used usb_get_serial_data(port->serial) which compiled but resulted in a NULL pointer being returned (and subsequently used). I did not go deeper into this but I guess this is a regression. Signed-off-by: Philipp Hachtmann --- drivers/usb/serial/symbolserial.c | 6 +++--- 1 f

[PATCH 2/2] USB: symbolserial: Correct transferred data size

2015-08-17 Thread Philipp Hachtmann
ctual barcode data and lots of trailing zeroes. This patch lets the driver only send the real data. Signed-off-by: Philipp Hachtmann --- drivers/usb/serial/symbolserial.c | 18 -- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/drivers/usb/serial/symbolserial.c b/driver

VFS: Parallel unmounting of filesystems produces system call error

2014-11-18 Thread Philipp Hachtmann
Hi Al, I just ran some tests involving many parallel mount and unmount operations. I sometimes get EINVAL and the umount program says "not mounted". Which is definitively wrong. It feels like a race condition somewhere in the VFS code. I use todays master branch (commit fc14f9c1272f62c3) on s390

[PATCH 1/3] sched: Support for CPU runtime and SMT based adaption

2015-01-30 Thread Philipp Hachtmann
econd hook is a call to an architecture function scale_rq_clock_delta which additionally scales the calculated delta by an SMT based factor. Signed-off-by: Philipp Hachtmann --- kernel/sched/core.c | 4 +++- kernel/sched/fair.c | 8 kernel/sched/sched.h | 8 3 files change

[PATCH 3/3] s390/cputime: SMT based scaling of CPU runtime deltas

2015-01-30 Thread Philipp Hachtmann
ta by an SMT based factor. Signed-off-by: Philipp Hachtmann --- arch/s390/include/asm/cputime.h | 17 - arch/s390/kernel/vtime.c| 4 ++-- 2 files changed, 18 insertions(+), 3 deletions(-) diff --git a/arch/s390/include/asm/cputime.h b/arch/s390/include/asm/cputime.h

[RFC] [PATCH 0/3] sched: Support for real CPU runtime and SMT scaling

2015-01-30 Thread Philipp Hachtmann
and defaults to a NOP when not defined by architecture code. Regards Philipp Philipp Hachtmann (3): sched: Support for CPU runtime and SMT based adaption s390/cputime: Provide CPU runtime since IPL s390/cputime: SMT based scaling of CPU runtime deltas arch/s390/include/asm

[PATCH 2/3] s390/cputime: Provide CPU runtime since IPL

2015-01-30 Thread Philipp Hachtmann
The cpu maintains a cpu timer which runs only while the cpu is available to the system (i.e. not scheduled away by the hypervisor). This patch introduces a function cpu_exec_time that returns a time stamp which reflects the cpu's real processing time since IPL. Signed-off-by: Philipp Hach

Re: [PATCH linux-next] fs: remove void * casting in init_once()

2017-05-17 Thread Philipp Hachtmann
On 16.05.2017 20:38, Fabian Frederick wrote: See Documentation/process/coding-style.rst: "Casting the return value which is a void pointer is redundant. The conversion from void pointer to any other pointer type is guaranteed by the C programming language." This will stop copy/paste cascade w