Re: [PATCH] dt-bindings: Add silabs,si5341

2019-05-01 Thread Rob Herring
On Wed, Apr 24, 2019 at 11:02:16AM +0200, Mike Looijmans wrote: > Adds the devicetree bindings for the si5341 driver that supports the Bindings are for h/w, not a driver. Perhaps 'dt-bindings: clock: ...' to give a bit more clue what this is in the subject. > Si5341 and Si5340 chips. > >

Re: [PATCH v2 2/4] dt-bindings: memory: Add binding for NVIDIA Tegra30 External Memory Controller

2019-05-01 Thread Rob Herring
On Wed, May 1, 2019 at 7:06 PM Dmitry Osipenko wrote: > > 30.04.2019 1:05, Rob Herring пишет: > > On Sun, Apr 14, 2019 at 11:20:07PM +0300, Dmitry Osipenko wrote: > >> Add device-tree binding for NVIDIA Tegra30 External Memory Controller. > >> The binding is based on the Tegra124 EMC binding

[PATCH v3 2/2] phy: qcom: Add Qualcomm PCIe2 PHY driver

2019-05-01 Thread Bjorn Andersson
The Qualcomm PCIe2 PHY is based on design from Synopsys and found in several different platforms where the QMP PHY isn't used. Reviewed-by: Niklas Cassel Signed-off-by: Bjorn Andersson --- Changes since v2: - None drivers/phy/qualcomm/Kconfig | 8 + drivers/phy/qualcomm/Makefile

[PATCH v3 0/2] Qualcomm PCIe2 PHY

2019-05-01 Thread Bjorn Andersson
The Qualcomm PCIe2 PHY is based on design from Synopsys and found in several different platforms where the QMP PHY isn't used. Bjorn Andersson (2): dt-bindings: phy: Add binding for Qualcomm PCIe2 PHY phy: qcom: Add Qualcomm PCIe2 PHY driver .../bindings/phy/qcom-pcie2-phy.txt |

[PATCH v3 1/2] dt-bindings: phy: Add binding for Qualcomm PCIe2 PHY

2019-05-01 Thread Bjorn Andersson
The Qualcomm PCIe2 PHY is a Synopsys based PCIe PHY found in a number of Qualcomm platforms, add a binding to describe this. Signed-off-by: Bjorn Andersson --- Changes since v2: - Add #clock-cells .../bindings/phy/qcom-pcie2-phy.txt | 42 +++ 1 file changed, 42

Re: [PATCH v2 2/4] dt-bindings: memory: Add binding for NVIDIA Tegra30 External Memory Controller

2019-05-01 Thread Dmitry Osipenko
30.04.2019 1:05, Rob Herring пишет: > On Sun, Apr 14, 2019 at 11:20:07PM +0300, Dmitry Osipenko wrote: >> Add device-tree binding for NVIDIA Tegra30 External Memory Controller. >> The binding is based on the Tegra124 EMC binding since hardware is >> similar, although there are couple significant

Re: [PATCH v2] arm64: dts: ls1028a: Add USB dt nodes

2019-05-01 Thread Rob Herring
On Fri, Apr 26, 2019 at 05:54:26AM +, Ran Wang wrote: > This patch adds USB dt nodes for LS1028A. > > Signed-off-by: Ran Wang > --- > Changes in v2: > - Rename node from usb3@... to usb@... to meet DTSpec > > arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 20 > 1

[PATCH v4 12/16] PM / devfreq: tegra: Reconfigure hardware on governor's restart

2019-05-01 Thread Dmitry Osipenko
Move hardware configuration to governor's start/resume methods. This allows to re-initialize hardware counters and reconfigure cleanly if governor was stopped/paused. That is needed because we are not aware of all hardware changes that happened while governor was stopped and the paused state may

[PATCH v4 09/16] PM / devfreq: tegra: Avoid inconsistency of current frequency value

2019-05-01 Thread Dmitry Osipenko
The frequency value potentially could change in-between. It doesn't cause any real problem at all right now, but that could change in the future. Hence let's avoid the inconsistency. Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra-devfreq.c | 6 -- 1 file

[PATCH v4 03/16] PM / devfreq: tegra: Replace write memory barrier with the read barrier

2019-05-01 Thread Dmitry Osipenko
The write memory barrier isn't needed because the BUS buffer is flushed by read after write that happens after the removed wmb(), we will also use readl() instead of the relaxed version to ensure that read is indeed completed. Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko ---

[PATCH v4 06/16] PM / devfreq: tegra: Drop primary interrupt handler

2019-05-01 Thread Dmitry Osipenko
There is no real need in the primary interrupt handler, hence move everything to the secondary (threaded) handler. In a result locking is consistent now and there are no potential races with the interrupt handler because it is protected with the devfreq's mutex. Reviewed-by: Chanwoo Choi

[PATCH v4 10/16] PM / devfreq: tegra: Mark ACTMON's governor as immutable

2019-05-01 Thread Dmitry Osipenko
The ACTMON's governor supports only the Tegra's devfreq device and there is no need to use any other governor, hence let's mark Tegra governor as immutable to permanently stick it with Tegra's devfreq device. Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko --- drivers/devfreq/Kconfig

[PATCH v4 16/16] PM / devfreq: Introduce driver for NVIDIA Tegra20

2019-05-01 Thread Dmitry Osipenko
Add devfreq driver for NVIDIA Tegra20 SoC's. The driver periodically reads out Memory Controller counters and adjusts memory frequency based on the memory clients activity. Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko --- MAINTAINERS | 8 ++

[PATCH v4 08/16] PM / devfreq: tegra: Clean up driver's probe / remove

2019-05-01 Thread Dmitry Osipenko
Reset hardware, disable ACTMON clock, release OPP's and handle all possible error cases correctly, maintaining the correct tear down order. Also use devm_platform_ioremap_resource() which is now available in the kernel. Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko ---

[PATCH v4 15/16] PM / devfreq: tegra: Rename tegra-devfreq.c to tegra30-devfreq.c

2019-05-01 Thread Dmitry Osipenko
In order to reflect that driver serves NVIDIA Tegra30 and later SoC generations, let's rename the driver's source file to "tegra30-devfreq.c". This will make driver files to look more consistent after addition of a driver for Tegra20. Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko ---

[PATCH v4 00/16] NVIDIA Tegra devfreq improvements and Tegra20/30 support

2019-05-01 Thread Dmitry Osipenko
Changelog: v4: Addressed all review comments that were made by Chanwoo Choi to v3: - changed the driver removal order to match the probe exactly - added clarifying comment for 1/8 ratio to the Tegra20 driver Chanwoo, please also note that the clk patch that should fix

[PATCH v4 04/16] PM / devfreq: tegra: Don't ignore clk errors

2019-05-01 Thread Dmitry Osipenko
The clk_set_min_rate() could fail and in this case clk_set_rate() sets rate to 0, which may drop EMC rate to minimum and make machine very difficult to use. Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra-devfreq.c | 16 ++-- 1 file changed, 14

[PATCH v4 13/16] PM / devfreq: tegra: Support Tegra30

2019-05-01 Thread Dmitry Osipenko
The devfreq driver can be used on Tegra30 without any code change and it works perfectly fine, the default Tegra124 parameters are good enough for Tegra30. Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko --- drivers/devfreq/Kconfig | 4 ++-- drivers/devfreq/tegra-devfreq.c | 1

[PATCH v4 07/16] PM / devfreq: tegra: Properly disable interrupts

2019-05-01 Thread Dmitry Osipenko
There is no guarantee that interrupt handling isn't running in parallel with tegra_actmon_disable_interrupts(), hence it is necessary to protect DEV_CTRL register accesses and clear IRQ status with ACTMON's IRQ being disabled in the Interrupt Controller in order to ensure that device interrupt is

[PATCH v4 05/16] PM / devfreq: tegra: Don't set EMC clock rate to maximum on probe

2019-05-01 Thread Dmitry Osipenko
There is no real benefit from doing so, hence let's drop that rate setting for consistency. Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra-devfreq.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/devfreq/tegra-devfreq.c

[PATCH v4 11/16] PM / devfreq: tegra: Move governor registration to driver's probe

2019-05-01 Thread Dmitry Osipenko
There is no need to register the ACTMON's governor separately from the driver, hence let's move the registration into the driver's probe function for consistency and to make code cleaner a tad. Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra-devfreq.c | 43

[PATCH v4 01/16] PM / devfreq: tegra: Fix kHz to Hz conversion

2019-05-01 Thread Dmitry Osipenko
The kHz to Hz is incorrectly converted in a few places in the code, this results in a wrong frequency being calculated because devfreq core uses OPP frequencies that are given in Hz to clamp the rate, while tegra-devfreq gives to the core value in kHz and then it also expects to receive value in

[PATCH v4 02/16] PM / devfreq: tegra: Replace readl-writel with relaxed versions

2019-05-01 Thread Dmitry Osipenko
There is no need to insert memory barrier on each readl/writel invocation, hence use the relaxed versions. Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra-devfreq.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v4 14/16] PM / devfreq: tegra: Enable COMPILE_TEST for the driver

2019-05-01 Thread Dmitry Osipenko
The driver's compilation doesn't have any specific dependencies, hence the COMPILE_TEST option can be supported in Kconfig. Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko --- drivers/devfreq/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] x86/entry/64: randomize kernel stack offset upon syscall

2019-05-01 Thread Andy Lutomirski
On Wed, May 1, 2019 at 1:42 AM David Laight wrote: > > From: Reshetova, Elena > > Sent: 30 April 2019 18:51 > ... > > +unsigned char random_get_byte(void) > > +{ > > +struct rnd_buffer *buffer = _cpu_var(stack_rand_offset); > > +unsigned char res; > > + > > +if (buffer->byte_counter

Re: [PATCH v5 1/3] power_supply: Add Standard, Adaptive, and Custom charge types

2019-05-01 Thread Sebastian Reichel
Hi Nick, Yes. I merged the three patches adding the generic power supply properties, thanks. -- Sebastian On Wed, May 01, 2019 at 10:34:38AM -0600, Nick Crews wrote: > Hi Sebastian, does this look like an acceptable way of splitting up the > content into multiple commits? > > Sorry to bug, and

Re: [RFC PATCH v2 11/17] sched: Basic tracking of matching tasks

2019-05-01 Thread Tim Chen
On 4/28/19 11:15 PM, Aaron Lu wrote: > On Tue, Apr 23, 2019 at 04:18:16PM +, Vineeth Remanan Pillai wrote: >> +/* >> + * Find left-most (aka, highest priority) task matching @cookie. >> + */ >> +struct task_struct *sched_core_find(struct rq *rq, unsigned long cookie) >> +{ >> +struct

[PATCH v8 1/3] arm64: dts: fsl: librem5: Add a device tree for the Librem5 devkit

2019-05-01 Thread Angus Ainslie (Purism)
This is for the development kit board for the Librem 5. The current level of support yields a working console and is able to boot userspace from the network or eMMC. Additional subsystems that are active : - Both USB ports - SD card socket - WiFi usdhc - WWAN modem - GNSS - GPIO keys - LEDs -

[PATCH v8 3/3] dt-bindings: arm: fsl: Add the imx8mq boards

2019-05-01 Thread Angus Ainslie (Purism)
Add an entry for imx8mq based boards Signed-off-by: Angus Ainslie (Purism) Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/arm/fsl.yaml | 7 +++ 1 file changed, 7 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml

[PATCH v8 2/3] dt-bindings: Add an entry for Purism SPC

2019-05-01 Thread Angus Ainslie (Purism)
Add an entry for Purism, SPC Signed-off-by: Angus Ainslie (Purism) Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt

[PATCH v8 0/3] Add support for the Purism Librem5 devkit

2019-05-01 Thread Angus Ainslie (Purism)
The Librem5 devkit is based on the imx8mq from NXP. This is a default devicetree to boot the board to a command prompt. Changes since v7: More regulators always on for USB. Add vbus regulator. Drop vbat regulator. Replace legacy "gpio-key,wakeup" with "wakeup-source". Add vbus-supply to get rid

linux-next: manual merge of the kbuild tree with Linus' tree

2019-05-01 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the kbuild tree got a conflict in: Makefile between commit: 6f303d60534c ("gcc-9: silence 'address-of-packed-member' warning") from Linus' tree and commit: c21e4135d629 ("kbuild: re-enable int-in-bool-context warning") from the kbuild tree. I fixed

Re: [PATCH v5 0/3] Driver for UCS1002

2019-05-01 Thread Sebastian Reichel
Hi, On Tue, Apr 30, 2019 at 08:34:31PM -0700, Andrey Smirnov wrote: > This small series adds a driver for UCS1002 Programmable USB Port > Power Controller with Charger Emulation. See [page] for product page > and [datasheet] for device dataseet. Hopefully each individual patch > is self

[PATCH] misc: aspeed-lpc-ctrl: Correct return values

2019-05-01 Thread Vijay Khemka
Corrected some of return values with appropriate meanings. Signed-off-by: Vijay Khemka --- drivers/misc/aspeed-lpc-ctrl.c | 15 +++ 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/drivers/misc/aspeed-lpc-ctrl.c b/drivers/misc/aspeed-lpc-ctrl.c index

[PATCH] misc: aspeed-lpc-ctrl: make parameter optional

2019-05-01 Thread Vijay Khemka
Makiing memory-region and flash as optional parameter in device tree if user needs to use these parameter through ioctl then need to define in devicetree. Signed-off-by: Vijay Khemka --- drivers/misc/aspeed-lpc-ctrl.c | 58 +- 1 file changed, 36 insertions(+), 22

Re: linux-next: Signed-off-by missing for commit in the battery tree

2019-05-01 Thread Sebastian Reichel
Hi, On Thu, May 02, 2019 at 07:52:38AM +1000, Stephen Rothwell wrote: > Hi Sebastian, > > Commit > > 465089b4abe0 ("TODO") > > is missing a Signed-off-by from its author and committer. > > Not much of a commit message either :-) oops, thanks for the hint :) Dropped! -- Sebastian

Re: [PATCH RESEND v13 7/8] power: supply: Initial support for ROHM BD70528 PMIC charger block

2019-05-01 Thread Sebastian Reichel
Hi, On Thu, Apr 25, 2019 at 02:16:51PM +0300, Matti Vaittinen wrote: > ROHM BD70528 PMIC includes battery charger block. Support charger > staus queries and doing few basic settings like input current limit > and charging current. > > Signed-off-by: Matti Vaittinen > --- > Changelog v13: > - no

Re: [PATCH v2] misc: aspeed-lpc-ctrl: make parameter optional

2019-05-01 Thread Vijay Khemka
Let me send both patches. On 4/30/19, 11:45 PM, "Greg Kroah-Hartman" wrote: On Wed, May 01, 2019 at 05:55:07AM +, Joel Stanley wrote: > On Fri, 18 Jan 2019 at 20:12, Vijay Khemka wrote: > > > > Hi Andrew, > > Thanks for this review, I will have a follow up patch for

Re: [GIT PULL] power-supply changes for 5.1

2019-05-01 Thread pr-tracker-bot
The pull request you sent on Wed, 1 May 2019 23:26:10 +0200: > ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git > tags/for-v5.1-rc has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/600d7258316d87cf9ecd58b6fdc8a35deca0870c Thank you!

Re: kobject_init_and_add() confusion

2019-05-01 Thread Tobin C. Harding
On Wed, May 01, 2019 at 01:10:22PM +0200, Greg Kroah-Hartman wrote: > On Wed, May 01, 2019 at 09:38:03AM +1000, Tobin C. Harding wrote: > > Hi, > > > > Looks like I've created a bit of confusion trying to fix memleaks in > > calls to kobject_init_and_add(). Its spread over various patches and >

Re: memleak around kobject_init_and_add()

2019-05-01 Thread Tobin C. Harding
On Sat, Apr 27, 2019 at 09:28:09PM +0200, Greg Kroah-Hartman wrote: > On Sat, Apr 27, 2019 at 06:13:30PM +1000, Tobin C. Harding wrote: > > (Note at bottom on reasons for 'To' list 'Cc' list) > > > > Hi, > > > > kobject_init_and_add() seems to be routinely misused. A failed call to this > >

linux-next: Signed-off-by missing for commit in the battery tree

2019-05-01 Thread Stephen Rothwell
Hi Sebastian, Commit 465089b4abe0 ("TODO") is missing a Signed-off-by from its author and committer. Not much of a commit message either :-) -- Cheers, Stephen Rothwell pgpzdojyLYIxv.pgp Description: OpenPGP digital signature

Re: kobject_init_and_add() confusion

2019-05-01 Thread Tobin C. Harding
On Wed, May 01, 2019 at 09:54:16AM +0200, Rafael J. Wysocki wrote: > On Wed, May 1, 2019 at 1:38 AM Tobin C. Harding wrote: > > > > Hi, > > > > Looks like I've created a bit of confusion trying to fix memleaks in > > calls to kobject_init_and_add(). Its spread over various patches and > >

Re: next/master boot bisection: next-20190430 on beagle-xm

2019-05-01 Thread Kevin Hilman
I was able to reproduce this in next-20190430, but... I'm not sure what fixed it, but this is passing again in today's linux-next (next-20190501) Kevin

linux-next: Signed-off-by missing for commit in the parisc-hd tree

2019-05-01 Thread Stephen Rothwell
Hi all, Commit 2b731a920986 ("parisc: Update huge TLB page support to use per-pagetable spinlock") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgp91W3xNrXFC.pgp Description: OpenPGP digital signature

linux-next: Signed-off-by missing for commit in the clk tree

2019-05-01 Thread Stephen Rothwell
Hi all, Commit a048fe996b51 ("clk: imx: pllv4: add fractional-N pll support") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgpqk0z_q_X9s.pgp Description: OpenPGP digital signature

linux-next: Signed-off-by missing for commit in the kbuild tree

2019-05-01 Thread Stephen Rothwell
Hi Masahiro, Commit 7b6954a982e7 ("scripts: override locale from environment when running recordmcount.pl") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgpwqBv11FbpS.pgp Description: OpenPGP digital signature

[PATCH 2/2] bus: ti-sysc: Handle devices with no control registers

2019-05-01 Thread Tony Lindgren
Some interconnect target modules have no module control registers at all, such as d_can on am335x and am437x. The d_can register offset at 0 is CTL register with 0x401 as the default value. I guess I mistook the 0x401 value for a revision register as the value happens to look similar to what the

[PATCH 0/2] Two ti-sysc driver fixes for v5.3 merge window

2019-05-01 Thread Tony Lindgren
Hi all, Here are few fixes for the am335x d_can boot issue Sebastian reported for Beaglebone. Regards, Tony Tony Lindgren (2): ARM: dts: Configure osc clock for d_can on am335x bus: ti-sysc: Handle devices with no control registers arch/arm/boot/dts/am33xx-l4.dtsi | 14 ++

[PATCH 1/2] ARM: dts: Configure osc clock for d_can on am335x

2019-05-01 Thread Tony Lindgren
Reading the module revision register can cause an external abort on non-linefetch depending of osc clock is not already enabled. This started happening with commit 1a5cd7c23cc5 ("bus: ti-sysc: Enable all clocks directly during init to read revision") as reported by Sebastian Andrzej Siewior . The

Re: [PATCH v2] power: supply: bq27xxx_battery: Notify also about status changes

2019-05-01 Thread Sebastian Reichel
Hi, On Fri, Apr 26, 2019 at 11:59:02AM +0200, Krzysztof Kozlowski wrote: > User-space might be interested in receiving uevents when the charging > starts/stops or if conditions of battery changes (e.g. > over-temperature). Notify about changes in battery also when the flags > change, not only

Re: [PATCH v3] kernel/module: Reschedule while waiting for modules to finish loading

2019-05-01 Thread Prarit Bhargava
On 4/30/19 6:22 PM, Prarit Bhargava wrote: > On a s390 z14 LAR with 2 cpus about stalls about 3% of the time while > loading the s390_trng.ko module. > > Add a reschedule point to the loop that waits for modules to complete > loading. > > v3: cleanup Fixes line. Jessica, even with this

[GIT PULL] power-supply changes for 5.1

2019-05-01 Thread Sebastian Reichel
Hi Linus, I have two more fixes for the 5.1 cycle. One division by zero fix in a specific driver and one core workaround for bad userspace behaviour from systemd regarding uevents. IMHO this can be considered to be a userspace bug, but the debug messages are useless anyways. -- Sebastian The

Re: next/master boot bisection: next-20190430 on beagle-xm

2019-05-01 Thread Tony Lindgren
* Sebastian Andrzej Siewior [190501 21:14]: > On 2019-05-01 13:21:49 [-0700], Tony Lindgren wrote: > > Hi, > Hi, > > > OK I found two issues. It seems that d_can also needs osc clock > > on am335x. And there's no revision register for d_can.. We're now > > reading the CTL register unnecessarily.

Re: next/master boot bisection: next-20190430 on beagle-xm

2019-05-01 Thread Sebastian Andrzej Siewior
On 2019-05-01 13:21:49 [-0700], Tony Lindgren wrote: > Hi, Hi, > OK I found two issues. It seems that d_can also needs osc clock > on am335x. And there's no revision register for d_can.. We're now > reading the CTL register unnecessarily. > > Below is what I hope fixes the boot issue for you,

Re: [PATCH] platform/x86: sony-laptop: Fix unintentional fall-through

2019-05-01 Thread Kees Cook
On Wed, Apr 24, 2019 at 11:09 AM Gustavo A. R. Silva wrote: > > It seems that the default case should return AE_CTRL_TERMINATE, instead > of falling through to case ACPI_RESOURCE_TYPE_END_TAG and returning AE_OK; > otherwise the line of code at the end of the function is unreachable and > makes

Re: [RESEND PATCH v6 08/12] x86/fsgsbase/64: Use the per-CPU base as GSBASE at the paranoid_entry

2019-05-01 Thread Bae, Chang Seok
> On May 1, 2019, at 13:25, Andy Lutomirski wrote: > > > >> On May 1, 2019, at 1:21 PM, Bae, Chang Seok wrote: >> >> On May 1, 2019, at 11:01, Bae, Chang Seok wrote: On May 1, 2019, at 10:40, Andy Lutomirski wrote: On Wed, May 1, 2019 at 6:52 AM Bae, Chang Seok

Re: [PATCH V2] clk: imx: pllv4: add fractional-N pll support

2019-05-01 Thread Stephen Boyd
The Content-transfer-encoding header is still base64. I guess it can't be fixed. Quoting Anson Huang (2019-04-29 17:57:22) > The pllv4 supports fractional-N function, the formula is: > > PLL output freq = input * (mult + num/denom), > > This patch adds fractional-N function support, including >

Re: Strange issues with epoll since 5.0

2019-05-01 Thread Deepa Dinamani
On Wed, May 1, 2019 at 1:48 PM Eric Wong wrote: > > Deepa Dinamani wrote: > > So here is my analysis: > > > > > So the 854a6ed56839a40f6 seems to be better than the original code in > > that it detects the signal. > > OTOH, does matter to anybody that a signal is detected slightly > sooner than

Re: Strange issues with epoll since 5.0

2019-05-01 Thread Eric Wong
Deepa Dinamani wrote: > So here is my analysis: > So the 854a6ed56839a40f6 seems to be better than the original code in > that it detects the signal. OTOH, does matter to anybody that a signal is detected slightly sooner than it would've been, otherwise? > But, the problem is that it doesn't

Re: DISCONTIGMEM is deprecated

2019-05-01 Thread Mike Rapoport
On Sun, Apr 28, 2019 at 01:11:07AM -0700, Christoph Hellwig wrote: > On Wed, Apr 24, 2019 at 02:33:53PM +0300, Mike Rapoport wrote: > > On Tue, Apr 23, 2019 at 12:13:54AM -0700, Christoph Hellwig wrote: > > > On Sun, Apr 21, 2019 at 10:16:04PM +0100, Mel Gorman wrote: > > > > 32-bit NUMA systems

Re: [GIT PULL] ACPI fix for v5.1-rc8

2019-05-01 Thread pr-tracker-bot
The pull request you sent on Wed, 1 May 2019 10:39:19 +0200: > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git acpi-5.1-rc8 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/fb0af61d3afe0b8f8b7bd2ed7c9fcaae670ced4a Thank you! -- Deet-doot-dot, I am a

[PATCH] ceph: remove ceph_get_direct_page_vector

2019-05-01 Thread Christoph Hellwig
This function is entirely unused. Signed-off-by: Christoph Hellwig --- include/linux/ceph/libceph.h | 4 net/ceph/pagevec.c | 33 - 2 files changed, 37 deletions(-) diff --git a/include/linux/ceph/libceph.h b/include/linux/ceph/libceph.h index

Re: [PATCH] platform/x86: sony-laptop: Fix unintentional fall-through

2019-05-01 Thread Gustavo A. R. Silva
Hi all, Friendly ping: Who can take this? Thanks -- Gustavo On 4/24/19 1:09 PM, Gustavo A. R. Silva wrote: > It seems that the default case should return AE_CTRL_TERMINATE, instead > of falling through to case ACPI_RESOURCE_TYPE_END_TAG and returning AE_OK; > otherwise the line of code at the

Re: mlx5_core failed to load with 5.1.0-rc7-next-20190430+

2019-05-01 Thread Saeed Mahameed
On Wed, 2019-05-01 at 10:24 -0400, Qian Cai wrote: > On Tue, 2019-04-30 at 20:26 -0700, Saeed Mahameed wrote: > > On Tue, Apr 30, 2019 at 8:00 PM Saeed Mahameed > > wrote: > > > On Tue, Apr 30, 2019 at 6:23 PM Qian Cai wrote: > > > > Reverted the commit b169e64a2444 ("net/mlx5: Geneve, Add flow

[GIT PULL] updates to soc/fsl drivers for v5.2

2019-05-01 Thread Li Yang
Hi arm-soc maintainers, Please help to merge for-next patches for the upcoming merge window. Thanks Regards, Leo The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b: Linux 5.1-rc1 (2019-03-17 14:22:26 -0700) are available in the Git repository at:

[GIT PULL] fixes to soc/fsl drivers for v5.1

2019-05-01 Thread Li Yang
Hi arm-soc maintainers, Please help to merge the following fix for soc/fsl drivers. Thanks, Leo The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b: Linux 5.1-rc1 (2019-03-17 14:22:26 -0700) are available in the Git repository at:

[PATCH v2 4/4] ftrace: Add an option for tracing console latencies

2019-05-01 Thread Viktor Rosendahl
This new option CONFIG_TRACE_CONSOLE_LATENCY will enable the latency tracers to trace the console latencies. Previously this has always been implicitely disabled. I guess this is because they are considered to be well known and unavoidable. However, for some organizations it may nevertheless be

[PATCH v2 3/4] Add the latency-collector to tools

2019-05-01 Thread Viktor Rosendahl
This is a tool that is intended to work around the fact that the preemptoff, irqsoff, and preemptirqsoff tracers only work in overwrite mode. The idea is to act randomly in such a way that we do not systematically lose any latencies, so that if enough testing is done, all latencies will be

[PATCH v2 2/4] preemptirq_delay_test: Add the burst feature and a sysfs trigger

2019-05-01 Thread Viktor Rosendahl
This burst feature enables the user to generate a burst of preempt/irqsoff latencies. This makes it possible to test whether we are able to detect latencies that systematically occur very close to each other. The maximum burst size is 10. We also create 10 identical test functions, so that we get

[PATCH v2 0/4] Some new features for the preempt/irqsoff tracers

2019-05-01 Thread Viktor Rosendahl
Hello all, Changes in v2: - I have tried to improve some of the commit messages by adding additional explanations. - [PATCH 2/4]: We use burst size checking instead of the confusing modulo game. The example given in the Kconfig file is corrected and extended. I was not able to find a way to

[PATCH v2 1/4] ftrace: Implement fs notification for preempt/irqsoff tracers

2019-05-01 Thread Viktor Rosendahl
This patch implements the feature that the trace file, e.g. /sys/kernel/debug/tracing/trace will receive notifications through the fsnotify framework when a new trace is available. This makes it possible to implement a user space program that can, with equal probability, obtain traces of

[PATCH v2] mmc: usdhi6rol0: mark expected switch fall-throughs

2019-05-01 Thread Gustavo A. R. Silva
In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. This patch fixes the following warnings: In file included from drivers/mmc/host/usdhi6rol0.c:9: drivers/mmc/host/usdhi6rol0.c: In function ‘usdhi6_timeout_work’:

[RFC][PATCH 0/2] ftrace/x86: Allow for breakpoint handlers to emulate call functions

2019-05-01 Thread Steven Rostedt
I split Peter's patch up into two. One that implements the gap in the breakpoint handler, and supplies the helper functions. And the other one that adds ftrace as the user of that code. Peter, I need an offical "Signed-off-by" from you for these. I'm currently running them through my full test

[RFC][PATCH 1/2] x86: Allow breakpoints to emulate call functions

2019-05-01 Thread Steven Rostedt
From: Peter Zijlstra In order to allow breakpoints to emulate call functions, they need to push the return address onto the stack. But because the breakpoint exception frame is added to the stack when the breakpoint is hit, there's no room to add the address onto the stack and return to the

[RFC][PATCH 2/2] ftrace/x86: Emulate call function while updating in breakpoint handler

2019-05-01 Thread Steven Rostedt
From: Peter Zijlstra Nicolai Stange discovered[1] that if live kernel patching is enabled, and the function tracer started tracing the same function that was patched, the conversion of the fentry call site during the translation of going from calling the live kernel patch trampoline to the

Re: [PATCH] rtc: st-lpc: remove unnecessary check

2019-05-01 Thread Alexandre Belloni
On 01/05/2019 17:11:44+, Trent Piepho wrote: > > I can't believe you can possibly have more than one second between the > > check in the core and the check in the driver, it doesn't make much > > sense to check, even in the current state of the core. > > It's certainly possible to have

Re: [PATCH] PCI/LINK: Account for BW notification in vector calculation

2019-05-01 Thread Bjorn Helgaas
On Mon, Apr 22, 2019 at 04:43:30PM -0600, Alex Williamson wrote: > On systems that don't support any PCIe services other than bandwidth > notification, pcie_message_numbers() can return zero vectors, causing > the vector reallocation in pcie_port_enable_irq_vec() to retry with > zero, which fails,

Re: [PATCH] mmc: usdhi6rol0: mark expected switch fall-throughs

2019-05-01 Thread Gustavo A. R. Silva
Hi Ulf, Sorry for the late reply, please see my comments below... On 3/21/19 5:46 AM, Ulf Hansson wrote: > On Wed, 20 Mar 2019 at 21:02, Gustavo A. R. Silva > wrote: >> >> In preparation to enabling -Wimplicit-fallthrough, mark switch >> cases where we are expecting to fall through. >> >> This

Re: [RFC V2 09/11] dt-bindings: interconnect: Add header for interconnect node

2019-05-01 Thread Rob Herring
On Tue, Apr 30, 2019 at 04:51:03PM +0800, Henry Chen wrote: > Add header file for mt8183 interconnect node that could be shared between > the interconeect provider driver and Device Tree source files. > > Signed-off-by: Henry Chen > --- > include/dt-bindings/interconnect/mtk,mt8183.h | 18

Re: [RFC V2 08/11] dt-bindings: interconnect: add MT8183 interconnect dt-bindings

2019-05-01 Thread Rob Herring
On Tue, Apr 30, 2019 at 04:51:02PM +0800, Henry Chen wrote: > Add interconnect provider dt-bindings for MT8183. > > Signed-off-by: Henry Chen > --- > .../bindings/interconnect/mtk,mt8183.txt | 24 > ++ > 1 file changed, 24 insertions(+) > create mode 100644 >

Re: Question about sched_setaffinity()

2019-05-01 Thread Paul E. McKenney
On Wed, May 01, 2019 at 03:16:55PM -0400, Steven Rostedt wrote: > On Wed, 1 May 2019 12:12:13 -0700 > "Paul E. McKenney" wrote: > > > > OK, what I did was to apply the patch at the end of this email to -rcu > > branch dev, then run rcutorture as follows: > > > > nohup

Re: perf build broken in 5.1-rc7

2019-05-01 Thread Arnaldo Carvalho de Melo
Em Wed, May 01, 2019 at 11:20:02PM +0300, Thomas Backlund escreveu: > > Den 01-05-2019 kl. 20:31, skrev Arnaldo Carvalho de Melo: > > Em Wed, May 01, 2019 at 05:09:59PM +0300, Thomas Backlund escreveu: > > > Den 01-05-2019 kl. 16:07, skrev Arnaldo Carvalho de Melo: > > > > Em Tue, Apr 30, 2019 at

Re: [RFC V2 02/11] dt-bindings: soc: Add opp table on scpsys bindings

2019-05-01 Thread Rob Herring
On Tue, 30 Apr 2019 16:50:56 +0800, Henry Chen wrote: > Add opp table on scpsys dt-bindings for Mediatek SoC. > > Signed-off-by: Henry Chen > --- > .../devicetree/bindings/soc/mediatek/scpsys.txt| 42 > ++ > 1 file changed, 42 insertions(+) > Reviewed-by: Rob Herring

Re: [RESEND PATCH v6 08/12] x86/fsgsbase/64: Use the per-CPU base as GSBASE at the paranoid_entry

2019-05-01 Thread Andy Lutomirski
> On May 1, 2019, at 1:21 PM, Bae, Chang Seok wrote: > > >>> On May 1, 2019, at 11:01, Bae, Chang Seok wrote: >>> >>> On May 1, 2019, at 10:40, Andy Lutomirski wrote: >>> >>> On Wed, May 1, 2019 at 6:52 AM Bae, Chang Seok >>> wrote: > On Apr 5, 2019, at 06:50, Andy

Re: [RFC V2 01/11] dt-bindings: soc: Add dvfsrc driver bindings

2019-05-01 Thread Rob Herring
On Tue, 30 Apr 2019 16:50:55 +0800, Henry Chen wrote: > Document the binding for enabling dvfsrc on MediaTek SoC. > > Signed-off-by: Henry Chen > --- > .../devicetree/bindings/soc/mediatek/dvfsrc.txt| 23 > ++ > include/dt-bindings/soc/mtk,dvfsrc.h | 14

Re: next/master boot bisection: next-20190430 on beagle-xm

2019-05-01 Thread Tony Lindgren
Hi, * Sebastian Andrzej Siewior [190501 19:03]: > On 2019-05-01 10:44:31 [-0700], Tony Lindgren wrote: > > Hmm so I tried without "earlycon" in command line thinking it might be > > happening with just "earlyprintk" but still no luck. > > > > BTW, in general you might want to update your kernel

Re: [PATCH v2 2/4] dt-bindings: doc: Reflect new NVMEM of_get_mac_address behaviour

2019-05-01 Thread Rob Herring
On Sun, Apr 28, 2019 at 06:53:26PM +0200, Andrew Lunn wrote: > On Sun, Apr 28, 2019 at 02:53:20PM +0200, Petr Štetiar wrote: > > As of_get_mac_address now supports NVMEM under the hood, we need to update > > the bindings documentation with the new nvmem-cell* properties, which would > > mean copy

Re: [PATCH] clk: actions: Use the correct style for SPDX License Identifier

2019-05-01 Thread Andreas Färber
+ linux-actions Am 01.05.19 um 09:07 schrieb Nishad Kamdar: > This patch corrects the SPDX License Identifier style > in header files related to Clock Drivers for Actions Semi Socs. > For C header files Documentation/process/license-rules.rst > mandates C-like comments (opposed to C source files

Re: perf build broken in 5.1-rc7

2019-05-01 Thread Thomas Backlund
Den 01-05-2019 kl. 20:31, skrev Arnaldo Carvalho de Melo: Em Wed, May 01, 2019 at 05:09:59PM +0300, Thomas Backlund escreveu: Den 01-05-2019 kl. 16:07, skrev Arnaldo Carvalho de Melo: Em Tue, Apr 30, 2019 at 04:31:14PM +0300, Thomas Backlund escreveu: Can you check the output for

Re: [PATCH V2 4/4] dt-bindings: watchdog: remove i.MX system controller watchdog

2019-05-01 Thread Rob Herring
On Sun, Apr 28, 2019 at 03:27:17AM +, Anson Huang wrote: > i.MX system controller watchdog now depends on SCU driver, so it > needs to be subnode of SCU node in DT, binding doc is moved to > fsl,scu.txt as well. > > Signed-off-by: Anson Huang > --- > New patch. > --- >

Re: [PATCH V2 1/4] dt-bindings: fsl: scu: add watchdog binding

2019-05-01 Thread Rob Herring
On Sun, Apr 28, 2019 at 03:27:00AM +, Anson Huang wrote: > i.MX system controller watchdog has pretimeout function which > depends on i.MX SCU driver, so watchdog DT node needs to be > subnode of SCU, this patch adds i.MX system controller watchdog > binding to SCU binding doc. > >

Re: [PATCH v2 10/15] dt-bindings: dma: imx-sdma: add i.mx6ul/6sx compatible name

2019-05-01 Thread Rob Herring
On Fri, 26 Apr 2019 08:06:03 +, Robin Gong wrote: > Add i.mx6ul and i.mx6sx compatible name. > > Signed-off-by: Robin Gong > --- > Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt | 2 ++ > 1 file changed, 2 insertions(+) > Reviewed-by: Rob Herring

Re: [PATCH v2 08/15] dt-bindings: spi: imx: add i.mx6ul to state errata fixed

2019-05-01 Thread Rob Herring
On Fri, Apr 26, 2019 at 08:05:51AM +, Robin Gong wrote: > ERR009165 fixed from i.mx6ul, add it to show the errata fixed. > > Signed-off-by: Robin Gong > --- > Documentation/devicetree/bindings/spi/fsl-imx-cspi.txt | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git

[PATCH 1/2] arm64: fix syscall_fn_t type

2019-05-01 Thread Sami Tolvanen
Use const struct pt_regs * instead of struct pt_regs * as the argument type to fix indirect call type mismatches with Control-Flow Integrity checking. Signed-off-by: Sami Tolvanen --- arch/arm64/include/asm/syscall.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 2/2] arm64: use the correct function type in SYSCALL_DEFINE0

2019-05-01 Thread Sami Tolvanen
Although a syscall defined using SYSCALL_DEFINE0 doesn't accept parameters, use the correct function type to avoid indirect call type mismatches with Control-Flow Integrity checking. Signed-off-by: Sami Tolvanen --- arch/arm64/include/asm/syscall_wrapper.h | 18 +- 1 file

[PATCH 0/2] fix function type mismatches in syscall wrappers

2019-05-01 Thread Sami Tolvanen
These patches fix type mismatches in arm64 syscall wrapper definitions, which trip indirect call checks with Control-Flow Integrity. Sami Tolvanen (2): arm64: fix syscall_fn_t type arm64: use the correct function type in SYSCALL_DEFINE0 arch/arm64/include/asm/syscall.h | 2 +-

Re: [PATCH v2 1/2] dt-bindings: adc: mt8183: add binding document

2019-05-01 Thread Rob Herring
On Wed, 24 Apr 2019 09:11:11 +0800, Zhiyong Tao wrote: > The commit adds mt8183 compatible node in binding document. > > Signed-off-by: Zhiyong Tao > --- > Documentation/devicetree/bindings/iio/adc/mt6577_auxadc.txt | 1 + > 1 file changed, 1 insertion(+) > Reviewed-by: Rob Herring

Re: [PATCH v2 1/3] dt-bindings: pwm: Update bindings for the Meson G12A Family

2019-05-01 Thread Rob Herring
On Tue, 23 Apr 2019 15:36:44 +0200, Neil Armstrong wrote: > Update the doc to explicitly support Meson G12A Family. > The 2 first (A & B) AO PWM uses different clock source than the last 2 > (C & D) AO PWM modules, thus we need to differentiate them. > > Signed-off-by: Neil Armstrong > --- >

[PATCH 1/3] arm: remove ARCH_SELECT_MEMORY_MODEL

2019-05-01 Thread Mike Rapoport
The ARCH_SELECT_MEMORY_MODEL in arch/arm/Kconfig is enabled only when ARCH_SPARSEMEM_ENABLE=y. But in this case, ARCH_SPARSEMEM_DEFAULT is also enabled and this in turn enables SPARSEMEM_MANUAL. Since there is no definition of ARCH_FLATMEM_ENABLE in arch/arm/Kconfig, SPARSEMEM_MANUAL is the only

<    1   2   3   4   5   >