[PATCH] regulator: max77802-regulator: fix indentation in if statement

From: Colin Ian King There are several lines in an if statement that are not indented correctly. Fix these by removing the tabs. Signed-off-by: Colin Ian King --- drivers/regulator/max77802-regulator.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [PATCH v3 02/11] dt-bindings: power: supply: add DT bindings for max77650

On Tue 2019-02-12 14:28:10, Bartosz Golaszewski wrote: > wt., 12 lut 2019 o 12:54 Pavel Machek napisał(a): > > > > Hi! > > > > > diff --git > > > a/Documentation/devicetree/bindings/power/supply/max77650-charger.txt > > > b/Documentation/devicetree/bindings/power/supply/max77650-charger.txt > >

Re: [PATCH v3 10/11] input: max77650: add onkey support

On Tue 2019-02-12 14:29:49, Bartosz Golaszewski wrote: > wt., 12 lut 2019 o 13:17 Pavel Machek napisał(a): > > > > Hi! > > > > > + error = device_property_read_string(dev, > > > + "maxim,onkey-mode", _prop); > > > + if (error) > > > +

Re: [PATCH RESEND] initramfs: cleanup incomplete rootfs

On Tue, Feb 12, 2019 at 2:12 PM David Engraf wrote: > On 12.02.19 at 11:43, Andy Shevchenko wrote: > > On Mon, Feb 11, 2019 at 2:40 PM David Engraf wrote: > >> On 11.02.19 at 12:40, Andy Shevchenko wrote: > >> Ok got it. When the memory behind the actual file size is clear (0x0) > >> the

Re: [PATCH v3 08/10] x86/setcpuid: Add kernel option setcpuid

On Tue, 12 Feb 2019, Peter Zijlstra wrote: > On Mon, Feb 11, 2019 at 11:16:43AM -0800, Fenghua Yu wrote: > > 4. The feature can be disabled by kernel option > > "clearcpuid=split_lock_detection" during early boot time. > > IFF clearcpuid lives, it should also employ CPUID faulting and clear it >

[PATCH] drm/nouveau/falcon: fix a few indentation issues

From: Colin Ian King There are a few statements that are indented incorrectly. Fix these. Signed-off-by: Colin Ian King --- drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/falcon/msgqueue.c

Re: [PATCH] xarray: Document erasing entries during iteration

On Tue, Feb 12, 2019 at 06:29:58PM +1100, Tobin C. Harding wrote: > I had my first go using the XArray today and during that I wondered if > it was safe to remove items during iteration. Conceptually it seems > fine and it seemed to work just fine in code - is this something people > should not

[PATCH 5/7] clk: stm32mp1: fix HSI divider flag

From: Gabriel Fernandez The divider of HSI (clk-hsi-div) is power of two divider. Signed-off-by: Gabriel Fernandez --- drivers/clk/clk-stm32mp1.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/clk/clk-stm32mp1.c b/drivers/clk/clk-stm32mp1.c index

Re: [PATCH v10 2/3] x86,/proc/pid/status: Add AVX-512 usage elapsed time

On 2019/2/12 21:24, Thomas Gleixner wrote: > On Tue, 12 Feb 2019, Li, Aubrey wrote: > >> On 2019/2/12 21:03, Thomas Gleixner wrote: >> I didn't include the first patch, because I saw it's already in tip >> tree. Did you use tip tree? > > Yes, that's my bad, forgot to switch branches. That still

[PATCH 1/7] clk: stm32mp1: parent clocks update

From: Gabriel Fernandez This patch updates parent clocks for axi, fdcan, sai and adc12. Signed-off-by: Gabriel Fernandez --- drivers/clk/clk-stm32mp1.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/clk/clk-stm32mp1.c b/drivers/clk/clk-stm32mp1.c index

[PATCH 6/7] clk: stm32mp1: remove unnecessary CLK_DIVIDER_ALLOW_ZERO flag

From: Gabriel Fernandez This patch removes unnecessary CLK_DIVIDER_ALLOW_ZERO flag of ethptp_k and ck_hse_rtc clocks. Signed-off-by: Gabriel Fernandez --- drivers/clk/clk-stm32mp1.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/clk/clk-stm32mp1.c

[PATCH 4/7] clk: stm32mp1: fix mcu divider table

From: Gabriel Fernandez index 8: ck_mcuss divided by 256 (not 512) Signed-off-by: Gabriel Fernandez --- drivers/clk/clk-stm32mp1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/clk/clk-stm32mp1.c b/drivers/clk/clk-stm32mp1.c index 5b30e4eeca2c..385dac678a7f

[PATCH 2/7] clk: stm32mp1: add CLK_SET_RATE_NO_REPARENT to Kernel clocks

From: Gabriel Fernandez Don't change parent during a set rate for Kernel clocks. Signed-off-by: Gabriel Fernandez --- drivers/clk/clk-stm32mp1.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/drivers/clk/clk-stm32mp1.c b/drivers/clk/clk-stm32mp1.c index

[PATCH 3/7] clk: stm32mp1: set ck_csi as critical clock

From: Gabriel Fernandez ck_csi is used for IO compensation so it should be considered as "always-on" and kept on. Signed-off-by: Gabriel Fernandez --- drivers/clk/clk-stm32mp1.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/clk/clk-stm32mp1.c

[PATCH 7/7] clk: stm32mp1: fix bit width of hse_rtc divider

From: Gabriel Fernandez This patch fixes the bit width of the hse rtc divider. Signed-off-by: Gabriel Fernandez --- drivers/clk/clk-stm32mp1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/clk/clk-stm32mp1.c b/drivers/clk/clk-stm32mp1.c index

[PATCH 0/7] update STM32MP1 clocks

From: Gabriel Fernandez This patch-set fixes minor corrections (fixes and documentation alignment) - add missing parent clocks - don't change parent on set rate for kernel clocks - set ck_csi clock as critical - fix divider configuration Gabriel Fernandez (7): clk: stm32mp1: parent clocks

Re: [PATCH v2 6/6] RISC-V: Implement keepinitrd kernel parameter

On Tue, Feb 12, 2019 at 4:07 PM Andreas Schwab wrote: > > On Feb 12 2019, Anup Patel wrote: > > > So in case of initrd we might not want to free-up the RAM but > > we can certainly free-up in case of initramfs. > > But the default should be keepinitrd=0, shoudn't it? Actually, it is

Re: [PATCH v3 07/11] power: supply: max77650: add support for battery charger

On Tue 2019-02-12 14:31:52, Bartosz Golaszewski wrote: > wt., 12 lut 2019 o 13:07 Pavel Machek napisał(a): > > > > Hi! > > > > > +#define MAX77650_CHARGER_ENABLED BIT(0) > > > +#define MAX77650_CHARGER_DISABLED0x00 > > > +#define MAX77650_CHARGER_CHG_EN_MASK BIT(0)

Re: [PATCH v10 2/3] x86,/proc/pid/status: Add AVX-512 usage elapsed time

On Tue, 12 Feb 2019, Li, Aubrey wrote: > On 2019/2/12 21:24, Thomas Gleixner wrote: > > And please take your time and do not shoot out half baken patch series > > every 5 minutes. > > > Sorry for the trouble, just want to solve the problem before your eyes move > away from this thread. You

Re: [PATCH net-next v4 2/9] switchdev: Add SWITCHDEV_PORT_ATTR_SET, SWITCHDEV_PORT_ATTR_GET

On Mon, Feb 11, 2019 at 11:09:54AM -0800, Florian Fainelli wrote: > In preparation for allowing switchdev enabled drivers to veto specific > attribute settings from within the context of the caller, introduce a > new switchdev notifier type for port attributes. > > Suggested-by: Ido Schimmel >

Re: [PATCH v2 13/28] thunderbolt: Add helper function to iterate from one port to another

On Mon, Feb 11, 2019 at 11:54:36AM +0200, Mika Westerberg wrote: > On Mon, Feb 11, 2019 at 07:16:00AM +0100, Lukas Wunner wrote: > > On Wed, Feb 06, 2019 at 04:17:23PM +0300, Mika Westerberg wrote: > > > +/** > > > + * tb_port_get_next() - Return next port for given port > > > + * @start: Start

Re: [RFC PATCH v2 0/4] mm, memory_hotplug: allocate memmap from hotadded memory

On Tue, Feb 12, 2019 at 01:21:38PM +, Shameerali Kolothum Thodi wrote: > > Hi Oscar, > > > > I ran tests on one of our arm64 machines. Particular machine doesn't > > actually > > have > > the mechanics for hotplug, so was all 'faked', but software wise it's all > > the > > same. > > > >

[PATCH] parisc: use memblock_alloc() instead of custom get_memblock()

The get_memblock() function implements custom bottom-up memblock allocator. Setting 'memblock_bottom_up = true' before any memblock allocation is done allows replacing get_memblock() calls with memblock_alloc(). Signed-off-by: Mike Rapoport --- arch/parisc/mm/init.c | 52

[PATCH v3 0/6] Fixmap support and MM cleanups

From: Anup Patel This patchset does: 1. Moves MM related code from kernel/setup.c to mm/init.c 2. Implements compile-time fixed mappings Using fixed mappings available, we can now get earlyprints even without SBI calls. For example, we can use kernel parameter

[PATCH v3 1/6] RISC-V: Move free_initrd_mem() to kernel/setup.c

We move free_initrd_mem() to kernel/setup.c so that all initrd related functions are in one place. Signed-off-by: Anup Patel Reviewed-by: Christoph Hellwig --- arch/riscv/kernel/setup.c | 4 arch/riscv/mm/init.c | 7 --- 2 files changed, 4 insertions(+), 7 deletions(-) diff

[PATCH v3 3/6] RISC-V: Move setup_bootmem() to mm/init.c

The setup_bootmem() mainly populates memblocks and does early memory reservations. The right location for this function is mm/init.c. Signed-off-by: Anup Patel Reviewed-by: Christoph Hellwig --- arch/riscv/include/asm/pgtable.h | 1 + arch/riscv/kernel/setup.c| 48

[PATCH v3 5/6] RISC-V: Implement compile-time fixed mappings

This patch implements compile-time virtual to physical mappings. These compile-time fixed mappings can be used by earlycon, ACPI, and early ioremap for creating fixed mappings when FIX_EARLYCON_MEM=y. To start with, we have enabled compile-time fixed mappings for earlycon. Signed-off-by: Anup

[PATCH v3 4/6] RISC-V: Move setup_vm() to mm/init.c

The setup_vm() is responsible for setting up initial page table hence should be placed in mm/init.c. Signed-off-by: Anup Patel Reviewed-by: Christoph Hellwig --- arch/riscv/kernel/setup.c | 49 --- arch/riscv/mm/init.c | 49

[PATCH v3 2/6] RISC-V: Setup init_mm before parse_early_param()

We should setup init_mm before doing parse_early_param() in setup_arch() to be consistent with setup_arch() of other architectures such as x86, ARM, and ARM64. Signed-off-by: Anup Patel Reviewed-by: Christoph Hellwig --- arch/riscv/kernel/setup.c | 9 - 1 file changed, 4 insertions(+),

Re: [PATCH 3/3] mm/mincore: provide mapped status when cached status is not allowed

On Tue 12-02-19 14:09:03, Jiri Kosina wrote: > On Tue, 12 Feb 2019, Michal Hocko wrote: > > > I would go with patch 1 for 5.1. Patches 2 still sounds controversial or > > incomplete to me. > > Is it because of the disagreement what 'non-blocking' really means, or do > you see something else

[PATCH v3 6/6] RISC-V: Implement keepinitrd kernel parameter

This patch implements keepinitrd kernel parameter. By default, keepinitrd=0 so initrd memory will be freed by default freed but users can pass "keepinitrd=1" to keep the initrd memory. The keepinitrd kernel parameter is already implemented by unicore32, arm, and arm64 architectures and it is

Re: [PATCH net-next v4 0/9] net: Remove switchdev_ops

Tue, Feb 12, 2019 at 02:14:47PM CET, ido...@mellanox.com wrote: >On Mon, Feb 11, 2019 at 11:09:52AM -0800, Florian Fainelli wrote: >> Hi all, >> >> This patch series finishes by the removal of switchdev_ops. To get there >> we convert the existing switchdev_port_attr_{set,get} switchdev_ops to >>

[PATCH 2/2] arm64: dts: Add SEI Robotics SEI510 Board

The SEI Robotics SEI510 Board is based on the Amlogic G12A S905X2 and has the following features : - Amlogic G12A S905X2 SoC - 10/100 Ethernet - USB2 + USB3 ports - Micro SDCard Port - Audio + CVBS AV Jack port - HDMI 2.1 + CEC Port - ADC Touch Button - Far-Field Microphone Array + Mono HP - IR

[PATCH 0/2] arm64: dts: Add SEI Robotics SEI510 Board support

This patchset adds minimal support for the SEI Robotics SEI510 Board, which is based on the Amlogic G12A S905X2 : and has the following features : - Amlogic G12A S905X2 SoC - 10/100 Ethernet - USB2 + USB3 ports - Micro SDCard Port - Audio + CVBS AV Jack port - HDMI 2.1 + CEC Port - ADC Touch

[PATCH 1/2] vendor-prefixes: Add prefix for Shenzhen SEI Robotics Co., Ltd

Add vendor prefix for the Shenzhen SEI Robotics Co., Ltd, a chinese ODM specialized in Android TV HDMI Stick, OTT Box, Hybrid STB, Smart Home Gateway & more. Signed-off-by: Neil Armstrong --- Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH v2 18/28] thunderbolt: Scan only valid NULL adapter ports in hotplug

On Wed, Feb 06, 2019 at 04:17:28PM +0300, Mika Westerberg wrote: > The only way to expand Thunderbolt topology is through the NULL adapter > ports (typically ports 1, 2, 3 and 4). There is no point handling > Thunderbolt hotplug events on any other port. > > Add a helper function

[PATCH] drm/amdgpu: fix several indentation issues

From: Colin Ian King There are several statements that are incorrectly indented. Fix these. Signed-off-by: Colin Ian King --- drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c | 2 +- drivers/gpu/drm/amd/amdgpu/dce_v6_0.c| 2 +- drivers/gpu/drm/amd/amdgpu/nbio_v7_4.c

Re: [GIT PULL] PHY: For 5.1 merge window

On Tue, Feb 12, 2019 at 06:43:19PM +0530, Kishon Vijay Abraham I wrote: > Hi Greg, > > Please find the pull request for 5.1 merge window below. > > It adds two new Armada PHY drivers to support COMPHY and UTMI PHY and a > PHY driver to support Cadence D-PHY. It also extends existing omap-usb2

Re: [PATCH v2 0/4] perf: enable compression of record mode trace to save storage space

On 12.02.2019 15:27, Arnaldo Carvalho de Melo wrote: > Em Mon, Feb 11, 2019 at 11:17:14PM +0300, Alexey Budankov escreveu: >> This is the rebase to the tip of Arnaldo's perf/core repository. > >> The patch set implements runtime trace compression for record mode and >> trace file

[PATCH v3 1/3] mmc: sdhci: use WP GPIO in sdhci_check_ro()

Even though SDHCI controllers may have a dedicated WP pin that can be queried using the SDHCI_PRESENT_STATE register, some platforms may chose to use a separate regular GPIO to route the WP signal. Such a GPIO is typically represented using the wp-gpios property in the Device Tree. Unfortunately,

[PATCH v3 0/3] mmc: Introduce support for WP GPIO in the core SDHCI

Hello, While doing the bring up of a Zynq 7000 platform where the WP signal of a SD slot is connected to a regular GPIO rather than through the SDHCI WP pin, I realized that the GPIO described by wp-gpios was properly requested, but it was in fact not used at all. Indeed, the SDHCI core

Re: [PATCH] drm/msm/a6xx: Add support for an interconnect path

Hi Greg, On 2/12/19 12:16, Greg KH wrote: > On Tue, Feb 12, 2019 at 11:52:38AM +0200, Georgi Djakov wrote: >> From: Jordan Crouse >> >> Try to get the interconnect path for the GPU and vote for the maximum >> bandwidth to support all frequencies. This is needed for performance. >> Later we will

[PATCH v3 3/3] mmc: sdhci-tegra: drop ->get_ro() implementation

The SDHCI core is know properly checking for the state of a WP GPIO, so there is no longer any need for the sdhci-tegra code to implement ->get_ro() using mmc_gpio_get_ro(). Signed-off-by: Thomas Petazzoni Tested-by: Thierry Reding Acked-by: Thierry Reding Acked-by: Adrian Hunter --- Changes

[PATCH v3 2/3] mmc: sdhci-omap: drop ->get_ro() implementation

The SDHCI core is now properly checking for the state of a WP GPIO, so there is no longer any need for the sdhci-omap code to implement ->get_ro() using mmc_gpio_get_ro(). Signed-off-by: Thomas Petazzoni Reviewed-by: Thierry Reding Acked-by: Adrian Hunter --- Changes since v2: - Added Acked-by

Re: [PATCH net-next v4 4/9] mlxsw: spectrum_switchdev: Handle SWITCHDEV_PORT_ATTR_GET/SET

On Mon, Feb 11, 2019 at 11:09:56AM -0800, Florian Fainelli wrote: > Following patches will change the way we communicate getting or setting > a port's attribute and use a blocking notifier to perform those tasks. > > Prepare mlxsw to support receiving notifier events targeting >

Re: [PATCH v3 6/6] RISC-V: Implement keepinitrd kernel parameter

On Feb 12 2019, Anup Patel wrote: > This patch implements keepinitrd kernel parameter. By default, > keepinitrd=0 so initrd memory will be freed by default freed but -freed Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3

Re: [PATCH 0/2] driver core: Fixes related to device links

On Tue, Feb 12, 2019 at 01:01:13PM +0100, Rafael J. Wysocki wrote: > Hi Greg at al, > > These fix two issues on top of the recent device links material in > driver-core/driver-core-next. > > The first one fixes a race condition that may trigger when > __pm_runtime_set_status() is used

Re: [PATCH net-next v4 9/9] net: Remove switchdev_ops

On Mon, Feb 11, 2019 at 11:10:01AM -0800, Florian Fainelli wrote: > Now that we have converted all possible callers to using a switchdev > notifier for attributes we do not have a need for implementing > switchdev_ops anymore, and this can be removed from all drivers the > net_device structure. >

Re: [PATCH v3 1/3] mmc: sdhci: use WP GPIO in sdhci_check_ro()

On 12/02/19 4:07 PM, Thomas Petazzoni wrote: > Even though SDHCI controllers may have a dedicated WP pin that can be > queried using the SDHCI_PRESENT_STATE register, some platforms may > chose to use a separate regular GPIO to route the WP signal. Such a > GPIO is typically represented using the

Re: [PATCH 0/2] eeprom: at24: new property

wt., 5 lut 2019 o 15:00 Bartosz Golaszewski napisał(a): > > From: Bartosz Golaszewski > > Microchip 24aa02t EEPROM is compatible with Atmel 24c02 except that > it's visible on 8 i2c slave addresses. We already support such a > use case with hard-coded config for 'atmel,24c00'. Let's add a more >

Re: [PATCH] parisc: use memblock_alloc() instead of custom get_memblock()

On Tue, Feb 12, 2019 at 03:59:50PM +0200, Mike Rapoport wrote: > -static void * __init get_memblock(unsigned long size) > -{ > - static phys_addr_t search_addr __initdata; > - phys_addr_t phys; > - > - if (!search_addr) > - search_addr = PAGE_ALIGN(__pa((unsigned long)

Re: [tip:locking/core] sched/wake_q: Reduce reference counting for special users

> diff --git a/kernel/futex.c b/kernel/futex.c > index 69e619baf709..2abe1a0b3062 100644 > --- a/kernel/futex.c > +++ b/kernel/futex.c > @@ -1463,8 +1463,7 @@ static void mark_wake_futex(struct wake_q_head *wake_q, > struct futex_q *q) >* Queue the task for later wakeup for after we've

Re: [PATCH] x86/kvm/nVMX: read from MSR_IA32_VMX_PROCBASED_CTLS2 only when it is available

On 07/02/19 22:17, Jim Mattson wrote: >> SDM says MSR_IA32_VMX_PROCBASED_CTLS2 is only available "If >> (CPUID.01H:ECX.[5] && IA32_VMX_PROCBASED_CTLS[63])". It was found that >> some old cpus (namely "Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (family: 0x6, >> model: 0xf, stepping: 0x6") don't have it.

[RFC PATCH v1 0/3] bd718x7: Support SNVS low power state

Patch series adding SNVS power state support to ROHM bd718x7 driver. The SNVS is a low power state used by i.MX family of SoCs. In SNVS state processor and most of the peripherials are shut off in order to minimize power consumption. BD71837 and BD71847 can be configured to use the SNVS state as

[RFC PATCH v1 1/3] devicetree: bindings: bd718x7: document HW state related ROHM specific properties

Add ROHM BD71837 / BD71847 specific device tree bindings for controlling the PMIC shutdown/reset states and voltages for different HW states. The PMIC was designed to be used with NXP i.MX8 SoC and it supports SNVS low power state which seems to be typical for NXP i.MX SoCs. However, when SNVS is

Re: possible deadlock in pipe_lock (2)

On Tue, Feb 12, 2019 at 2:39 PM Amir Goldstein wrote: > > > > My other thought is that perhaps sb_start_write() should invoke > > > s_ops->start_write() so that overlay can do the freeze protection on > > > the upper early. > > > > So my understanding of overlayfs is pretty basic so I'm sorry if

[RFC PATCH v1 2/3] regulator: add regulator_desc_list_voltage_linear_range

Add regulator_desc_list_voltage_linear_range which can be used by drivers for getting the voltages before regulator is registered. This may be useful for drivers which need to fetch the voltage selectors at device-tree parsing callback. Signed-off-by: Matti Vaittinen --- Please not apply as

[RFC PATCH v1 3/3] regulator: bd718x7: Support SNVS low power state

read ROHM BD71837 / BD71847 specific device tree bindings for controlling the PMIC shutdown/reset states and voltages for different HW states. The PMIC was designed to be used with NXP i.MX8 SoC and it supports SNVS low power state which seems to be typical for NXP i.MX SoCs. However, when SNVS is

Re: [PATCH net-next v2 06/16] net: bridge: Stop calling switchdev_port_attr_get()

On Sun, Feb 10, 2019 at 11:34:14AM -0800, Florian Fainelli wrote: > Le 2/10/19 à 11:05 AM, Ido Schimmel a écrit : > > On Sun, Feb 10, 2019 at 09:50:55AM -0800, Florian Fainelli wrote: > >> Now that all switchdev drivers have been converted to checking the > >> bridge port flags during the prepare

Applied "ASoC: Use __printf markup to silence compiler" to the asoc tree

The patch ASoC: Use __printf markup to silence compiler has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Applied "ASoC: pcm3060: Add soft reset on probe" to the asoc tree

The patch ASoC: pcm3060: Add soft reset on probe has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus

Applied "ASoC: pcm3060: Add clock select" to the asoc tree

The patch ASoC: pcm3060: Add clock select has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during

Applied "tlv320aic32x4: delay i2c access by 1 ms after hardware reset" to the asoc tree

The patch tlv320aic32x4: delay i2c access by 1 ms after hardware reset has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "regulator: lp8788-buck: Convert to linear range" to the regulator tree

The patch regulator: lp8788-buck: Convert to linear range has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "dt-bindings: spi: Document Renesas R-Car Gen3 RPC-IF controller bindings" to the spi tree

The patch dt-bindings: spi: Document Renesas R-Car Gen3 RPC-IF controller bindings has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the

Applied "regulator: max77802-regulator: fix indentation in if statement" to the regulator tree

The patch regulator: max77802-regulator: fix indentation in if statement has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the

Applied "regulator: s2mps11: Fix steps for buck7, buck8 and LDO35" to the regulator tree

The patch regulator: s2mps11: Fix steps for buck7, buck8 and LDO35 has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "spi: Add Renesas R-Car Gen3 RPC-IF SPI controller driver" to the spi tree

The patch spi: Add Renesas R-Car Gen3 RPC-IF SPI controller driver has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

[PATCH 0/3] arm64: meson: Add SoC ID detection for G12A

This patchset : - Fixes the package id detection for S905 variants and AXG packages - Adds new SoC IDs and Packages IDs for G12A/G12B - Adds Add AO Secure node for G12A dtsi Neil Armstrong (3): soc: amlogic: gx-socinfo: Add mask for each SoC packages soc: amlogic: gx-socinfo: Add new SoC IDs

[PATCH 1/3] soc: amlogic: gx-socinfo: Add mask for each SoC packages

When updated IDs on f842c41adc04 ("amlogic: meson-gx-socinfo: Update soc ids") we introduced packages ids using the full 8bit value, but in the function socinfo_to_package_id() the id was filtered with the 0xf0 mask. While the 0xf0 mask is valid for most board, it filters out the lower 4 bits

[PATCH 2/3] soc: amlogic: gx-socinfo: Add new SoC IDs and Packages IDs

This adds the G12A and G12B SoC ids and the S90X2 package ID. Signed-off-by: Neil Armstrong --- drivers/soc/amlogic/meson-gx-socinfo.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/soc/amlogic/meson-gx-socinfo.c b/drivers/soc/amlogic/meson-gx-socinfo.c index

[PATCH 3/3] arm64: dts: meson-g12a: Add AO Secure node

This adds the Always-On ao-secure system control registers node, which is used by the meson-gx-socinfo driver to detect the SoC IDs. Signed-off-by: Neil Armstrong --- arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git

Re: [PATCH 2/2] pwm: hibvt: Add hi3559v100 support

On Tue, Feb 12, 2019 at 10:49:27AM +0100, Mathieu Othacehe wrote: > Add support for hi3559v100-shub-pwm and hisilicon,hi3559v100-pwm > platforms. They require a special quirk: pwm has to be enabled again > to force duty_cycle refresh. > > Signed-off-by: Mathieu Othacehe > --- >

[RFC PATCH v1 17/25] printk: add processor number to output

It can be difficult to sort printk out if multiple processors are printing simultaneously. Add the processor number to the printk output to allow the messages to be sorted. Signed-off-by: John Ogness --- kernel/printk/printk.c | 19 +++ 1 file changed, 15 insertions(+), 4

[RFC PATCH v1 03/25] printk-rb: define ring buffer struct and initializer

See Documentation/printk-ringbuffer.txt for details about the initializer arguments. Signed-off-by: John Ogness --- include/linux/printk_ringbuffer.h | 28 1 file changed, 28 insertions(+) diff --git a/include/linux/printk_ringbuffer.h

[RFC PATCH v1 25/25] printk: remove unused code

Code relating to the safe context and anything dealing with the previous log buffer implementation is no longer in use. Remove it. Signed-off-by: John Ogness --- kernel/printk/internal.h | 53 --- kernel/printk/printk.c | 167 ---

[RFC PATCH v1 14/25] printk: do boot_delay_msec inside printk_delay

Both functions needed to be called one after the other, so just integrate boot_delay_msec into printk_delay for simplification. Signed-off-by: John Ogness --- kernel/printk/printk.c | 35 +-- 1 file changed, 17 insertions(+), 18 deletions(-) diff --git

[RFC PATCH v1 06/25] printk-rb: add blocking reader support

Add a blocking read function for readers. An irq_work function is used to signal the wait queue so that write notification can be triggered from any context. Signed-off-by: John Ogness --- include/linux/printk_ringbuffer.h | 20 lib/printk_ringbuffer.c | 49

[RFC PATCH v1 19/25] printk: introduce emergency messages

Console messages are generally either critical or non-critical. Critical messages are messages such as crashes or sysrq output. Critical messages should never be lost because generally they provide important debugging information. Since all console messages are output via a fully preemptible

[RFC PATCH v1 20/25] serial: 8250: implement write_atomic

Implement a non-sleeping NMI-safe write_atomic console function in order to support emergency printk messages. Since interrupts need to be disabled during transmit, all usage of the IER register was wrapped with access functions that use the console_atomic_lock function to synchronize register

Oops in rpc_clnt_debugfs_register() from debugfs change

I've bisected an oops that occurs in rpc_clnt_debugfs_register() trying to dereference a pointer with -EACCES in it. This is the causing commit, though I suspect the bug is in sunrpc expecting to see NULL rather than an error. ff9fb72bc07705c00795ca48631f7fffe24d2c6b is the first bad commit

[RFC PATCH v1 02/25] printk-rb: add prb locking functions

Add processor-reentrant spin locking functions. These allow restricting the number of possible contexts to 2, which can simplify implementing code that also supports NMI interruptions. prb_lock(); /* * This code is synchronized with all contexts * except an NMI on the same

[RFC PATCH v1 00/25] printk: new implementation

Hello, As probably many of you are aware, the current printk implementation has some issues. This series (against 5.0-rc6) makes some fundamental changes in an attempt to address these issues. The particular issues I am referring to: 1. The printk buffer is protected by a global raw spinlock for

[RFC PATCH v1 04/25] printk-rb: add writer interface

Add the writer functions prb_reserve() and prb_commit(). These make use of processor-reentrant spin locks to limit the number of possible interruption scenarios for the writers. Signed-off-by: John Ogness --- include/linux/printk_ringbuffer.h | 17 lib/printk_ringbuffer.c | 172

[RFC PATCH v1 22/25] printk: implement /dev/kmsg

Since printk messages are now logged to a new ring buffer, update the /dev/kmsg functions to pull the messages from there. Signed-off-by: John Ogness --- fs/proc/kmsg.c | 4 +- include/linux/printk.h | 1 + kernel/printk/printk.c | 162

[RFC PATCH v1 23/25] printk: implement syslog

Since printk messages are now logged to a new ring buffer, update the syslog functions to pull the messages from there. Signed-off-by: John Ogness --- kernel/printk/printk.c | 340 ++--- 1 file changed, 235 insertions(+), 105 deletions(-) diff --git

[RFC PATCH v1 11/25] printk_safe: remove printk safe code

vprintk variants are now NMI-safe so there is no longer a need for the "safe" calls. NOTE: This also removes printk flushing functionality. Signed-off-by: John Ogness --- include/linux/hardirq.h | 2 - include/linux/printk.h | 27 --- init/main.c | 1 -

[RFC PATCH v1 18/25] console: add write_atomic interface

Add a write_atomic callback to the console. This is an optional function for console drivers. The function must be atomic (including NMI safe) for writing to the console. Console drivers must still implement the write callback. The write_atomic callback will only be used for emergency messages.

[RFC PATCH v1 24/25] printk: implement kmsg_dump

Since printk messages are now logged to a new ring buffer, update the kmsg_dump functions to pull the messages from there. Signed-off-by: John Ogness --- include/linux/kmsg_dump.h | 6 +- kernel/printk/printk.c| 258 -- 2 files changed, 139

Re: [PATCH v6 5/9] vsprintf: Factor out %pV handler as va_format()

On Tue, 12 Feb 2019 14:00:30 +0100 Petr Mladek wrote: > On Fri 2019-02-08 09:11:17, Joe Perches wrote: > > On Fri, 2019-02-08 at 16:23 +0100, Petr Mladek wrote: > > > Move the code from the long pointer() function. We are going to improve > > > error handling that will make it more

[PATCH] iio/gyro/bmg160: Use millidegrees for temperature scale

Standard unit for temperature is millidegrees Celcius, whereas this driver was reporting in degrees. Fix the scale factor in the driver. Signed-off-by: Mike Looijmans --- drivers/iio/gyro/bmg160_core.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

[RFC PATCH v1 01/25] printk-rb: add printk ring buffer documentation

The full documentation file for the printk ring buffer. Signed-off-by: John Ogness --- Documentation/printk-ringbuffer.txt | 377 1 file changed, 377 insertions(+) create mode 100644 Documentation/printk-ringbuffer.txt diff --git

[RFC PATCH v1 21/25] printk: implement KERN_CONT

Implement KERN_CONT based on the printing CPU rather than on the printing task. As long as the KERN_CONT messages are coming from the same CPU and no non-KERN_CONT messages come, the messages are assumed to belong to each other. Signed-off-by: John Ogness --- kernel/printk/printk.c | 73

[RFC PATCH v1 15/25] printk: print history for new consoles

When new consoles register, they currently print how many messages they have missed. However, many (or all) of those messages may still be in the ring buffer. Add functionality to print as much of the history as available. This is a clean replacement of the old exclusive console hack.

[RFC PATCH v1 09/25] printk: remove exclusive console hack

In order to support printing the printk log history when new consoles are registered, a global exclusive_console variable is temporarily set. This only works because printk runs with preemption disabled. When console printing is moved to a fully preemptible dedicated kthread, this hack no longer

[RFC PATCH v1 16/25] printk: implement CON_PRINTBUFFER

If the CON_PRINTBUFFER flag is not set, do not replay the history for that console. Signed-off-by: John Ogness --- kernel/printk/printk.c | 25 ++--- 1 file changed, 6 insertions(+), 19 deletions(-) diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c index

[RFC PATCH v1 05/25] printk-rb: add basic non-blocking reading interface

Add reader iterator static declaration/initializer, dynamic initializer, and functions to iterate and retrieve ring buffer data. Signed-off-by: John Ogness --- include/linux/printk_ringbuffer.h | 20 lib/printk_ringbuffer.c | 190 ++ 2 files

[RFC PATCH v1 07/25] printk-rb: add functionality required by printk

The printk subsystem needs to be able to query the size of the ring buffer, seek to specific entries within the ring buffer, and track if records could not be stored in the ring buffer. Signed-off-by: John Ogness --- include/linux/printk_ringbuffer.h | 5 +++ lib/printk_ringbuffer.c

[RFC PATCH v1 10/25] printk: redirect emit/store to new ringbuffer

vprintk_emit and vprintk_store are the main functions that all printk variants eventually go through. Change these to store the message in the new printk ring buffer that the printk kthread is reading. Remove functions no longer in use because of the changes to vprintk_emit and vprintk_store. In

[RFC PATCH v1 13/25] printk: track seq per console

Allow each console to track which seq record was last printed. This simplifies identifying dropped records. Signed-off-by: John Ogness --- include/linux/console.h | 1 + kernel/printk/printk.c | 30 +++--- 2 files changed, 28 insertions(+), 3 deletions(-) diff --git

<    1   2   3   4   5   6   7   8   9   10   >