Re: [linux-sunxi] [PATCH 02/11] arm64: allwinner: a64: add NMI controller on A64

On Wed, Apr 5, 2017 at 2:11 PM, Maxime Ripard wrote: > On Wed, Apr 05, 2017 at 11:51:45AM +0800, Chen-Yu Tsai wrote: >> On Wed, Apr 5, 2017 at 2:01 AM, Icenowy Zheng wrote: >> > Allwinner A64 SoC features a NMI controller, which is usually

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Wed, Apr 05, 2017 at 06:24:50AM +0200, Mike Galbraith wrote: > On Wed, 2017-04-05 at 06:51 +0300, Michael S. Tsirkin wrote: > > > Any issues at all left with this tree? > > In particular any regressions? > > Nothing blatantly obvious in a testdrive that lasted a couple minutes. > I'd have

Re: [PATCH v6 02/11] powerpc/powernv: Autoload IMC device driver module

On Tuesday 04 April 2017 06:28 AM, Daniel Axtens wrote: Hi all, I'm trying to get my head around these patches - at this point I'm just doing a first pass, so I may have more substantive structural comments later on. In the mean time - here are some minor C nits: + * Copyright (C) 2016

Re: [PATCH 3/9] bio-integrity: bio_integrity_advance must update integrity seed

On 04/04/2017 08:56 PM, Dmitry Monakhov wrote: > SCSI drivers do care about bip_seed so we must update it accordingly. > > Signed-off-by: Dmitry Monakhov > --- > block/bio-integrity.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/block/bio-integrity.c

Re: [PATCH 7/9] Guard bvec iteration logic v3

On 04/04/2017 08:56 PM, Dmitry Monakhov wrote: > Currently if some one try to advance bvec beyond it's size we simply > dump WARN_ONCE and continue to iterate beyond bvec array boundaries. > This simply means that we endup dereferencing/corrupting random memory > region. > > Sane reaction would

[PATCH v2 04/11] platform/x86: fujitsu-laptop: simplify set_lcd_level()

acpi_execute_simple_method() takes a method parameter which tells it to look for the given method underneath the given handle, so calling acpi_get_handle() beforehand is redundant. Replace the call to acpi_get_handle() with a call to acpi_execute_simple_method(), thus eliminating the need for a

[PATCH v2 05/11] platform/x86: fujitsu-laptop: sync brightness in set_lcd_level()

When using brightness keys and backlight device's sysfs interface alternately, an incorrect input event might be generated for a brightness key press. Consider the following sequence of events: 1. Set backlight brightness to 6 using brightness keys. 2. Write 4 to

[PATCH v2 03/11] platform/x86: fujitsu-laptop: merge set_lcd_level_alt() into set_lcd_level()

Depending on the value of the use_alt_lcd_levels module parameter, one of two functions is used for setting LCD brightness level. These functions are almost identical and only differ in the name of the ACPI method they call. Instead of checking the value of use_alt_lcd_levels at each call site,

[PATCH v2 02/11] platform/x86: fujitsu-laptop: switch to a managed backlight device

Use a managed backlight device to get rid of acpi_fujitsu_bl_remove(). Change the parent of the backlight device from NULL to the FUJ02B1 ACPI device as the latter is required for the backlight device to work. Signed-off-by: Michał Kępień ---

[PATCH v2 01/11] platform/x86: fujitsu-laptop: only handle backlight when appropriate

The backlight part of fujitsu-laptop is only used by laptops which are incapable of using the standard ACPI video interface for handling brightness changes. Conversely, on laptops which are capable of using the latter, no vendor-specific ACPI calls should be made unless explicitly requested by

Re: question about concurrent regmap i2c usage

On 04.04.2017 14:26, Mark Brown wrote: On Tue, Apr 04, 2017 at 10:28:23AM +0200, Michael Hennerich wrote: A question came up, regarding whether it's recommended to mix regmap_i2c and plain i2c_smbus or direct adapter transfers. In this specific case for the i2c MUX portion we need to avoid

Re: [PATCH 8/9] bio: add bvec_iter rewind API

On 04/04/2017 08:56 PM, Dmitry Monakhov wrote: > Some ->bi_end_io handlers (for example: pi_verify or decrypt handlers) > need to know original data vector, but after bio traverse io-stack it may > be advanced, splited and relocated many times so it is hard to guess > original iterator. Let's add

Re: [PATCH 9/9] bio-integrity: Restore original iterator on verify stage

On 04/04/2017 08:56 PM, Dmitry Monakhov wrote: > Currently ->verify_fn not woks at all because at the moment it is called > bio->bi_iter.bi_size == 0, so we do not iterate integrity bvecs at all. > > In order to perform verification we need to know original data vector, > with new bvec rewind API

[PATCH v2 06/11] platform/x86: fujitsu-laptop: clean up use_alt_lcd_levels handling

The value of each module parameter can be changed on the fly via sysfs. However, the current way of handling use_alt_lcd_levels prevents the user from dynamically switching from a value of 0 or 1 back to autodetection as the latter is only performed upon ACPI device instantiation. Fix this by

[PATCH v2 3/3] platform/x86: fujitsu-laptop: rename call_fext_func() arguments

Rename call_fext_func() arguments so that each argument's name signifies its role: - cmd -> func: sub-function to call (flags, buttons etc.), - arg0 -> op: operation to perform (get, set, get capabilities etc.), - arg1 -> feature: feature to act on (e.g. which LED), if relevant, - arg2 ->

[PATCH v2 1/3] platform/x86: fujitsu-laptop: clean up local variables in call_fext_func()

Set values of FUNC call parameters in a designated initializer. Do not initialize status and handle variables as the values these are initialized to have no influence on execution flow. Use an array variable instead of the address of the first element of that array. Signed-off-by: Michał Kępień

[PATCH v2 0/3] fujitsu-laptop: call_fext_func() cleanup

This series contains a few cleanups for the call_fext_func() function. Just as a reminder, please note that v1 of this series is currently applied in testing. Changes from v1: - Update debug message logged by call_fext_func() to reflect code flow changes introduced by patch 2/3.

[PATCH v2 08/11] platform/x86: fujitsu-laptop: ignore errors when setting backlight power

Not all Fujitsu laptops support controlling backlight power through the FUJ02E3 ACPI device. Remove the debug message informing about a failed attempt to set backlight power as it may be confusing and the return value of call_fext_func() is logged anyway. Signed-off-by: Michał Kępień

Re: [PATCH v2 2/4] reset: Add APIs to manage array of resets

Hi Philipp, On 04/04/2017 06:17 PM, Philipp Zabel wrote: Hi Vivek, On Tue, 2017-04-04 at 16:09 +0530, Vivek Gautam wrote: [...] I'd prefer to mirror the gpiod API a little, and to have the number contained in the array structure, similar to struct gpio_descs: [...] Alright, i can update

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Wed, 2017-04-05 at 08:29 +0200, Christoph Hellwig wrote: > Can you check where the issues appear? I'd like to do a pure revert > of the shared interrupts, but that three has a lot more in it.. Not immediately, one of my several pots is emitting black smoke. -Mike

[PATCH v2 09/11] platform/x86: fujitsu-laptop: do not log set_lcd_level() failures in bl_update_status()

Any set_lcd_level() call can fail for one of two reasons: either requested brightness is outside the allowed range or the ACPI method used for setting brightness level is not available. For bl_update_status(), the first case is handled by backlight core, which means bl_update_status() will not

[PATCH v2 2/3] platform/x86: fujitsu-laptop: simplify call_fext_func()

acpi_evaluate_integer() takes a pathname parameter which contains the name of the entity to evaluate underneath the given handle, so calling acpi_get_handle() beforehand is redundant. Replace the call to acpi_get_handle() with a call to acpi_evaluate_integer(), thus eliminating the need for a

Re: net/sched: latent livelock in dev_deactivate_many() due to yield() usage

On Tue, 2017-04-04 at 22:25 -0700, Cong Wang wrote: > On Tue, Apr 4, 2017 at 8:20 PM, Mike Galbraith wrote: > > - while (some_qdisc_is_busy(dev)) > > - yield(); > > + swait_event_timeout(swait, > > !some_qdisc_is_busy(dev), 1); > >

Re: [PATCH 10/11] arm64: allwinner: a64: enable AXP803 regulators for Pine64

On Wed, Apr 05, 2017 at 02:01:44AM +0800, Icenowy Zheng wrote: > Add support of AXP803 regulators in the Pine64 device tree, in order to > enable many future functionalities, e.g. Wi-Fi. > > Signed-off-by: Icenowy Zheng > --- > .../arm64/boot/dts/allwinner/sun50i-a64-pine64.dts

Re: [PATCH v4 0/6] ARM: dts: sunxi: Add CAN node and can0_pins_a pinctrl settings

On Tue, Apr 04, 2017 at 08:36:26PM +0200, Patrick Menschel wrote: > The Allwinner A10/A20 SoCs have an on-board CAN (Controller Area Network) > controller. This patch adds the CAN core to the SoC's include files, > sun4i-a10.dtsi and sun7i-a20.dtsi. > > On linux-can mailing list was a discussion

Re: [PATCH 1/2] doc: Add bindings document for Xilinx LogiCore PR Decoupler

On 5.4.2017 01:36, Moritz Fischer wrote: > On Thu, Mar 30, 2017 at 05:44:29PM -0500, Rob Herring wrote: >> On Fri, Mar 24, 2017 at 10:33:20AM -0500, Alan Tull wrote: >>> From: Moritz Fischer >> >> Please use "dt-bindings: fpga: ..." for the subject. >> >> >>> >>> This adds the

Re: [PATCH] net: thunderx: Switch to pci_alloc_irq_vectors

On Tue, Apr 04, 2017 at 02:59:06PM +0530, dev.srinivas...@gmail.com wrote: > From: Thanneeru Srinivasulu > > Remove deprecated pci_enable_msix API in favour of it's > successor pci_alloc_irq_vectors. > > Signed-off-by: Thanneeru Srinivasulu >

Re: [PATCH v6 02/11] powerpc/powernv: Autoload IMC device driver module

On Tuesday 04 April 2017 07:18 AM, Daniel Axtens wrote: Hi, + do { + pages = PAGE_SIZE * i; + pcni->vbase[i++] = (u64)phys_to_virt(pcni->pbase + +pages); + }

Re: [PATCH 6/9] T10: Move opencoded contants to common header

On 04/04/2017 08:56 PM, Dmitry Monakhov wrote: > Signed-off-by: Dmitry Monakhov > --- > block/t10-pi.c | 9 +++-- > drivers/scsi/lpfc/lpfc_scsi.c| 5 +++-- > drivers/scsi/qla2xxx/qla_isr.c | 8 > drivers/target/target_core_sbc.c | 2 +- >

Re: [PATCH 5/9] bio-integrity: fold bio_integrity_enabled to bio_integrity_prep

On 04/04/2017 08:56 PM, Dmitry Monakhov wrote: > Currently all integrity prep hooks are open-coded, and if prepare fails > we ignore it's code and fail bio with EIO. Let's return real error to > upper layer, so later caller may react accordingly. > > In fact no one want to use

Re: [PATCH] net: thunderx: Switch to pci_alloc_irq_vectors

On Wed, Apr 5, 2017 at 11:57 AM, Christoph Hellwig wrote: > On Tue, Apr 04, 2017 at 02:59:06PM +0530, dev.srinivas...@gmail.com wrote: >> From: Thanneeru Srinivasulu >> >> Remove deprecated pci_enable_msix API in favour of it's >> successor

Re: [linux-sunxi] [PATCH 02/11] arm64: allwinner: a64: add NMI controller on A64

On Wed, Apr 05, 2017 at 02:20:31PM +0800, Chen-Yu Tsai wrote: > On Wed, Apr 5, 2017 at 2:11 PM, Maxime Ripard > wrote: > > On Wed, Apr 05, 2017 at 11:51:45AM +0800, Chen-Yu Tsai wrote: > >> On Wed, Apr 5, 2017 at 2:01 AM, Icenowy Zheng wrote: >

[PATCH] drm: bridge: dw-hdmi: remove unused hdmi_bus_fmt_is_yuv420

Remove usused yet hdmi_bus_fmt_is_yuv420 function. Fixes: def23aa7e982 ("drm: bridge: dw-hdmi: Switch to V4L bus format and encodings") Signed-off-by: Neil Armstrong --- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 14 -- 1 file changed, 14 deletions(-)

Re: [RFC PATCH v1 00/30] fs: inode->i_version rework and optimization

On Wed 05-04-17 11:43:32, NeilBrown wrote: > On Tue, Apr 04 2017, J. Bruce Fields wrote: > > > On Thu, Mar 30, 2017 at 02:35:32PM -0400, Jeff Layton wrote: > >> On Thu, 2017-03-30 at 12:12 -0400, J. Bruce Fields wrote: > >> > On Thu, Mar 30, 2017 at 07:11:48AM -0400, Jeff Layton wrote: > >> > >

Re: dm: move dm_table_destroy() to same header as dm_table_create()

Hi, On 05/04/17 00:35, Brian Norris wrote: > On Tue, Mar 28, 2017 at 03:31:51PM -0400, Mike Snitzer wrote: >> On Tue, Mar 28 2017 at 2:31pm -0400, >> Brian Norris wrote: >> >>> If anyone is going to use dm_table_create(), they probably should be >>> able to use

Re: [PATCH] drm: bridge: dw-hdmi: remove unused hdmi_bus_fmt_is_yuv420

Hi Neil, Thank you for the patch. On Wednesday 05 Apr 2017 09:32:59 Neil Armstrong wrote: > Remove usused yet hdmi_bus_fmt_is_yuv420 function. > > Fixes: def23aa7e982 ("drm: bridge: dw-hdmi: Switch to V4L bus format and > encodings") Signed-off-by: Neil Armstrong

Re: [PATCH] xen, fbfront: add support for specifying size via xenstore

On 23/03/17 13:53, Juergen Gross wrote: > Today xen-fbfront supports specifying the display size via module > parameters only. Add support for specifying the size via Xenstore in > order to enable doing this easily via the domain's Xen configuration. > > Add an error message in case the

Re: [PATCH] xen, fbfront: fix connecting to backend

On 23/03/17 13:52, Juergen Gross wrote: > Connecting to the backend isn't working reliably in xen-fbfront: in > case XenbusStateInitWait of the backend has been missed the backend > transition to XenbusStateConnected will trigger the connected state > only without doing the actions required when

Re: [RFC PATCH] kernel: sched: Provide a pointer to the valid CPU mask

On 2017-04-05 09:39:43 [+0200], Ingo Molnar wrote: > > So maybe we could add the following facility: > > ptr = sched_migrate_to_cpu_save(cpu); > > ... > > sched_migrate_to_cpu_restore(ptr); > > ... and use it in the cpufreq code. Then -rt could simply define >

Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage

On (04/05/17 15:29), Ye Xiaolong wrote: [..] > >>does this patch make it any better? > > > >I am trying it and will post the result once I get it. > > Sorry for the late. I applied the patch of on top of the fbc14616f4 ("printk: > enable printk offloading") > and the "reboot-without-waring"

[PATCH v1] mtd: mtk-nor: set controller's address width according to nor flas

Guochun Mao (1): mtd: mtk-nor: set controller's address width according to nor flash drivers/mtd/spi-nor/mtk-quadspi.c | 27 +++ 1 file changed, 27 insertions(+) -- 1.9.1

[PATCH v5 6/7] ARM: dts: sun8i: sina33: enable battery power supply subnode

The Sinlinx SinA33 has an AXP223 PMIC and a battery connector, thus, we enable the battery power supply subnode in its Device Tree. Signed-off-by: Quentin Schulz Acked-by: Maxime Ripard Acked-by: Chen-Yu Tsai

[PATCH -mm -v2] mm, swap: Sort swap entries before free

From: Huang Ying To reduce the lock contention of swap_info_struct->lock when freeing swap entry. The freed swap entries will be collected in a per-CPU buffer firstly, and be really freed later in batch. During the batch freeing, if the consecutive swap entries in the

Re: [PATCH 04/17] pci: Add arch_can_pci_mmap_wc() macro

On Tue, 2017-04-04 at 16:36 -0500, Bjorn Helgaas wrote: > > --- a/arch/xtensa/kernel/pci.c > > +++ b/arch/xtensa/kernel/pci.c > > @@ -345,7 +345,7 @@ __pci_mmap_set_pgprot(struct pci_dev *dev, struct > > vm_area_struct *vma, > >   > >   /* Set to write-through */ > >   prot = (prot &

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

On 05.04.2017 06:36, Stephen Rothwell wrote: Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/gpu/built-in.o:(__tracepoints+0x64): multiple definition of `__tracepoint_remove_device_from_group'

Re: [PATCH 2/3] arm64: allwinner: a64: add USB0 OHCI/EHCI related devicetree parts

On Wed, Apr 05, 2017 at 03:17:19PM +0800, Icenowy Zheng wrote: > > > 在 2017年04月05日 15:15, Maxime Ripard 写道: > > On Wed, Apr 05, 2017 at 02:45:17AM +0800, Icenowy Zheng wrote: > > > As we added USB0 route auto switching support for A64, add related > > > device tree parts to the A64 DTSI file

Re: linux-next: build warning after merge of the drm-misc tree

On 04/05/2017 02:41 AM, Stephen Rothwell wrote: > Hi all, > > After merging the drm-misc tree, today's linux-next build > (arm_multi_v7_defconfig) produced this warning: > > drivers/gpu/drm/bridge/synopsys/dw-hdmi.c:608:13: warning: > 'hdmi_bus_fmt_is_yuv420' defined but not used

Re: [printk] fbc14616f4: BUG:kernel_reboot-without-warning_in_test_stage

On 03/31, Ye Xiaolong wrote: >On 03/31, Sergey Senozhatsky wrote: >>On (03/31/17 11:35), Sergey Senozhatsky wrote: >>[..] >>> > [ 21.009531] VFS: Warning: trinity-c2 using old stat() call. Recompile >>> > your binary. >>> > [ 21.148898] VFS: Warning: trinity-c0 using old stat() call.

Re: [RFC PATCH] kernel: sched: Provide a pointer to the valid CPU mask

* Sebastian Andrzej Siewior wrote: > In commit 4b53a3412d66 ("sched/core: Remove the tsk_nr_cpus_allowed() > wrapper") the tsk_nr_cpus_allowed() wrapper was removed. There was not > much difference in !RT but in RT we used this to implement > migrate_disable(). Within a

Re: [RFC PATCH] raid1: reset 'bi_next' before reuse the bio

On 04/05/2017 12:17 AM, NeilBrown wrote: [snip] >> diff --git a/drivers/md/raid1.c b/drivers/md/raid1.c >> index 7d67235..0554110 100644 >> --- a/drivers/md/raid1.c >> +++ b/drivers/md/raid1.c >> @@ -1986,11 +1986,13 @@ static int fix_sync_read_error(struct r1bio *r1_bio) >> /*

[PATCH 3/4] treewide: convert PF_MEMALLOC manipulations to new helpers

We now have memalloc_noreclaim_{save,restore} helpers for robust setting and clearing of PF_MEMALLOC. Let's convert the code which was using the generic tsk_restore_flags(). No functional change. Signed-off-by: Vlastimil Babka Cc: Josef Bacik Cc: Lee Duncan

[PATCH 4/4] mtd: nand: nandsim: convert to memalloc_noreclaim_*()

Nandsim has own functions set_memalloc() and clear_memalloc() for robust setting and clearing of PF_MEMALLOC. Replace them by the new generic helpers. No functional change. Signed-off-by: Vlastimil Babka Cc: Boris Brezillon Cc: Richard

[PATCH 1/4] mm: prevent potential recursive reclaim due to clearing PF_MEMALLOC

The function __alloc_pages_direct_compact() sets PF_MEMALLOC to prevent deadlock during page migration by lock_page() (see the comment in __unmap_and_move()). Then it unconditionally clears the flag, which can clear a pre-existing PF_MEMALLOC flag and result in recursive reclaim. This was not a

[PATCH 2/4] mm: introduce memalloc_noreclaim_{save,restore}

The previous patch has shown that simply setting and clearing PF_MEMALLOC in current->flags can result in wrongly clearing a pre-existing PF_MEMALLOC flag and potentially lead to recursive reclaim. Let's introduce helpers that support proper nesting by saving the previous stat of the flag, similar

[tip:efi/urgent] efi/libstub: Skip GOP with PIXEL_BLT_ONLY format

Commit-ID: 540f4c0e894f7e46a66dfa424b16424cbdc12c38 Gitweb: http://git.kernel.org/tip/540f4c0e894f7e46a66dfa424b16424cbdc12c38 Author: Cohen, Eugene AuthorDate: Tue, 4 Apr 2017 16:27:43 +0100 Committer: Ingo Molnar CommitDate: Wed, 5 Apr 2017 09:20:18

Re: [tip:locking/core] rtmutex: Deboost before waking up the top waiter

locking/rtmutex: Fix preempt leak in __rt_mutex_futex_unlock() mark_wakeup_next_waiter() already disables preemption, doing so again leaves us with an unpaired preempt_disable(). Signed-off-by: Mike Galbraith --- kernel/locking/rtmutex.c | 10 +- 1 file changed, 5

Re: [PATCH] arm64: perf: Count EL2 events if either of kernel and hyp are not excluded

On Wed, Apr 05, 2017 at 09:29:32AM +0530, Ganapatrao Kulkarni wrote: > On Tue, Apr 4, 2017 at 5:56 PM, Will Deacon wrote: > > On Tue, Apr 04, 2017 at 05:37:10PM +0530, Ganapatrao Kulkarni wrote: > >> On Tue, Apr 4, 2017 at 4:48 PM, Will Deacon wrote: >

[PATCH v5 5/7] ARM: dtsi: axp22x: add battery power supply subnode

The X-Powers AXP22X PMIC exposes battery supply various data such as the battery status (charging, discharging, full, dead), current max limit, current current, battery capacity (in percentage), voltage max limit, current voltage, and battery capacity (in Ah). This adds the battery power supply

[PATCH v3 0/9] drm: rockchip: Fix rockchip drm unbind crash error

Verified on rk3399 chromebook kevin: 1/ stop ui && pkill -9 frecon 2/ unbind/bind drm Changes in v3: Address Sean Paul 's comments. Update commit message. Address Sean Paul 's comments. Update commit message. Address Daniel Vetter 's

[PATCH v3 6/9] drm/rockchip: Reoder drm bind/unbind sequence

Current drm bind/unbind sequence would cause some memory issues. For example we should not cleanup iommu before cleanup mode config. Reorder bind/unbind sequence, follow exynos drm. Signed-off-by: Jeffy Chen --- Changes in v3: Address Sean Paul

[PATCH v3 7/9] drm/rockchip: Shutdown all crtcs when unbinding drm

Signed-off-by: Jeffy Chen --- Changes in v3: Address Daniel Vetter 's comments. Update commit message. Changes in v2: None drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v3 1/9] drm: bridge: analogix: Detach panel when unbinding analogix dp

The panel is attached when binding analogix dp. Signed-off-by: Jeffy Chen --- Changes in v3: None Changes in v2: Fix some commit messages. drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH v3 5/9] drm/rockchip: vop: Enable pm domain before vop_initial

We're trying to access vop registers here, so need to make sure the pm domain is on. Normally it should be enabled by the bootloader, but there's no guarantee of it. And if we wanna do unbind/bind, it would also cause the device to hang. And this patch also does these: 1/ move vop_initial to the

[PATCH v3 8/9] drm/rockchip: gem: Don't alloc/free gem buf when dev_private is invalid

After unbinding drm, the userspace may still has a chance to access gem buf. Add a sanity check for a NULL dev_private to prevent that from happening. Signed-off-by: Jeffy Chen --- Changes in v3: Address Daniel Vetter 's comments. Update commit

Re: [PATCH v5 14/24] dt-bindings: mfd: syscon: Add documentation for #syscon-cells property

Hi Rob, On Saturday 01 April 2017 12:36 AM, Rob Herring wrote: > On Fri, Mar 31, 2017 at 01:58:52PM -0500, Rob Herring wrote: >> On Mon, Mar 27, 2017 at 03:15:10PM +0530, Kishon Vijay Abraham I wrote: >>> Add documentation for the optional #syscon-cells property to determine >>> the number of

[PATCH] net: davinci_mdio: add GPIO reset logic

Some boards [1] leave the PHYs at an invalid state during system power-up or reset thus causing unreliability issues with the PHY like not being detected by the mdio bus or link not functional. To work around these boards have a GPIO connected to the PHY's reset pin. Implement GPIO reset handling

Re: [PATCH v3 1/3] usb: udc: allow adding and removing the same gadget device

Hi, Alan Stern writes: >> >> allow usb_del_gadget_udc() and usb add_gadget_udc() to be called >> >> repeatedly on the same gadget->dev structure. >> >> >> >> We need to clear the gadget->dev structure so that kobject_init() >> >> doesn't complain about already

Re: [PATCH 0/2] ARM: am335x-icev2: Add ethernet support

On 04/04/17 19:01, Tony Lindgren wrote: > * Roger Quadros [170330 05:37]: >> Hi Tony & Dave, >> >> On 13/03/17 15:42, Roger Quadros wrote: >>> Hi, >>> >>> This series adds ethernet support to am335x-icev2 board. >>> >>> The ethernet PHYs on the board need an explicit GPIO reset

Re: [PATCH v1] checkpatch: test missing initial blank line in block comment

On Wed, 2017-04-05 at 08:23 +, Hugues FRUCHET wrote: > Hi Joe, thanks for reviewing, Hello Hugues > I have run the command you advice on the entire kernel code, modifying > the script to only match the newly introduced check case. > There was 14389 hits, quite huge, so I cannot 100% certify

[PATCH v1 1/1] mtd: mtk-nor: set controller's address width according to nor flash

When nor's size larger than 16MByte, nor's address width maybe set to 3 or 4, and controller should change address width according to nor's setting. Signed-off-by: Guochun Mao --- drivers/mtd/spi-nor/mtk-quadspi.c | 27 +++ 1 file changed, 27

[PATCH v6 02/23] Documentation: PCI: Guide to use PCI Endpoint Core Layer

Add Documentation to help users use endpoint library to enable endpoint mode in the PCI controller and add new PCI endpoint functions. Signed-off-by: Kishon Vijay Abraham I Acked-By: Joao Pinto Signed-off-by: Bjorn Helgaas ---

Re: in_irq_or_nmi() and RFC patch

On Mon, Apr 03, 2017 at 01:05:06PM +0100, Mel Gorman wrote: > > Started performance benchmarking: > > 163 cycles = current state > > 183 cycles = with BH disable + in_irq > > 218 cycles = with BH disable + in_irq + irqs_disabled > > > > Thus, the performance numbers unfortunately looks bad,

[PATCH v6 19/23] tools: PCI: Add a userspace tool to test PCI endpoint

Add a userspace tool to invoke the ioctls exposed by the PCI endpoint test driver to perform various PCI tests. Signed-off-by: Kishon Vijay Abraham I Signed-off-by: Bjorn Helgaas --- tools/pci/pcitest.c | 186

[PATCH v6 09/23] PCI: dwc: designware: Add EP mode support

Add endpoint mode support to designware driver. This uses the EP Core layer introduced recently to add endpoint mode support. *Any* function driver can now use this designware device in order to achieve the EP functionality. Signed-off-by: Kishon Vijay Abraham I Signed-off-by:

[PATCH v6 22/23] MAINTAINERS: Add PCI Endpoint maintainer

Add maintainer for the newly introduced PCI Endpoint framework. Signed-off-by: Kishon Vijay Abraham I Signed-off-by: Bjorn Helgaas --- MAINTAINERS | 9 + 1 file changed, 9 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index

[PATCH -mm] mm, swap: Remove unused function prototype

From: Huang Ying This is a code cleanup patch, no functionality changes. There are 2 unused function prototype in swap.h, they are removed. Signed-off-by: "Huang, Ying" Cc: Tim Chen --- include/linux/swap.h | 3 --- 1

[PATCH -mm -v2] mm, swap: Use kvzalloc to allocate some swap data structure

From: Huang Ying Now vzalloc() is used in swap code to allocate various data structures, such as swap cache, swap slots cache, cluster info, etc. Because the size may be too large on some system, so that normal kzalloc() may fail. But using kzalloc() has some advantages,

Re: [PATCH 2/3] arm64: allwinner: a64: add USB0 OHCI/EHCI related devicetree parts

On Wed, Apr 05, 2017 at 02:45:17AM +0800, Icenowy Zheng wrote: > As we added USB0 route auto switching support for A64, add related > device tree parts to the A64 DTSI file (EHCI0/OHCI0 controllers and the > pmu0 memory area for PHY). > > Signed-off-by: Icenowy Zheng > --- >

Re: [PATCH v2] loop: Add PF_LESS_THROTTLE to block/loop device thread.

On Wed 05-04-17 14:33:50, NeilBrown wrote: > > When a filesystem is mounted from a loop device, writes are > throttled by balance_dirty_pages() twice: once when writing > to the filesystem and once when the loop_handle_cmd() writes > to the backing file. This double-throttling can trigger >

Re: [PATCH v2] loop: Add PF_LESS_THROTTLE to block/loop device thread.

On Wed 05-04-17 09:19:27, Michal Hocko wrote: > On Wed 05-04-17 14:33:50, NeilBrown wrote: [...] > > diff --git a/drivers/block/loop.c b/drivers/block/loop.c > > index 0ecb6461ed81..44b3506fd086 100644 > > --- a/drivers/block/loop.c > > +++ b/drivers/block/loop.c > > @@ -852,6 +852,7 @@ static int

Re: [PATCH 2/3] arm64: allwinner: a64: add USB0 OHCI/EHCI related devicetree parts

在 2017年04月05日 15:26, Maxime Ripard 写道: On Wed, Apr 05, 2017 at 03:17:19PM +0800, Icenowy Zheng wrote: 在 2017年04月05日 15:15, Maxime Ripard 写道: On Wed, Apr 05, 2017 at 02:45:17AM +0800, Icenowy Zheng wrote: As we added USB0 route auto switching support for A64, add related device tree parts

Re: [1/2] wireless: ath9k_htc: fix NULL-deref at probe

Johan Hovold wrote: > Make sure to check the number of endpoints to avoid dereferencing a > NULL-pointer or accessing memory beyond the endpoint array should a > malicious device lack the expected endpoints. > > Fixes: 36bcce430657 ("ath9k_htc: Handle storage devices") > Cc:

[PATCH] fixup! gpu: host1x: Add IOMMU support

Signed-off-by: Mikko Perttunen --- drivers/gpu/host1x/dev.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/host1x/dev.c b/drivers/gpu/host1x/dev.c index f8fda446a6a6..f05ebb14fa63 100644 --- a/drivers/gpu/host1x/dev.c +++ b/drivers/gpu/host1x/dev.c @@

RE: [PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Wednesday, April 5, 2017 12:31 PM, Wei Wang wrote: > On Wednesday, April 5, 2017 11:54 AM, Michael S. Tsirkin wrote: > > On Wed, Apr 05, 2017 at 03:31:36AM +, Wang, Wei W wrote: > > > On Thursday, March 16, 2017 3:09 PM Wei Wang wrote: > > > > The implementation of the current

[PATCH 0/4] more robust PF_MEMALLOC handling

Hi, this series aims to unify the setting and clearing of PF_MEMALLOC, which prevents recursive reclaim. There are some places that clear the flag unconditionally from current->flags, which may result in clearing a pre-existing flag. This already resulted in a bug report that Patch 1 fixes

Re: [PATCH v2 2/4] cpufreq: imx6q: Set max suspend_freq to avoid changes during suspend

Am Dienstag, den 04.04.2017, 20:04 +0300 schrieb Leonard Crestez: > If the cpufreq driver tries to modify voltage/freq during suspend/resume > it might need to control an external PMIC via I2C or SPI but those > devices might be already suspended. This issue is likely to happen > whenever the LDOs

[tip:efi/urgent] efi/fb: Avoid reconfiguration of BAR that covers the framebuffer

Commit-ID: 5a8997342183bb792fe2c15cecf371665d784dd7 Gitweb: http://git.kernel.org/tip/5a8997342183bb792fe2c15cecf371665d784dd7 Author: Ard Biesheuvel AuthorDate: Tue, 4 Apr 2017 16:27:44 +0100 Committer: Ingo Molnar CommitDate: Wed, 5 Apr

Re: [linux-sunxi] Re: [PATCH 10/11] arm64: allwinner: a64: enable AXP803 regulators for Pine64

On Wed, Apr 05, 2017 at 02:15:43PM +0800, Icenowy Zheng wrote: > > 2017年4月5日 14:13于 Maxime Ripard 写道： > > > > On Wed, Apr 05, 2017 at 02:01:44AM +0800, Icenowy Zheng wrote: > > > Add support of AXP803 regulators in the Pine64 device tree, in order to > > >

Re: ia64 exceptions (Re: [RFC][CFT][PATCHSET v1] uaccess unification)

On Wed, Apr 05, 2017 at 06:05:08AM +0100, Al Viro wrote: > Speaking of ia64: copy_user.S contains the following oddity: > 2: > EX(.failure_in3,(p16) ld8 val1[0]=[src1],16) > (p16) ld8 val2[0]=[src2],16 > > src1 is 16-byte aligned, src2 is src1 + 8. > > What guarantees that we can't

Re: [PATCH] sched: Fix numabalancing to work with isolated cpus

On Wed, Apr 05, 2017 at 07:20:06AM +0530, Srikar Dronamraju wrote: > > > > > > To avoid this, please check for isolated cpus before choosing a target > > > cpu. > > > > > > > Hmm, would this also prevent a task running inside a cgroup that is > > allowed accessed to isolated CPUs from

Re: [linux-sunxi] Re: [PATCH v3 04/11] drm/sun4i: abstract the layer type

On Wed, Apr 05, 2017 at 01:23:15PM +0800, Icenowy Zheng wrote: > > 2017年4月5日 10:27于 Chen-Yu Tsai 写道： > > > > On Wed, Apr 5, 2017 at 3:53 AM, Icenowy Zheng wrote: > > > > > > > > > 在 2017年04月05日 03:28, Sean Paul 写道: > > >> > > >> On Thu, Mar 30, 2017 at

Re: [PATCH 2/3] arm64: allwinner: a64: add USB0 OHCI/EHCI related devicetree parts

On Wed, Apr 05, 2017 at 03:33:09PM +0800, Icenowy Zheng wrote: > > > P.S. to be compatible with older DTs, I think I should adjust > > > the phy driver, make it enable dual-route function only when > > > pmu0 is present. > > > > That, or if we're quick enough, we can still add it to 4.11. There's

Re: [PATCH v1 1/6] mm: get rid of zone_is_initialized

On Fri 31-03-17 09:39:54, Michal Hocko wrote: > Fixed screw ups during the initial patch split up as per Hillf > --- > From 8be6c5e47de66210e47710c80e72e8abd899017b Mon Sep 17 00:00:00 2001 > From: Michal Hocko > Date: Wed, 29 Mar 2017 15:11:30 +0200 > Subject: [PATCH] mm: get

[PATCH v6 08/23] Documentation: PCI: Add binding documentation for pci-test endpoint function

Add binding documentation for pci-test endpoint function that helps in adding and configuring pci-test endpoint function. Signed-off-by: Kishon Vijay Abraham I Signed-off-by: Bjorn Helgaas --- Documentation/PCI/00-INDEX | 2 ++

[PATCH v6 12/23] PCI: dwc: dra7xx: Add EP mode support

The PCIe controller integrated in dra7xx SoCs is capable of operating in endpoint mode. Add endpoint mode support to dra7xx driver. Signed-off-by: Kishon Vijay Abraham I Signed-off-by: Bjorn Helgaas --- drivers/pci/dwc/Kconfig | 31 +-

[PATCH v6 03/23] PCI: endpoint: Introduce configfs entry for configuring EP functions

Introduce a new configfs entry to configure the EP function (like configuring the standard configuration header entries) and to bind the EP function with EP controller. Signed-off-by: Kishon Vijay Abraham I Signed-off-by: Bjorn Helgaas ---

[PATCH v6 13/23] dt-bindings: PCI: dra7xx: Add DT bindings for PCI dra7xx EP mode

Add device tree binding documentation for PCI dra7xx EP mode. Acked-by: Rob Herring Signed-off-by: Kishon Vijay Abraham I Signed-off-by: Bjorn Helgaas --- Documentation/devicetree/bindings/pci/ti-pci.txt | 37 +++- 1

[PATCH v6 23/23] ARM: DRA7: clockdomain: Change the CLKTRCTRL of CM_PCIE_CLKSTCTRL to SW_WKUP

The PCIe programming sequence in TRM suggests CLKSTCTRL of PCIe should be set to SW_WKUP. There are no issues when CLKSTCTRL is set to HW_AUTO in RC mode. However in EP mode, the host system is not able to access the MEMSPACE and setting the CLKSTCTRL to SW_WKUP fixes it. Acked-by: Tony Lindgren

[PATCH v6 14/23] PCI: dwc: dra7xx: Workaround for errata id i870

According to errata i870, access to the PCIe slave port that are not 32-bit aligned will result in incorrect mapping to TLP Address and Byte enable fields. Accessing non 32-bit aligned data causes incorrect data in the target buffer if memcpy is used. Implement the workaround for this errata

[PATCH v5 4/7] ARM: dtsi: axp209: add battery power supply subnode

The X-Powers AXP209 PMIC exposes battery supply various data such as the battery status (charging, discharging, full, dead), current max limit, current current, battery capacity (in percentage), voltage max and min limits, current voltage, and battery capacity (in Ah). This adds the battery power

  1   2   3   4   5   6   7   8   9   10   >