Re: [PATCH v4] usb: dwc2: fix regression on big-endian PowerPC/ARM systems

2016-05-13 Thread John Youn
On 5/13/2016 6:53 AM, Arnd Bergmann wrote: > A patch that went into Linux-4.4 to fix big-endian mode on a Lantiq > MIPS system unfortunately broke big-endian operation on PowerPC > APM82181 as reported by Christian Lamparter, and likely other > systems. > > It actually introduced multiple issues:

udgb on fsl booke?

2016-05-13 Thread Daniel Walker
Hi, I noticed that udbg is missing for fsl booke , or at least it doesn't appear to be implemented. I don't know a great deal about fsl book. I'm working on an MCP85XX at the moment , and I was looking into the udbg system to get prints. It looks like fsl booke might be similar enough to

Re: [PATCH-next v2 0/2] cpufreq: powernv: Fixes for Global pstate management

2016-05-13 Thread Rafael J. Wysocki
On Monday, May 09, 2016 09:02:04 PM Viresh Kumar wrote: > On 03-05-16, 20:49, Akshay Adiga wrote: > > Fixes are based on patch https://patchwork.ozlabs.org/patch/612058/ which > > is in Rafael's linux-next. > > > > - Patch [1] fixes WARN_ON in powernv_target_index() > > - Patch [2] Deleting any

Re: [PATCH 5/5] vfio-pci: Allow to mmap MSI-X table if interrupt remapping is supported

2016-05-13 Thread Alex Williamson
On Fri, 13 May 2016 06:50:25 + "Tian, Kevin" wrote: > > From: Alex Williamson [mailto:alex.william...@redhat.com] > > Sent: Friday, May 13, 2016 1:33 PM > > > > > > > > As argued previously in this thread, there's nothing special about a > > > > DMA write to memory

[PATCH RESEND v8] powerpc32: provide VIRT_CPU_ACCOUNTING

2016-05-13 Thread Christophe Leroy
This patch provides VIRT_CPU_ACCOUTING to PPC32 architecture. PPC32 doesn't have the PACA structure, so we use the task_info structure to store the accounting data. In order to reuse on PPC32 the PPC64 functions, all u64 data has been replaced by 'unsigned long' so that it is u32 on PPC32 and u64

[PATCH v4] usb: dwc2: fix regression on big-endian PowerPC/ARM systems

2016-05-13 Thread Arnd Bergmann
A patch that went into Linux-4.4 to fix big-endian mode on a Lantiq MIPS system unfortunately broke big-endian operation on PowerPC APM82181 as reported by Christian Lamparter, and likely other systems. It actually introduced multiple issues: - it broke big-endian ARM kernels: any machine that

Re: [PATCH v3] usb: dwc2: fix regression on big-endian PowerPC/ARM systems

2016-05-13 Thread Arnd Bergmann
On Thursday 12 May 2016 23:32:18 John Youn wrote: > > Hi Arnd, > > The capitalization issue is still there in this patch. > > There's also a few checkpatch issues. Fixed now, thanks. I'll send a v4 in a bit. > And should the barrier be moved after the write like it says in the > comment? That

[PATCH] drivers/of: Fix build warning in populate_node()

2016-05-13 Thread Gavin Shan
Function populate_node() is used to unflatten FDT blob to device tree. It supports maximal 64 level of device nodes. There is one array @fpsizes[64] tracking the full name length of last unflattened device node in the corresponding level (index of element in the array - 1). Build warning is seen

Re: [PATCH v2 1/7] powerpc/8xx: Fix vaddr for IMMR early remap

2016-05-13 Thread Christophe Leroy
Le 11/05/2016 à 22:38, Scott Wood a écrit : On Wed, 2016-05-11 at 17:03 +0200, Christophe Leroy wrote: Memory: 124428K/131072K available (3748K kernel code, 188K rwdata, 648K rodata, 508K init, 290K bss, 6644K reserved) Kernel virtual memory layout: * 0xfffdf000..0xf000 : fixmap *

RE: [PATCH 5/5] vfio-pci: Allow to mmap MSI-X table if interrupt remapping is supported

2016-05-13 Thread David Laight
From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: 13 May 2016 06:33 ... > Simply denying direct writes to the vector table or preventing mapping > of the vector table into the user address space does not provide any > tangible form of protection. Many devices make use of window

Re: powerpc: Discard ffs() function and use builtin_ffs instead

2016-05-13 Thread Gabriel Paubert
On Fri, May 13, 2016 at 04:16:57PM +1000, Michael Ellerman wrote: > On Thu, 2016-12-05 at 15:32:22 UTC, Christophe Leroy wrote: > > With the ffs() function as defined in arch/powerpc/include/asm/bitops.h > > GCC will not optimise the code in case of constant parameter, as shown > > by the small

Re: [PATCH v7 45/50] drivers/of: Avoid recursively calling unflatten_dt_node()

2016-05-13 Thread Geert Uytterhoeven
On Wed, Nov 4, 2015 at 5:07 PM, Rob Herring wrote: > On Wed, Nov 4, 2015 at 7:12 AM, Gavin Shan wrote: >> In current implementation, unflatten_dt_node() is called recursively >> to unflatten device nodes in FDT blob. It's stress to limited stack

Re: powerpc: Discard ffs() function and use builtin_ffs instead

2016-05-13 Thread Christophe Leroy
Le 13/05/2016 à 08:16, Michael Ellerman a écrit : On Thu, 2016-12-05 at 15:32:22 UTC, Christophe Leroy wrote: With the ffs() function as defined in arch/powerpc/include/asm/bitops.h GCC will not optimise the code in case of constant parameter, as shown by the small exemple below. int

RE: [PATCH 5/5] vfio-pci: Allow to mmap MSI-X table if interrupt remapping is supported

2016-05-13 Thread Tian, Kevin
> From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Friday, May 13, 2016 1:33 PM > > > > > > As argued previously in this thread, there's nothing special about a > > > DMA write to memory versus a DMA write to a special address that > > > triggers an MSI vector. If the device is

Re: [PATCH v3] usb: dwc2: fix regression on big-endian PowerPC/ARM systems

2016-05-13 Thread John Youn
On 5/12/2016 1:56 PM, Arnd Bergmann wrote: > A patch that went into Linux-4.4 to fix big-endian mode on a Lantiq > MIPS system unfortunately broke big-endian operation on PowerPC > APM82181 as reported by Christian Lamparter, and likely other > systems. > > It actually introduced multiple issues:

Re: powerpc: Discard ffs() function and use builtin_ffs instead

2016-05-13 Thread Michael Ellerman
On Thu, 2016-12-05 at 15:32:22 UTC, Christophe Leroy wrote: > With the ffs() function as defined in arch/powerpc/include/asm/bitops.h > GCC will not optimise the code in case of constant parameter, as shown > by the small exemple below. > > int ffs_test(void) > { > return 4 << ffs(31); > }