Re: [PATCH 2/3] usb: chipidea: Hook into mux framework to toggle usb switch

On 2017-07-12 03:02, Stephen Boyd wrote: > On the db410c 96boards platform we have a TC7USB40MU on the board > to mux the D+/D- lines coming from the controller between a micro > usb "device" port and a USB hub for "host" roles[1]. During a > role switch, we need to toggle this mux to forward the

Re: [tip:smp/urgent] smp/hotplug: Replace BUG_ON and react useful

On Tue, 11 Jul 2017, Linus Torvalds wrote: > On Tue, Jul 11, 2017 at 3:39 PM, tip-bot for Thomas Gleixner > wrote: > > Rightfully-ranted-at-by: Linux Torvalds > > Insert . Google led me to this one: http://i.imgur.com/qIbRuvb.jpg Not

[PATCH] mm: Mark create_huge_pmd() inline to prevent build failure

With gcc 4.1.2: mm/memory.o: In function `create_huge_pmd': memory.c:(.text+0x93e): undefined reference to `do_huge_pmd_anonymous_page' Converting transparent_hugepage_enabled() from a macro to a static inline function reduced the ability of the compiler to remove unused code. Fix this

Re: [PATCH v4] Input: mousedev - fix implicit conversion warning

Hi Dmitry, did you get a chance to merge the sugguested revision, yet?

Re: in:imklog segfault in 4.12+git on most sparc64's

> From: Al Viro > Date: Wed, 12 Jul 2017 04:59:45 +0100 > > > Again, my apologies for format of that all - I'm almost completely > > off-net and while typing an ed script is feasible, context diff is > > too far over the top. Usimg mutt in ssh session from android is >

Re: [RFC v2 4/6] drivers: boot_constraint: Add debugfs support

On 12-07-17, 12:04, Viresh Kumar wrote: > This patch adds debugfs support for boot constraints. This is how it > looks for a "vmmc-supply" constraint for the MMC device. > > $ ls -R /sys/kernel/debug/boot_constraints/ > /sys/kernel/debug/boot_constraints/: > f723d000.dwmmc0 > >

Re: [PATCH v2] ARM: dts: imx7d-sdb: Set VLDO4 outpt to 2.8V for MIPI CSI/DSI

On Sat, Jul 01, 2017 at 01:09:11PM +0530, mindentropy wrote: > From: Gautam Bhat > > * According to mx7sabresd schematics the MIPI CSI/DSI voltage rails >should be 2.8V but the voltage provided is a maximum of 3.3V and >minimum of 1.8V. Providing such a higher

[PATCH v2 06/22] rtc: cpcap: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. version 2: - fix compilation issues by using do_div() Signed-off-by: Benjamin Gaignard

[PATCH v2 09/22] rtc: ds1511: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Alessandro Zummo

[PATCH v2 08/22] rtc: ds1305: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Alessandro Zummo

Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods

On Wed, Jul 12, 2017 at 12:15:08PM +0800, Li, Aubrey wrote: > Okay, the difference is that Mike's patch uses a very simple algorithm to > make the decision. No, the difference is that we don't end up with duplication of a metric ton of code. It uses the normal idle path, it just makes the NOHZ

Re: [PATCH] usb: dwc3: Fix the USB 3.0 hub detection bug after warm boot

Hi, On 12 July 2017 at 11:52, gustavo panizzo wrote: > The dwc3 could not release resources when the module is built-in > because this module does not have shutdown method. This causes the USB > 3.0 hub is not able to detect after warm boot. > > Original patch by Brian Kim,

Re: [PATCH RESEND] staging: sm750fb: avoid conflicting vesafb

On Tue, Jul 11, 2017 at 10:03:01PM +0100, Sudip Mukherjee wrote: > Hi Greg, > > On Fri, Jun 30, 2017 at 09:57:43PM +0100, Sudip Mukherjee wrote: > > From: Teddy Wang > > > > If vesafb is enabled in the config then /dev/fb0 is created by vesa > > and this sm750

[PATCH 2/4] arm64: dts: rockchip: add ARM Mali GPU node for RK3399 SoCs

Add Mali GPU device tree node for the RK3399 SoCs, with devfreq opp table. RK3399 and RK3399-OP1 SoCs have a different recommendation table with gpu opp. As the ARM's mali driver found on https://developer.arm.com/products/software/mali-drivers/midgard-kernel. Signed-off-by: Caesar Wang

[PATCH 0/4] arm64: dts: rockchip: support mail and IPA thermal for rk3399

This series patches supported the mail in devicetree and used the thermal IPA by default. Verified with rk3399 kevin board on my github https://github.com/Caesar-github/rockchip/commits/gru/next-stable-chromeos The kernel is based on Linus's master branch and Heiko's v4.14-armsoc-tmp/dts64

[PATCH 4/4] arm64: dts: rockchip: update the thermal zones for RK3399 SoCs

As RK3399 had used the Power allocator thermal governor by default, enabled this to manage thermals by dynamically allocating and limiting power to devices. Also, this patch supported the dynamic-power-coefficient/sustainable_power and GPU's power model for needed parameters with thermal IPA.

Re: [PATCH] mm: Mark create_huge_pmd() inline to prevent build failure

On Wed, Jul 12, 2017 at 8:57 AM, Geert Uytterhoeven wrote: > > With gcc 4.1.2: > > mm/memory.o: In function `create_huge_pmd': > memory.c:(.text+0x93e): undefined reference to > `do_huge_pmd_anonymous_page' > > Converting transparent_hugepage_enabled() from a macro

[PATCH] net: stmmac: revert "support future possible different internal phy mode"

Since internal phy-mode is reserved for non-xMII protocol we cannot use it with dwmac-sun8i. Furthermore, all DT patchs which comes with this patch were cleaned, so the current state is broken. This reverts commit 1c2fa5f84683 ("net: stmmac: support future possible different internal phy mode")

[PATCH 2/2] ftrace: silence uninitialized variable warning

My static checker complains that if "func" is NULL then "clear_filter" is uninitialized. This seems like it could be true, although it's possible something subtle is happening that I haven't seen. kernel/trace/ftrace.c:3844 match_records() error: uninitialized symbol 'clear_filter'.

Re: [PATCHSET for-4.13] cgroup: implement cgroup2 thread mode, v2

On Tue, Jul 11, 2017 at 05:12:39PM -0400, Waiman Long wrote: > On 07/11/2017 12:52 PM, Peter Zijlstra wrote: > > On Tue, Jul 11, 2017 at 10:14:42AM -0400, Waiman Long wrote: > > > >> The "join" was a special op for the children of cgroup root to join the > >> root as part of a threaded subtree.

Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335

On Tue, 2017-07-11 at 20:53 +0200, Mike Galbraith wrote: > On Tue, 2017-07-11 at 14:22 -0400, Ilia Mirkin wrote: > > > Some display stuff did change for 4.13 for GM20x+ boards. If it's not > > too much trouble, a bisect would be pretty useful. > > Vacation -> back to work happens in the very

Re: RISC-V Linux Port v6

On Wed, Jul 12, 2017 at 3:31 AM, Palmer Dabbelt wrote: > While it's only been a day since the last patch set (which might be a bit > fast), I've generally been spinning new patch sets whenever I get through my > inbox. For my other patch sets I've managed to get buried in a

Re: [PATCH] perf/core: generate overflow signal when samples are dropped (WAS: Re: [REGRESSION] perf/core: PMU interrupts dropped if we entered the kernel in the "skid" region)

* Jin, Yao wrote: > Could we provide 2 options in user space when enabling the event sampling? > > One option is for the use case like rr debugger which only cares the PMI > interrupt but doesn't care the skid. The skid samples doesn't need to be > dropped. Since

Re: [PATCH v7 06/16] lockdep: Detect and handle hist_lock ring buffer overwrite

On Wed, Jul 12, 2017 at 11:00:53AM +0900, Byungchul Park wrote: > On Tue, Jul 11, 2017 at 06:12:32PM +0200, Peter Zijlstra wrote: > > Right, like I wrote in the comment; I don't think you need quite this > > much. > > > > The problem only happens if you rewind more than MAX_XHLOCKS_NR; > >

[PATCH v2 02/22] x86: intel-mid: vrtc: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Thomas Gleixner CC:

[PATCH v2 07/22] rtc: davinci: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Alessandro Zummo

[PATCH v2 11/22] rtc: gemini: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Hans Ulli Kroll

[PATCH] rtc: Remove wrong deprecation comment

rtc_time_to_tm and rtc_tm_to_time are not deprecated and make perfect sense for RTCs that are simple 32bit counters. Signed-off-by: Alexandre Belloni --- include/linux/rtc.h | 6 -- 1 file changed, 6 deletions(-) diff --git a/include/linux/rtc.h

Re: [PATCH v3 2/3] drm/panel: Add support for s6e63j0x03 panel driver

Hi Andrzej, Could you please check this patch? Best regards, Hoegeun On 06/27/2017 11:11 AM, Hoegeun Kwon wrote: This patch adds MIPI-DSI based S6E63J0X03 AMOLED LCD panel driver which uses mipi_dsi bus to communicate with panel. The panel has 320×320 resolution in 1.63" physical panel. This

Re: [PATCH v4 03/14] drm/fb-helper: separate the fb_setcmap helper into atomic and legacy paths

On Tue, Jul 11, 2017 at 02:12:26PM +0200, Peter Rosin wrote: > On 2017-07-11 10:10, Daniel Vetter wrote: > > On Thu, Jul 06, 2017 at 02:20:37PM +0200, Peter Rosin wrote: > >> The legacy path implements setcmap in terms of crtc .gamma_set. > >> > >> The atomic path implements setcmap by directly

Re: [PATCH] pinctrl: st: constify gpio_chip structure

Hi Gustavo On 07/11/2017 08:15 PM, Gustavo A. R. Silva wrote: > This structure is only used to copy into other structure, so declare > it as const. > > This issue was detected using Coccinelle and the following semantic patch: > > @r disable optional_qualifier@ > identifier i; > position p; >

Re: [RFC v5 00/38] powerpc: Memory Protection Keys

On Tue 11-07-17 12:32:57, Ram Pai wrote: > On Tue, Jul 11, 2017 at 04:52:46PM +0200, Michal Hocko wrote: > > On Wed 05-07-17 14:21:37, Ram Pai wrote: > > > Memory protection keys enable applications to protect its > > > address space from inadvertent access or corruption from > > > itself. > > >

Re: [PATCH RESEND] HID: wacom: Remove comparison of u8 mode with zero and simplify.

On Jul 08 2017 or thereabouts, Christos Gkekas wrote: > Variable mode in method wacom_show_remote_mode() is defined as u8, thus > statement (mode >= 0) is always true and should be removed, simplifying > the logic. > > Signed-off-by: Christos Gkekas > --- Reviewed-by:

Re: [PATCH] HID: multitouch: do not blindly set EV_KEY or EV_ABS bits

On Jul 11 2017 or thereabouts, Dmitry Torokhov wrote: > Now that input core insists on having dev->absinfo when device claims to > generate EV_ABS in its dev->evbit, we should not be blindly setting that > bit. > > The code in question might have been needed before input_set_abs_params() >

Re: [PATCH v4 15/16] perf tools: add feature header record to pipe-mode

On Tue, Jul 11, 2017 at 05:32:40PM -0700, David Carrillo-Cisneros wrote: > On Tue, Jun 13, 2017 at 11:54 AM, Jiri Olsa wrote: > > On Mon, Jun 12, 2017 at 09:29:31PM -0700, David Carrillo-Cisneros wrote: > > > > SNIP > > > >> > >> void perf_event__print_totals(void); > >> diff

[PATCH v2 15/22] rtc: rs5c348: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Alessandro Zummo

[PATCH v2 19/22] rtc: sun6i: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Maxime Ripard

[PATCH v2 22/22] power: suspend test: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard Acked-by: Pavel Machek CC:

[PATCH v2 20/22] rtc: sysfs: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Alessandro Zummo

[PATCH v2 21/22] rtc: test: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. For the same reasons use set_mmss64 callback instead of set_mmss Since only set_mmss64 be will used remove

Re: [PATCH v3 1/7] libsas: Use static sas event pool to appease sas event lost

On 12/07/2017 03:06, wangyijing wrote: -unsigned long port_events_pending; -unsigned long phy_events_pending; +struct asd_sas_event port_events[PORT_POOL_SIZE]; +struct asd_sas_event phy_events[PHY_POOL_SIZE]; int error; Hi Yijing, So now we are creating a static

Re: [PATCH v2 1/7] pwm: rockchip: Add APB and function both clocks support

Hi Doug, 在 2017/7/12 1:03, Doug Anderson 写道: Hi, On Fri, Jul 7, 2017 at 9:03 PM, David Wu wrote: @@ -6,7 +6,13 @@ Required properties: "rockchip,rk3288-pwm": found on RK3288 SoC "rockchip,vop-pwm": found integrated in VOP on RK3288 SoC - reg: physical

Re: [PATCH] ARM: dts: imx: ventana: add ADV1780 analog video decoder

On Mon, Jun 19, 2017 at 08:00:10AM -0700, Tim Harvey wrote: > Enables the ADV7180 analog video decoder sensor connected to the > IMX6 IPU on various Gateworks Ventana boards. > > Signed-off-by: Tim Harvey Applied, thanks.

[PATCH] x86/kernel/cpu/amd.c: don't apply the lahf_lm workaround in a hypervisor

When I start a virtual machine, kvm complains about accesses to an unknown MSR ("vcpu0 unhandled rdmsr: 0xc001100d"). This is caused by the code in init_amd_k8 that tries to work around a BIOS bug that incorrectly sets lahf_lm. This patch disables this workaround when running in a hypervisor.

Re: [PATCH 2/4] arm64: dts: rockchip: add ARM Mali GPU node for RK3399 SoCs

Hi Caesar, Am Mittwoch, 12. Juli 2017, 14:29:28 CEST schrieb Caesar Wang: > Add Mali GPU device tree node for the RK3399 SoCs, with devfreq > opp table. > > RK3399 and RK3399-OP1 SoCs have a different recommendation table with > gpu opp. As the ARM's mali driver found on >

Re: [PATCH v10] vfio: ABI for mdev display dma-buf operation

On Wed, Jul 12, 2017 at 02:31:40AM +, Zhang, Tina wrote: > > > > -Original Message- > > From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On > > Behalf Of Daniel Vetter > > Sent: Tuesday, July 11, 2017 5:13 PM > > To: Gerd Hoffmann > > Cc:

Re: [PATCH] HID: hid-logitech-hidpp: add NULL check on devm_kmemdup() return value

On Jul 07 2017 or thereabouts, Gustavo A. R. Silva wrote: > Check return value from call to devm_kmemdup() > in order to prevent a NULL pointer dereference. > > Signed-off-by: Gustavo A. R. Silva > --- Reviewed-by: Benjamin Tissoires >

Re: [RFC v5 00/38] powerpc: Memory Protection Keys

On Wed 12-07-17 09:23:37, Michal Hocko wrote: > On Tue 11-07-17 12:32:57, Ram Pai wrote: [...] > > Ideally the MMU looks at the PTE for keys, in order to enforce > > protection. This is the case with x86 and is the case with power9 Radix > > page table. Hence the keys have to be programmed into

Re: [PATCH v4 03/14] drm/fb-helper: separate the fb_setcmap helper into atomic and legacy paths

On 2017-07-12 09:03, Daniel Vetter wrote: > On Tue, Jul 11, 2017 at 02:12:26PM +0200, Peter Rosin wrote: >> On 2017-07-11 10:10, Daniel Vetter wrote: >>> Tiny nit you might want to improve (since you need to respin for my naming >>> bikeshed of the property_replace_blob function anyway):

[PATCH v2 04/22] rtc: ab-b5ze-s3: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Alessandro Zummo

[PATCH v2 01/22] x86: rtc: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Thomas Gleixner CC:

[PATCH v2 05/22] rtc: ab8500: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. version 2: - fix compilation issues by using do_div() Signed-off-by: Benjamin Gaignard

[GIT PULL] overlayfs update for 4.13

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-linus This work from Amir introduces the inodes index feature, which provides: - hardlinks are not broken on copy up; - infrastructure for overlayfs NFS export. This also fixes constant

[PATCH 1/2] gpio: gpio-mxc: Fix: higher 16 GPIOs usable as wake source

In the function gpio_set_wake_irq(), port->irq_high is only checked for zero. As platform_get_irq() returns a value less then zero if no interrupt was found, any gpio >= 16 was handled like an irq_high interrupt was available. On iMX27 for example no high interrupt is available. This lead to the

[PATCH 0/2] gpio-mxc: Fix issue with gpios used as wake source on iMX27

The gpio-mxc driver is able to use two interrupts per gpio bank. One for the lower 16 and the other for the higher 16 gpios. The iMX27 has only one interrupt per bank. An error in the driver leads to the problem that the driver uses an invalid interrupt for the higher 16 gpios. Which in turn

[PATCH 2/2] gpio: gpio-mxc: gpio_set_wake_irq() use proper return values

Errors from enable_irq_wake() in gpio_set_wake_irq() were silently ignored. Thus led to the problem that gpio_set_wake_irq() always returned successfully, even if enable_irq_wake() returned an error. Signed-off-by: Philipp Rosenberger --- drivers/gpio/gpio-mxc.c |

[PATCH] drm: Add missing field copy in compat_drm_version

DRM_IOCTL_VERSION is supposed to update the name_len/date_len/desc_len fields to user. Fixes: 012c6741c6aa("switch compat_drm_version() to drm_ioctl_kernel()") Signed-off-by: Jeffy Chen --- drivers/gpu/drm/drm_ioc32.c | 3 +++ 1 file changed, 3 insertions(+) diff

Re: [RFC PATCH 2/4] pmbus: Add fan configuration support

On Tue, 2017-07-11 at 20:43 -0700, Guenter Roeck wrote: > On 07/11/2017 05:39 PM, Andrew Jeffery wrote: > > On Tue, 2017-07-11 at 06:40 -0700, Guenter Roeck wrote: > > > On 07/10/2017 06:56 AM, Andrew Jeffery wrote: > > > > Augment PMBus support to include control of fans via the > > > >

Re: [PATCH 0/2] perf stat: fix segfault when closing events

The perf tool segmentation fault which we were observing and this patch series intended to fix it, has been fixed due to change in default behaviour of perf stat[1][2]. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.12=0d79f8b93187c771b6971acfaba67f4e2f1e0710

Re: [REGRESSION] Touchpad failure after e7348396c6d5 ("Input: ALPS - fix V8+ protocol handling (73 03 28)")

On Tue, 11 Jul 2017 21:58:21 +0200, Paul Donohue wrote: > > On Tue, Jul 11, 2017 at 05:50:07PM +0200, Takashi Iwai wrote: > > Hi, just joining to the party in the middle, as I'm also facing the > > same problem on Dell E7270 laptop. Has this issue already been > > addressed? > > > > If not, the

[PATCH v4 1/1] usb:host:xhci support option to disable the xHCI USB2 HW LPM

XHCI specification 1.1 does not require xHCI-compliant controllers to always enable hardware USB2 LPM. However, the current xHCI driver always enable it when seeing HLC=1. This patch supports an option for users to control disabling USB2 Hardware LPM via DT/ACPI attribute. This option is needed in

[PATCH 1/2] README: revise the top level readme texts

This improves the top level README situation a little: Instead of starting with historical information like "This file was moved to..." we add a short introductory description and point the reader to the documention in a direct way, avoiding phrases like "Please notice that there are...".

Re: [PATCH] staging: ks7010: fix styling WARNINGs

On Fri, Jun 30, 2017 at 8:39 PM, Mark Rogers wrote: > Thank you for your feedback. I guess when making this patch I had the > preferred coding style in mind, but didn't ask myself if making the code > conform to it would truly improve readability. > > I agree with all of

[PATCH v2 10/22] rtc: ds1553: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Alessandro Zummo

Re: [PATCH] ARM: dts: imx: Correct B850v3 clock assignment

On Fri, Jun 30, 2017 at 03:43:37PM +0200, Romain Perier wrote: > From: Martyn Welch > > The IPU that drives HDMI must have its pre_sel set to pll2_pfd_396m > to avoid stepping on the LVDS output's toes, as the PLL can't be clocked > to the pixel clock and to the

Re: [PATCH 2/4] thermal: imx: Add support for reading OCOTP through nvmem

On Thu, Jul 06, 2017 at 04:20:42PM +0300, Leonard Crestez wrote: > On newer imx SOCs accessing OCOTP directly is wrong because the ocotp clock > needs to be enabled first. Add support for reading those same values through > the nvmem API instead. > > The older path is preserved for compatibility

[RFC v2 6/6] drivers: boot_constraint: Add constraints for OF devices

This implements the device tree dependent part of the boot constraints. The supply constraints are added automatically for the platform and AMBA devices created from DT and will be removed after the driver is registered for the devices. It is possible that some of the resources aren't available

[RFC v2 5/6] drivers: boot_constraint: Add initial DT bindings

This adds device tree bindings for boot constraints. Only power supply constraint types are supported currently. Signed-off-by: Viresh Kumar --- .../devicetree/bindings/boot-constraints.txt | 68 ++ 1 file changed, 68 insertions(+) create mode

[RFC v2 4/6] drivers: boot_constraint: Add debugfs support

This patch adds debugfs support for boot constraints. This is how it looks for a "vmmc-supply" constraint for the MMC device. $ ls -R /sys/kernel/debug/boot_constraints/ /sys/kernel/debug/boot_constraints/: f723d000.dwmmc0 /sys/kernel/debug/boot_constraints/f723d000.dwmmc0: supply-vmmc

[RFC v2 3/6] drivers: boot_constraint: Add boot_constraints_disable kernel parameter

Users must be given an option to discard any constraints set by bootloaders. For example, consider that a constraint is set for the LCD controller's supply and the LCD driver isn't loaded by the kernel. If the user doesn't need to use the LCD device, then he shouldn't be forced to honour the

Re: [sparc-next] SPARC64: Fix sun4v DMA panic

On Tue, Jul 11, 2017 at 02:34:47PM -0700, Tushar Dave wrote: > 64bit DMA only supported on sun4v equipped with ATU IOMMU HW. > 'Commit b02c2b0bfd7ae ("sparc: remove arch specific dma_supported > implementations")' introduced a code that incorrectly allow > dma_supported() to succeed for 64bit dma

[PATCH v2] fbdev: make get_fb_unmapped_area depends of !MMU

Even if CONFIG_FB_PROVIDE_GET_FB_UNMAPPED_AREA flag is selected do not compile and use get_fb_unmapped_area() if CONFIG_MMU is also set. This will avoid mmap errors when compiling multi architectures at same time. Signed-off-by: Benjamin Gaignard --- version 2: -

Re: [PATCH v4] clk: axs10x: introduce AXS10X pll driver

On Tue, 2017-07-11 at 22:25 -0700, Stephen Boyd wrote: > On 06/21, Eugeniy Paltsev wrote: > > AXS10X boards manages it's clocks using various PLLs. These PLL has > > same > > dividers and corresponding control registers mapped to different > > addresses. > > So we add one common driver for such

Re: [GIT pull] irq updates for 4.13

Hi Grygorii, On Tue, Jul 11, 2017 at 5:39 PM, Grygorii Strashko wrote: > On 07/11/2017 09:41 AM, Thomas Gleixner wrote: >> On Tue, 11 Jul 2017, Tony Lindgren wrote: >>> * Thomas Gleixner [170711 02:48]: >>> And "external abort on non-linefetch"

Re: [PATCH v8 1/5] x86: add simple udelay calibration

Hi, Lu At 05/05/2017 08:50 PM, Boris Ostrovsky wrote: On 05/05/2017 01:41 AM, Lu Baolu wrote: Hi, On 05/03/2017 06:38 AM, Boris Ostrovsky wrote: On 03/21/2017 04:01 AM, Lu Baolu wrote: Add a simple udelay calibration in x86 architecture-specific boot-time initializations. This will get a

[PATCH v2 03/22] net: broadcom: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Michael Chan

Re: [PATCH] ARM: dts: imx6q-bx50v3: disable SD card

On Fri, Jun 30, 2017 at 03:35:57PM +0200, Romain Perier wrote: > From: Ian Ray > > Default boot medium must be internal eMMC, we don't want the SDIO to be > used for these devices. This commit disables the SD card interface > for GE Healthcare Bx50v3 devices. > > Signed-off-by:

[RFC v2 2/6] drivers: boot_constraint: Add support for supply constraints

This patch adds the first constraint type: power-supply. The constraint is set by setting a voltage range for the respective regulator device, which will be honored by the regulator core even if more users turn up. Once the device is probed, the regulator is released and the constraint is

[RFC v2 1/6] drivers: Add boot constraints core

Some devices are powered ON by the bootloader before the bootloader handovers control to Linux. It maybe important for those devices to keep working until the time a Linux device driver probes the device and reconfigure its resources. A typical example of that can be the LCD controller, which is

[RFC v2 0/6] drivers: Boot Constraints core

Hi Greg and others, I am sending the V2 for this series after waiting for just 2 weeks because this one presents a clearer picture on how is this going to get used. V2 has gained updates for adding the constraints for platform and AMBA devices created from DT. Problem statement: Some devices

Re: [RFC PATCH] mm, oom: allow oom reaper to race with exit_mmap

On Tue 11-07-17 13:40:04, David Rientjes wrote: > On Tue, 11 Jul 2017, Michal Hocko wrote: > > > This? > > --- > > diff --git a/mm/oom_kill.c b/mm/oom_kill.c > > index 5dc0ff22d567..e155d1d8064f 100644 > > --- a/mm/oom_kill.c > > +++ b/mm/oom_kill.c > > @@ -470,11 +470,14 @@ static bool

Re: [PATCH] mm: Mark create_huge_pmd() inline to prevent build failure

Hi Arnd, On Wed, Jul 12, 2017 at 9:22 AM, Arnd Bergmann wrote: > On Wed, Jul 12, 2017 at 8:57 AM, Geert Uytterhoeven > wrote: >> With gcc 4.1.2: >> >> mm/memory.o: In function `create_huge_pmd': >> memory.c:(.text+0x93e): undefined reference to >>

Re: Submit of a driver for Pi433 - a radio module for Raspberry Pi

On Tue, Jul 11, 2017 at 06:02:09PM +0200, Marcus Wolf wrote: > Hi folks, > > I developed a radio shield for the 433MHz ISM band [0] for the Raspberry Pi. > This shield is called Pi433 [1]. It can be used to communicate between two > Raspberries or to control third party equipment e. g. cheap

Re: [PATCH v2] xattr: Enable security.capability in user namespaces

On Tue, 11 Jul 2017, Stefan Berger wrote: > + buflen = sizeof("@uid=") - 1 + sizeof("4294967295") - 1 + 1; Why not strlen() here? -- James Morris

Re: [PATCH] mm: Mark create_huge_pmd() inline to prevent build failure

On Wed, Jul 12, 2017 at 9:37 AM, Geert Uytterhoeven wrote: > You did mention seeing it with mips-gcc-4.1 in the thread "[RFC] minimum gcc > version for kernel: raise to gcc-4.3 or 4.6?", but didn't provide any further > details. Finally I started seeing it myself for m68k

[PATCH v2 12/22] rtc: mv: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Alessandro Zummo

[PATCH v2 13/22] rtc: omap: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. For the same reasons use set_mmss64 callback instead of set_mmss Signed-off-by: Benjamin Gaignard

Re: [PATCH] drivers/staging/wilc1000: fix sparse warning: right shift by bigger than source value

On Wed, 2017-07-12 at 08:12 +0200, Greg Kroah-Hartman wrote: > On Wed, Jul 12, 2017 at 10:23:02AM +0800, Rui Teng wrote: > > On 12/07/2017 1:04 AM, Greg Kroah-Hartman wrote: > > > On Mon, Jul 10, 2017 at 04:57:31PM +0800, Rui Teng wrote: > > > > This patch sets memory to zero directly to avoid

Re: perf report does not resolve symbols on s390x

On 07/11/2017 09:48 PM, Arnaldo Carvalho de Melo wrote: > Em Tue, Jul 11, 2017 at 04:38:28PM -0300, Arnaldo Carvalho de Melo escreveu: >> Em Tue, Jul 11, 2017 at 04:03:04PM -0300, Arnaldo Carvalho de Melo escreveu: >>> Em Fri, Jul 07, 2017 at 02:17:25PM +0200, Thomas-Mich Richter escreveu: .

Re: [PATCH v2 02/10] cpufreq: provide data for frequency-invariant load-tracking support

On Wed, Jul 12, 2017 at 09:39:17AM +0530, Viresh Kumar wrote: > Yeah, I saw your discussion with Peter on #linux-rt IRC and TBH I wasn't aware > that we are going to do fast switching that way. Just trying to get > understanding of that idea a bit.. > > So we will do fast switching from

Re: [PATCH] drivers/staging/wilc1000: fix sparse warning: right shift by bigger than source value

On Wed, Jul 12, 2017 at 10:23:02AM +0800, Rui Teng wrote: > On 12/07/2017 1:04 AM, Greg Kroah-Hartman wrote: > > On Mon, Jul 10, 2017 at 04:57:31PM +0800, Rui Teng wrote: > > > This patch sets memory to zero directly to avoid unnecessary shift and > > > bitwise operations on bool type, which can

[PATCH 1/4] dt-bindings: gpu: add the RK3399 mali for rockchip specifics

RK3399's GPU uses the quad-core Mali-T860, which is the new generation of high-end graphics processors from ARM. This patch added "rockchip,rk3399-mali" for dt-bindings, in order to support IPA of gpu thermal in later. Signed-off-by: Caesar Wang ---

[PATCH 3/4] arm64: dts: rockchip: enable the GPU for RK3399-GRU

This patch enables the gpu and adds the mali-supply power for RK3399-GRU devices. Signed-off-by: Caesar Wang --- arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi

Re: [PATCH 3/4] ARM: dts: imx6sx: Use nvmem-cells for tempmon

On Thu, Jul 06, 2017 at 04:20:43PM +0300, Leonard Crestez wrote: > On imx6sx accessing OCOTP directly is wrong because the ocotp clock > needs to be enabled first. Use the nvmem-cells binding instead. > > This requirement does not apply to older imx6qdl chips because there the > ocotp access

Re: [PATCH v1 1/1] ARM: dts: imx6: RIoTboard provide gpio-line-names

On Tue, Jun 20, 2017 at 04:28:30PM +0200, Oleksij Rempel wrote: > for each gpio controller Please write up a complete sentence. If you can explain a bit why these names are useful would be better. > > Signed-off-by: Oleksij Rempel > --- >

Re: [PATCH] MAINTAINERS: move the befs tree to kernel.org

On 07/09/2017 12:00 PM, Luis de Bethencourt wrote: Updating the location of the befs git tree and my email address. Signed-off-by: Luis de Bethencourt --- Hello, The currently listed email address isn't valid anymore due to a job change. It felt like a good moment to

[PATCH v2 18/22] rtc: stk17ta8: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Alessandro Zummo

[PATCH v2 14/22] rtc: pcap: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. version 2: - fix compilation issues by using do_div() Signed-off-by: Benjamin Gaignard

Re: [PATCH 1/2] pinctrl: stm32: select IRQ_DOMAIN_HIERARCHY instead of depends on

Hi, On 07/12/2017 01:11 AM, Masahiro Yamada wrote: Drivers that need IRQ_DOMAIN_HIERARCHY should "select" it, but drivers/pinctrl/stm32/Kconfig is the only exception that uses "depends on" syntax. This prevents GPIO drivers from select'ing IRQ_DOMAIN_HIERARCHY. For example, if I add "select

[PATCH v2 17/22] rtc: snvs: stop using rtc deprecated functions

rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they rely on 32bits variables and that will make rtc break in y2038/2016. Stop using those two functions to safer 64bits ones. Signed-off-by: Benjamin Gaignard CC: Alessandro Zummo

  1   2   3   4   5   6   7   8   9   10   >