[PATCH 2/4] memory: bcm2835: add bcm2835-memory controller

From: Martin Sperl Add a memory-controller driver for the bcm2835 SOC. This is mostly needed to claim the SDRAM clock so that this (and the corresponding parent pll) never gets disabled. It also exposes the sdram registers via debugfs. Signed-off-by: Martin Sperl

[PATCH 3/4] ARM: dts: bcm2835: add the bcm2835-sdram-controller to the dt

From: Martin Sperl Add the bcm2835 sdram controller to the device tree. Signed-off-by: Martin Sperl --- arch/arm/boot/dts/bcm283x.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/bcm283x.dtsi

[PATCH 1/4] dt: bindings: add bcm2835-memory-controller documentation

From: Martin Sperl Add memory controller dt-binding documentation for the bcm2835 soc. Signed-off-by: Martin Sperl --- .../bindings/memory-controllers/brcm,bcm2835-sdram.txt | 16 1 file changed, 16 insertions(+) create

[PATCH 0/4] add minimal bcm2835-sdram driver

From: Martin Sperl As the sdram clock is a critical clock to the system the minimal bcm2835-sdram driver claims (and enables) this clock and also exposes the corresponding sdram registers via debugfs. Martin Sperl (4): dt: bindings: add bcm2835-memory-controller

[PATCH 4/6] hv_netvsc: get rid of struct net_device pointer in struct netvsc_device

Simplify netvsvc pointer graph by getting rid of the redundant ndev pointer. We can always get a pointer to struct net_device from somewhere else. Signed-off-by: Vitaly Kuznetsov --- drivers/net/hyperv/hyperv_net.h | 2 -- drivers/net/hyperv/netvsc.c | 30

[PATCH 6/6] hv_netvsc: set nvdev link after populating chn_table

Crash in netvsc_send() is observed when netvsc device is re-created on mtu change/set channels. The crash is caused by dereferencing of NULL channel pointer which comes from chn_table. The root cause is a mixture of two facts: - we set nvdev pointer in net_device_context in alloc_net_device()

[PATCH] ASoC: dapm: deprecate MICBIAS widget type

Commit 086d7f804e26 ("ASoC: Convert WM8962 MICBIAS to a supply widget", 2011-09-23) says: A supply widget is generally clearer than a MICBIAS widget and a mic bias is just a type of supply so use a supply widget for the MICBIAS. This also avoids confusion with the routing

Re: [PATCH] arm64: kgdb: Match pstate size with gdbserver protocol

On 10/05/16 15:31, Mark Rutland wrote: On Tue, May 10, 2016 at 02:41:54PM +0100, Daniel Thompson wrote: On 10/05/16 11:45, Mark Rutland wrote: When commit 44679a4f142b ("arm64: KGDB: Add step debugging support") was introduced it was paired with a gdb patch that made an incompatible change to

Re: [PATCH 20/25] arm64:ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

On Thursday 12 May 2016 20:49:24 Zhangjian wrote: > Hi, > > On 2016/5/12 17:21, Arnd Bergmann wrote: > > On Thursday 12 May 2016 10:17:58 Catalin Marinas wrote: > >> On Wed, May 11, 2016 at 09:30:07PM +0200, Arnd Bergmann wrote: > >>> On Wednesday 11 May 2016 17:59:01 Catalin Marinas wrote: > >>>

[UPDATE][PATCH v5] ACPI / processor_idle: introduce ACPI_PROCESSOR_CSTATE

ACPI 6.0 adds a new method to specify the CPU idle states(C-states) called Low Power Idle(LPI) states. Since new architectures like ARM64 use only LPIs, introduce ACPI_PROCESSOR_CSTATE to encapsulate all the code supporting the old style C-states(_CST). This patch will help to extend the

Re: [Question] Missing data after DMA read transfer - mm issue with transparent huge page?

Le 05/12/2016 à 11:36 AM, Jerome Glisse a écrit : > On Thu, May 12, 2016 at 08:07:59AM +0200, Nicolas Morey-Chaisemartin wrote: >> >> Le 05/11/2016 à 04:51 PM, Jerome Glisse a écrit : >>> On Wed, May 11, 2016 at 01:15:54PM +0200, Nicolas Morey Chaisemartin wrote: Le 05/10/2016 à 12:01 PM,

Re: usb: dwc2: regression on MyBook Live Duo / Canyonlands since 4.3.0-rc4

On Thursday, May 12, 2016 01:55:44 PM Arnd Bergmann wrote: > On Thursday 12 May 2016 11:58:18 Christian Lamparter wrote: > > > > > Detecting the endianess of the > > > > > device is probably the best future-proof solution, but it's also > > > > > considerably more work to do in the driver, and

RE: [PATCH V2 1/1] perf/core: don't find side-band event from all pmus

> --- > Subject: perf/core: don't find side-band event from all pmus > From: Kan Liang > Date: Wed, 23 Mar 2016 11:24:37 -0700 > Hi Peter, Is there something wrong with the patch? The last time I saw this patch was in your personal tree (kernel/git/peterz/queue.git). But

Re: [PATCH v3 1/2] drm/fb-cma-helper: Add function drm_fb_cma_create_with_funcs()

Hi Noralf, Thank you for the patch. On Thursday 12 May 2016 14:53:25 Noralf Trønnes wrote: > Add drm_fb_cma_create_with_funcs() for drivers that need to set the > dirty() callback. > > Cc: laurent.pinch...@ideasonboard.com > Signed-off-by: Noralf Trønnes > --- > > Changes

Re: [PATCH V2 1/1] perf/core: don't find side-band event from all pmus

On Thu, May 12, 2016 at 01:30:36PM +, Liang, Kan wrote: > > > > --- > > Subject: perf/core: don't find side-band event from all pmus > > From: Kan Liang > > Date: Wed, 23 Mar 2016 11:24:37 -0700 > > > Hi Peter, > > Is there something wrong with the patch? > The last

Re: [PATCH v2] sched/completion: convert completions to use simple wait queues

On 04/28/2016 02:57 PM, Daniel Wagner wrote: > As one can see above in the swait_stat output, the fork() path is > using completion. A histogram of a fork bomp (1000 forks) benchmark > shows a slight performance drop by 4%. > > [wagi@handman completion-test-5 (master)]$ cat forky-4.6.0-rc4.txt |

[PATCH 1/2] HID: input: rework HID_QUIRK_MULTI_INPUT

The purpose of HID_QUIRK_MULTI_INPUT is to have an input device per report id. This is useful when the HID device presents several HID collections of different device types. The current implementation of hid-input creates one input node per id per type (input or output). This is problematic for

[PATCH 2/2] HID: multitouch: enable the Surface 3 Type Cover to report multitouch data

There is no reasons to filter out keyboard and consumer control collections in hid-multitouch. With the previous hid-input fix, there is now a full support of the Type Cover and we can remove all specific bits from hid-core and hid-microsoft. hid-multitouch will automatically set

Re: [PATCH] kvm-pr: manage illegal instructions

On 12/05/2016 11:27, Alexander Graf wrote: > On 05/12/2016 11:10 AM, Laurent Vivier wrote: >> >> On 11/05/2016 13:49, Alexander Graf wrote: >>> On 05/11/2016 01:14 PM, Laurent Vivier wrote: On 11/05/2016 12:35, Alexander Graf wrote: > On 03/15/2016 09:18 PM, Laurent Vivier wrote: >>

[PATCH v9 6/8] i2c: octeon: Sort include files alphabetically

Sort include files alphabetically to reduce probability of merge conflicts. Signed-off-by: Jan Glauber --- drivers/i2c/busses/i2c-octeon-core.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/i2c/busses/i2c-octeon-core.c

[PATCH v9 5/8] i2c: octeon,thunderx: Move register offsets to struct

The register offsets are different between Octeon and ThunderX so move them into the algorithm struct and get rid of the define. Signed-off-by: Jan Glauber --- drivers/i2c/busses/i2c-cavium.c| 28 +-- drivers/i2c/busses/i2c-cavium.h|

[PATCH v9 8/8] i2c: octeon: thunderx: Add MAINTAINERS entry

The i2c Octeon and ThunderX drivers are maintained by Cavium. While at it fix the whitespace errors of the next entry. Signed-off-by: Jan Glauber Acked-by: David Daney --- MAINTAINERS | 25 + 1 file changed, 17 insertions(+),

[PATCH V5 2/3] soc/tegra: pmc: Correct type of variable for tegra_pmc_readl()

The function tegra_pmc_readl() returns the u32 type data and hence change the data type of variable where this data is stored to u32 type. Signed-off-by: Laxman Dewangan Reviewed-by: Jon Hunter --- Changes from V1: -This is new in series as per

[PATCH V5 0/3] soc/tegra: Add support for IO pads power and voltage control

The IO pins of Tegra SoCs are grouped for common control of IO interface like setting voltage signal levels and power state of the interface. The group is generally referred as IO pads. The power state and voltage control of IO pins can be done at IO pads level. Tegra124 onwards IO pads support

[PATCH V5 1/3] soc/tegra: pmc: Use BIT macro for register field definition

Use BIT macro for register field definition and make constant as U when using in shift operator like (3 << 30) to (3U << 30) Signed-off-by: Laxman Dewangan Acked-by: Jon Hunter --- Changes from V1: - Remove the indenting of line which is not for BIT

Re: [RFC 02/13] mm, page_alloc: set alloc_flags only once in slowpath

On Tue 10-05-16 14:30:11, Vlastimil Babka wrote: [...] > >From 68f09f1d4381c7451238b4575557580380d8bf30 Mon Sep 17 00:00:00 2001 > From: Vlastimil Babka > Date: Fri, 29 Apr 2016 11:51:17 +0200 > Subject: [RFC 02/13] mm, page_alloc: set alloc_flags only once in slowpath > > In

Re: [PATCH 4/5] iommu/mediatek: add support for mtk iommu generation one HW

Hi, Robin, Thanks very much for your comment, and sorry for the last reply format. On Tue, 2016-05-10 at 11:28 +0100, Robin Murphy wrote: > On 09/05/16 09:00, honghui.zh...@mediatek.com wrote: > [...] > > +static void *mtk_iommu_alloc_pgt(struct device *dev, size_t size, gfp_t > > gfp) > > +{ >

Re: [PATCH v2 2/3] mfd: lp873x: Add lp873x PMIC support

On Tue, 10 May 2016, Keerthy wrote: > The LP873X chip is a power management IC for Portable Navigation Systems > and Tablet Computing devices. It contains the following components: > > - Regulators. > - Configurable General Purpose Output Signals(GPO). > > PMIC interacts with the

[PATCH 5/9] docproc: reduce unnecessary indentation

Improves clarity. No functional changes. Signed-off-by: Jani Nikula --- scripts/docproc.c | 93 --- 1 file changed, 47 insertions(+), 46 deletions(-) diff --git a/scripts/docproc.c b/scripts/docproc.c index

Re: [PATCH 20/25] arm64:ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

On Thu, May 12, 2016 at 08:52:46PM +0800, Zhangjian (Bamvor) wrote: > Hi, > > On 2016/5/12 16:24, Yury Norov wrote: > >On Thu, May 12, 2016 at 11:45:53AM +0800, Zhangjian (Bamvor) wrote: > > > >[...] > > > >>>Hmm, that is indeed tricky. I think COMPAT_SYSCALL_WRAP4 rightfully > >>>refuses the

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > > I debugged preadv02 and pwritev02 failures and found very weird bug. > > Test passes {iovec_base = 0x, iovec_len = 64} as one element > > of vector, and kernel

Re: [Question] Missing data after DMA read transfer - mm issue with transparent huge page?

On Thu, May 12, 2016 at 03:30:24PM +0200, Nicolas Morey-Chaisemartin wrote: > Le 05/12/2016 à 11:36 AM, Jerome Glisse a écrit : > > On Thu, May 12, 2016 at 08:07:59AM +0200, Nicolas Morey-Chaisemartin wrote: > >> > >> Le 05/11/2016 à 04:51 PM, Jerome Glisse a écrit : > >>> On Wed, May 11, 2016 at

[PATCH] arm64: Implement optimised IP checksum helpers

AArch64 is capable of 128-bit memory accesses without alignment restrictions, which makes it both possible and highly practical to slurp up a typical 20-byte IP header in just 2 loads. Implement our own version of ip_fast_checksum() to take advantage of that, resulting in considerably fewer

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 03:20:16PM +0100, Catalin Marinas wrote: > On Thu, May 12, 2016 at 03:07:35PM +0100, Catalin Marinas wrote: > > On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > > > On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > > > > On Thu, May 12, 2016 at

[PATCH v2] Xen: EFI: Parse DT parameters for Xen specific UEFI

From: Shannon Zhao The EFI DT parameters for bare metal are located under /chosen node, while for Xen Dom0 they are located under /hyperviosr/uefi node. These parameters under /chosen and /hyperviosr/uefi are not expected to appear at the same time. Parse these EFI

Re: [tip:perf/core] perf/x86/intel/pt: Generate PMI in the STOP region as well

tip-bot for Alexander Shishkin writes: > Commit-ID: 5fbe4788b55540a6c4fe2c47e05482ac356eaf74 > Gitweb: http://git.kernel.org/tip/5fbe4788b55540a6c4fe2c47e05482ac356eaf74 > Author: Alexander Shishkin > AuthorDate: Tue, 10 May 2016

Re: [PATCH v3 2/7] perf tools: Store vdso buildid unconditionally

Em Thu, May 12, 2016 at 08:43:11AM +, He Kuang escreveu: > When unwinding callchains on a different machine, vdso info should be > provided so the unwind process won't be interrupted if address falls > into vdso region. But in most cases, the addresses of sample events > are not in vdso range,

Re: [PATCH net] drivers: net: Don't print unpopulated net_device name

Hi Stephen, On 10/05/16 19:31, Stephen Hemminger wrote: On Tue, 10 May 2016 17:43:21 +0100 Harvey Hunt wrote: For ethernet devices, net_device.name will be eth%d before register_netdev() is called. Don't print the net_device name until the format string is replaced.

Re: next: Crashes in x86 images due to 'locking/rwsem, x86: Clean up ____down_write()'

On Thu, May 12, 2016 at 06:34:29AM -0700, Guenter Roeck wrote: > Borislav, > > your patch 'locking/rwsem, x86: Clean up down_write()' causes various > crashes in x86 qemu tests. Thanks for the report, let me take a look. @Ingo: can you please back this one out of the lineup for the merge

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > > On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > > > I debugged preadv02 and pwritev02 failures and found very weird bug. > > > Test passes {iovec_base =

[PATCH V5 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage

The IO pins of Tegra SoCs are grouped for common control of IO interface like setting voltage signal levels and power state of the interface. The group is generally referred as IO pads. The power state and voltage control of IO pins can be done at IO pads level. Tegra generation SoC supports the

[tip:x86/urgent] x86: Use compat version for preadv2 and pwritev2

Commit-ID: 9a7a076e8e4ffcfec05e3cafe4c4e31d41ddbaa0 Gitweb: http://git.kernel.org/tip/9a7a076e8e4ffcfec05e3cafe4c4e31d41ddbaa0 Author: Dmitry V. Levin AuthorDate: Wed, 11 May 2016 11:48:17 +0300 Committer: Thomas Gleixner CommitDate: Thu, 12 May

[tip:x86/urgent] x86/tsc: Add missing Cherrytrail frequency to the table

Commit-ID: e2724e9d969294879936daf7833d4adda26c8efc Gitweb: http://git.kernel.org/tip/e2724e9d969294879936daf7833d4adda26c8efc Author: Jeremy Compostella AuthorDate: Wed, 11 May 2016 17:23:34 +0200 Committer: Thomas Gleixner CommitDate:

Re: [RFC 03/13] mm, page_alloc: don't retry initial attempt in slowpath

On Tue 10-05-16 09:35:53, Vlastimil Babka wrote: > After __alloc_pages_slowpath() sets up new alloc_flags and wakes up kswapd, it > first tries get_page_from_freelist() with the new alloc_flags, as it may > succeed e.g. due to using min watermark instead of low watermark. This attempt > does not

Re: [PATCH] tools lib traceevent: Do not reassign parg after collapse_tree()

Hi Steve, On Thu, May 12, 2016 at 4:09 AM, Steven Rostedt wrote: > > At the end of process_filter(), collapse_tree() was changed to update the > parg parameter, but the reassignment after the call wasn't removed. > What happens is that the "current_op" gets modified and

[PATCH 1/2] cpufreq: governor: CPUFREQ_GOV_POLICY_EXIT never fails

From: Rafael J. Wysocki None of the cpufreq governors currently in the tree will ever fail an invocation of the ->governor() callback with the event argument equal to CPUFREQ_GOV_POLICY_EXIT (unless invoked with incorrect arguments which doesn't matter anyway) and it

Re: [PATCH RFC 10/22] block, bfq: add full hierarchical scheduling and cgroups support

Il 06/05/2016 22:20, Paolo Valente ha scritto: ... I can now confirm that, because of a little bug, a fraction ranging from one third to half of the writeback bios for the writer is wrongly associated with the root group. I'm sending a bugfix. I'm retesting BFQ after this blk fix. If I

[PATCH 2/2] cpufreq: governor: CPUFREQ_GOV_STOP never fails

From: Rafael J. Wysocki None of the cpufreq governors currently in the tree will ever fail an invocation of the ->governor() callback with the event argument equal to CPUFREQ_GOV_STOP (unless invoked with incorrect arguments which doesn't matter anyway) and it is

[PATCH 0/2] cpufreq: Avoid checking governor return values that are always 0

Hi, As it turns out, all of the existing governors (and the upcoming schedutil one) always return 0 from ->governor() for the event argument equal to _GOV_STOP or _POLICY_EXIT. The following two patches rearrange the core cpufreq code to take that into account. Thanks, Rafael

Re: [RFC 04/13] mm, page_alloc: restructure direct compaction handling in slowpath

On Tue 10-05-16 09:35:54, Vlastimil Babka wrote: > The retry loop in __alloc_pages_slowpath is supposed to keep trying reclaim > and compaction (and OOM), until either the allocation succeeds, or returns > with failure. Success here is more probable when reclaim precedes compaction, > as certain

[GIT PULL] last pin control fix for v4.6

Hi Linus, this will be my last pin control fix for this kernel cycle. It's tagged for stable and only hits a single driver with two added lines so should be safe. Tested in linux-next. Please pull it in! Yours, Linus Walleij The following changes since commit

Re: linux-next: manual merge of the gpio tree with the mips tree

On Thu, May 12, 2016 at 6:17 AM, Stephen Rothwell wrote: > I fixed it up (see below) and can carry the fix as necessary. This > is now fixed as far as linux-next is concerned, but any non trivial > conflicts should be mentioned to your upstream maintainer when your tree >

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > I debugged preadv02 and pwritev02 failures and found very weird bug. > Test passes {iovec_base = 0x, iovec_len = 64} as one element > of vector, and kernel reports successful read/write. > > There are 2 problems: > 1. How

next: Crashes in x86 images due to 'locking/rwsem, x86: Clean up ____down_write()'

Borislav, your patch 'locking/rwsem, x86: Clean up down_write()' causes various crashes in x86 qemu tests. BUG: unable to handle kernel paging request at 8015 IP: [] down_write+0x23/0x30 Call Trace: [] crypto_larval_kill+0x15/0x70 [] crypto_wait_for_test+0x46/0x70 []

Re: [PATCH] pinctrl: stm32: Implement .pin_config_dbg_show()

On Wed, May 11, 2016 at 3:40 PM, Patrice Chotard wrote: > On 05/10/2016 01:50 PM, Linus Walleij wrote: > Sorry i didn't pay attention, but there is a compilation warning in this > patch. > > drivers/pinctrl/stm32/pinctrl-stm32.c:823:7: warning: too many arguments for >

[PATCH v4] platform:x86: Add PMC Driver for Intel Core SOC

This patch adds the Power Management Controller driver as a pci driver for Intel Core SOC architecture. This driver can utilize debugging capabilities and supported features as exposed by the Power Management Controller. Please refer to the below specification for more details on PMC features.

[PATCH v9 4/8] i2c: thunderx: Add SMBUS alert support

Add SMBUS alert interrupt support. For now only device tree is supported for specifying the alert. In case of ACPI an error is returned. Signed-off-by: Jan Glauber --- drivers/i2c/busses/i2c-cavium.h| 6 drivers/i2c/busses/i2c-thunderx-core.c | 51

[PATCH v9 2/8] i2c: octeon: Split the driver into two parts

Move common functionality into a separate file in preparation of the re-use from the ThunderX i2c driver. Functions are slightly re-ordered but no other changes are included. Signed-off-by: Jan Glauber --- drivers/i2c/busses/Makefile | 3 +-

Re: [PATCH] nbd: Move socket shutdown out of spinlock

Hi, On Thursday 12 May 2016 16:42:31 Pranay Srivastava wrote: > Hi Markus, > > > On Thu, May 12, 2016 at 3:13 PM, Markus Pargmann wrote: > > spinlocked ranges should be small and not contain calls into huge > > subfunctions. Fix my mistake and just get the pointer to the

Re: [PATCH v8 1/2] Documentation: DT: dma: Add Xilinx zynqmp dma device tree binding documentation

On 05/12/2016 02:29 PM, Kedareswara rao Appana wrote: [...] > +- xlnx,include-sg: Indicates the controller to operate in simple or > + scatter gather dma mode This is also a software runtime configuration parameter.

[PATCH 3/6] hv_netvsc: untangle the pointer mess

We have the following structures keeping netvsc adapter state: - struct net_device - struct net_device_context - struct netvsc_device - struct rndis_device - struct hv_device and there are pointers/dependencies between them: - struct net_device_context is contained in struct net_device - struct

[PATCH 1/6] hv_netvsc: move start_remove flag to net_device_context

struct netvsc_device is destroyed on mtu change so keeping the protection flag there is not a good idea. Move it to struct net_device_context which is preserved. Signed-off-by: Vitaly Kuznetsov --- drivers/net/hyperv/hyperv_net.h | 4 +++- drivers/net/hyperv/netvsc.c |

[PATCH 5/6] hv_netvsc: synchronize netvsc_change_mtu()/netvsc_set_channels() with netvsc_remove()

When netvsc device is removed during mtu change or channels setup we get into troubles as both paths are trying to remove the device. Synchronize them with start_remove flag and rtnl lock. Signed-off-by: Vitaly Kuznetsov --- drivers/net/hyperv/netvsc_drv.c | 9 +++-- 1

[tip:perf/urgent] perf/x86/intel/pt: Generate PMI in the STOP region as well

Commit-ID: ab92b232ae05c382c3df0e3d6a5c6d16b639ac8c Gitweb: http://git.kernel.org/tip/ab92b232ae05c382c3df0e3d6a5c6d16b639ac8c Author: Alexander Shishkin AuthorDate: Tue, 10 May 2016 16:18:32 +0300 Committer: Ingo Molnar CommitDate:

[PATCH 0/6] hv_netvsc: avoid races on mtu change/set channels

MTU change and set channels operations are implemented as netvsc device re-creation destroying internal structures (struct net_device stays). This is really unfortunate but there is no support from Hyper-V host to do it in a different way. Such re-creation is unsurprisingly racy, Haiyang reported

Re: [tip:perf/core] perf/x86/intel/pt: Generate PMI in the STOP region as well

Ingo Molnar writes: > * Alexander Shishkin wrote: > >> tip-bot for Alexander Shishkin writes: >> >> > Commit-ID: 5fbe4788b55540a6c4fe2c47e05482ac356eaf74 >> > Gitweb: >> >

Re: [PATCH v2 1/3] Documentation: mfd: LP873X: Add information for the mfd and regulator drivers

On Tue, 10 May 2016, Keerthy wrote: > Add information for the mfd and regulator drivers. > > Signed-off-by: Keerthy > --- > Documentation/devicetree/bindings/mfd/lp873x.txt | 55 > > 1 file changed, 55 insertions(+) > create mode 100644

Re: [RFC 05/13] mm, page_alloc: make THP-specific decisions more generic

On Tue 10-05-16 09:35:55, Vlastimil Babka wrote: > Since THP allocations during page faults can be costly, extra decisions are > employed for them to avoid excessive reclaim and compaction, if the initial > compaction doesn't look promising. The detection has never been perfect as > there is no

Re: [PATCH v2] tpm: Fix suspend regression

On Thu, May 12, 2016 at 04:49:52PM +0300, Jarkko Sakkinen wrote: > On Wed, May 11, 2016 at 11:28:27AM -0400, Stefan Berger wrote: > > Fix the suspend regression due to the wrong way of retrieving the > > chip structure. The suspend functions are attached to the hardware > > device, not the chip

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 03:07:35PM +0100, Catalin Marinas wrote: > On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > > On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > > > On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > > > > I debugged preadv02 and

URGENT RESPONSE NEEDED, PLEASE REPLY....

Dear Friend, Pardon me for not having the pleasure of knowing your mindset before making you this offer and it is utterly confidential and genuine by virtue of its nature I write to solicit your assistance in a funds transfer deal involving £15.2M.This fund has been stashed out of the excess

[PATCH v8 1/2] Documentation: DT: dma: Add Xilinx zynqmp dma device tree binding documentation

Device-tree binding documentation for Xilinx zynqmp dma engine used in Zynq UltraScale+ MPSoC. Signed-off-by: Punnaiah Choudary Kalluri Signed-off-by: Kedareswara rao Appana --- Changes in v8: - Removed all the software runtime configuration parameters

[PATCH v8 2/2] dmaengine: Add Xilinx zynqmp dma engine driver support

Added the driver for zynqmp dma engine used in Zynq UltraScale+ MPSoC. This dma controller supports memory to memory and memory to I/O buffer transfers. Signed-off-by: Punnaiah Choudary Kalluri Signed-off-by: Kedareswara rao Appana --- Changes for v8: -

[PATCH 2/6] hv_netvsc: use start_remove flag to protect netvsc_link_change()

netvsc_link_change() can race with netvsc_change_mtu() or netvsc_set_channels() as these functions destroy struct netvsc_device and rndis filter. Use start_remove flag for syncronization. As netvsc_change_mtu()/netvsc_set_channels() are called with rtnl lock held we need to take it before checking

Re: [PATCH 20/25] arm64:ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

Hi, On 2016/5/12 17:21, Arnd Bergmann wrote: On Thursday 12 May 2016 10:17:58 Catalin Marinas wrote: On Wed, May 11, 2016 at 09:30:07PM +0200, Arnd Bergmann wrote: On Wednesday 11 May 2016 17:59:01 Catalin Marinas wrote: I don't think the shifts are a problem, the main downside would be the

[tip:perf/urgent] perf/core: Disable the event on a truncated AUX record

Commit-ID: 9f448cd3cbcec8995935e60b27802ae56aac8cc0 Gitweb: http://git.kernel.org/tip/9f448cd3cbcec8995935e60b27802ae56aac8cc0 Author: Alexander Shishkin AuthorDate: Tue, 10 May 2016 16:18:33 +0300 Committer: Ingo Molnar CommitDate:

Re: [PATCH -v2] x86/hweight: Get rid of the special calling convention

On Thu, May 12, 2016 at 02:14:52PM +0200, Peter Zijlstra wrote: > But this is a C function, with C calling convention. You're now assuming > GCC doesn't clobber anything with its prologue/epilogue. > > I think hpa meant to put it in an .S file and avoid all that. I wanted to have gcc use %[w]

Re: [PATCH v3 3/7] perf tools: Remove the logical that skip buildid cache if symfs is given

Em Thu, May 12, 2016 at 08:43:12AM +, He Kuang escreveu: > Symfs dir and buildid dir are two places that perf looks into for > symbols, currently, if symfs dir is given, buildid-cache is skipped. > > In the cross-platform perf record/script scenario, we need vdsos in > buildid-cache dir and

Re: [PATCH v7 0/5] ACPI: parse the SPCR table

On 2016/5/12 19:52, Aleksey Makarov wrote: > Hi Jon, > > In v7 I addressed the issues that were brought up by Rafael J . Wysocki > (but I still do not have ACK from ACPI people). > > The issue with D02 will be addressed in a separate patch. > > There possibly is an issue with 16550 and

[PATCH 4/9] docproc: add variables for subcommand and filename

Improves clarity. No functional changes. Signed-off-by: Jani Nikula --- scripts/docproc.c | 17 +++-- 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/scripts/docproc.c b/scripts/docproc.c index e267e621431a..48abc01a920e 100644 ---

[PATCH 2/9] kernel-doc: produce RestructuredText output

From: Jonathan Corbet If given the -rst flag, output will now be in RestructuredText. Various glitches to be worked out yet. In the end I decided not to use RST section headings within the kerneldoc comments. gpu.tmpl already has headings five levels deep; adding more is not

[PATCH 0/9] kernel-doc/docproc prep work for reStructuredText

Jon, I was hoping we could consider nudging things forward a bit in the kernel-doc and docproc reStructuredText front already in 4.7. I know it's a bit close to the merge window, but this should not interfere with anything else, and some of it are just trivial cleanups that I've been carrying

[PATCH 1/9] kernel-doc: rewrite usage description, remove duplicated comments

Instead of having the kernel-doc usage in both comments and in output to the user, merge them all to one here document. While at it, imrove the text and make it pretty. Give shoemaker's children some shoes. Signed-off-by: Jani Nikula --- scripts/kernel-doc | 83

Re: [PATCH net] drivers: net: Don't print unpopulated net_device name

Hi David, On 12/05/16 00:26, David Miller wrote: From: Harvey Hunt Date: Tue, 10 May 2016 17:43:21 +0100 @@ -1686,8 +1686,7 @@ dm9000_probe(struct platform_device *pdev) } if (!is_valid_ether_addr(ndev->dev_addr)) { - dev_warn(db->dev,

RE: [PATCH 1/1] perf/core: fix implicitly enable dynamic interrupt throttle

> > > Hmm, would it not be nicer to simply reject the write instead of silently > ignoring it? > Yes, I agree. Thanks, Kan > --- > kernel/events/core.c | 7 +++ > 1 file changed, 7 insertions(+) > > diff --git a/kernel/events/core.c b/kernel/events/core.c index >

Re: [PATCH] tools lib traceevent: Do not reassign parg after collapse_tree()

Em Thu, May 12, 2016 at 09:57:13PM +0900, Namhyung Kim escreveu: > Hi Steve, > > On Thu, May 12, 2016 at 4:09 AM, Steven Rostedt wrote: > > > > At the end of process_filter(), collapse_tree() was changed to update the > > parg parameter, but the reassignment after the call

[PATCH v9 0/8] i2c-octeon and i2c-thunderx driver

Hi Wolfram, this update adds ACPI support for the clock-frequency setting in the thunderx driver. For SMBUS alert support it is currently unclear how it will look like in ACPI so I left that unimplemented. Patch #5 - #7 are (final) cleanup patches. Patches are on-top of next-20160512. Changes

[PATCH v9 3/8] i2c: thunderx: Add i2c driver for ThunderX SOC

The ThunderX SOC uses the same i2c block as the Octeon SOC. The main difference is that on ThunderX the device is a PCI device so device probing is done via PCI, interrupts are MSI-X. The clock rates can be set via device tree or ACPI. Signed-off-by: Jan Glauber ---

[PATCH v9 7/8] i2c: cavium: Use booleon values for booleon variables

Initialize booleon values with true instead of 1. Signed-off-by: Jan Glauber --- drivers/i2c/busses/i2c-cavium.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/i2c/busses/i2c-cavium.c b/drivers/i2c/busses/i2c-cavium.c index e95ee5c..140f0d1

[PATCH v9 1/8] i2c: octeon: Rename driver to prepare for split

This is an intermediate commit in preparation of the driver split. The module rename in this commit will be reverted in the next patch, this is just done to make the series bisectible. Signed-off-by: Jan Glauber --- drivers/i2c/busses/Makefile| 2

[PATCH 4/4] ARM: bcm2835_defconfig: add bcm2835-sdram controller

From: Martin Sperl Add the bcm2835-sdram controller driver to the default config. (as the driver is enabled by default vi KConfig, we only need to enable CONFIG_MEMORY) Signed-off-by: Martin Sperl --- arch/arm/configs/bcm2835_defconfig | 1 +

[PATCH v2 2/2] powerpc/fadump: add support to parse size based on memory range

Currently, memory for fadump can be specified with fadump_reserve_mem=size, where only a fixed size can be specified. Add the below syntax as well, to support conditional reservation based on system memory size: fadump_reserve_mem=:[,:,...] This syntax helps using the same commandline

Re: pwm: atmel: PWM may not properly disable

2016-05-12 14:14 GMT+02:00 Thierry Reding : > On Thu, May 12, 2016 at 01:49:12PM +0200, Guillermo Rodriguez Garcia wrote: >> Hello, >> >> [...] >> >>> One thing that I'd request is that instead of the cpu_relax() you use a >> >>> usleep_range() within the loop instead. I

[PATCH 3/9] kernel-doc: use rst C domain directives and references for types

First, the headings for structs, enums and typedefs will be similar to functions. Second, this provides a kind of namespace for cross references. Third, and most importantly, the return and parameter types from .. c:function:: definitions will automagically become cross references to the

Re: linux-next: build failure after merge of the pinctrl tree

Laxman, this must be due to one of the two top commits for tegra: commit 1d18a3f0f0809f6c71f1f6e9e268ee904ce0b588 "pinctrl: tegra: avoid parked_reg and parked_bank" commit b22ef2a0979f2b91cfeeabb086e4d665183a93a1 "pinctrl: tegra: Correctly check the supported configuration" Is it something you

[PATCH ] pinctrl: tegra: Get rid of parked_reg

Remove the use of parked_reg and use parked_bit for to know whether field is supported or not. This is fix for the patch commit 1d18a3f0f0809f6c71f1f6e9e268ee904ce0b588 "pinctrl: tegra: avoid parked_reg and parked_bank Signed-off-by: Laxman Dewangan ---

[PATCH] arm: tegra: initial support for apalis tk1

This patch adds the device tree to support Toradex Apalis TK1 a computer on module which can be used on different carrier boards. The module consists of a Tegra TK1 SoC, a PMIC solution, 2 GB of DDR3L RAM, a bunch of level shifters, an eMMC, a TMP451 temperature sensor chip and an I210 gigabit

[PATCH v3 2/2] drm: Add helper for simple display pipeline

Provides helper functions for drivers that have a simple display pipeline. Plane, crtc and encoder are collapsed into one entity. Cc: jsa...@ti.com Signed-off-by: Noralf Trønnes --- Changes since v2: - Drop Kconfig knob DRM_KMS_HELPER - Expand documentation Changes since

[PATCH v3 0/2] drm: Add various helpers for simple drivers

This patchset adds various helpers that was originally part of the tinydrm patchset. 4 patches from the previous version have been applied and 2 are now left. Essentially it adds 2 functions: - drm_fb_cma_create_with_funcs() CMA backed framebuffer supporting a dirty() callback. -

Re: [PATCH v6 00/14] ACPI NUMA support for ARM64

On Thu, May 12, 2016 at 10:56 AM, Will Deacon wrote: > On Thu, May 12, 2016 at 12:29:02AM +0200, Rafael J. Wysocki wrote: >> On Wed, May 11, 2016 at 11:30 PM, David Daney >> wrote: >> > On 05/11/2016 02:22 PM, Rafael J. Wysocki wrote: >> >> On

  1   2   3   4   5   6   7   8   9   10   >