Re: [RFC PATCH 2/9] cpufreq: qcom: Re-organise kryo cpufreq to use it for other nvmem based qcom socs

Hi Niklas, On 4/4/2019 10:39 AM, Niklas Cassel wrote: > From: Sricharan R > > The kryo cpufreq driver reads the nvmem cell and uses that data to > populate the opps. There are other qcom cpufreq socs like krait which > does similar thing. Except for the interpretation of the read data, > rest

Re: [RESENT PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

On 08.04.19 06:07, zhong jiang wrote: > When adding the memory by probing memory block in sysfs interface, there is an > obvious issue that we will unlock the device_hotplug_lock when fails to takes > it. > > That issue was introduced in Commit 8df1d0e4a265 > ("mm/memory_hotplug: make

Re: [PATCH] s390/mm: Silence compiler warning when compiling without CONFIG_PGSTE

On 07.04.19 14:55, Thomas Huth wrote: > If CONFIG_PGSTE is not set (e.g. when compiling without KVM), GCC complains: > > CC arch/s390/mm/pgtable.o > arch/s390/mm/pgtable.c:413:15: warning: ‘pmd_alloc_map’ defined but not > used [-Wunused-function] > static pmd_t *pmd_alloc_map(struct

Re: [PATCH] soundwire: fix pm_runtime_get_sync return code checks

> On 5 Apr 2019, at 17:04, Pierre-Louis Bossart > wrote: > > On 4/5/19 2:26 AM, Jan Kotas wrote: >> >> >> ret = pm_runtime_get_sync(slave->bus->dev); >> -if (ret < 0) >> +if (ret < 0 && ret != -EACCES) >> > There was a patch submitted on 3/28 by Srinivas Kandagatla who

Re: WARN_ON_ONCE() hit at kernel/events/core.c:330

On 4/4/19 3:03 PM, Peter Zijlstra wrote: > On Thu, Apr 04, 2019 at 01:09:09PM +0200, Peter Zijlstra wrote: > >> That is not entirely the scenario I talked about, but *groan*. >> >> So what I meant was: >> >> CPU-0 CPU-n >> >>

Re: shmem_recalc_inode: unable to handle kernel NULL pointer dereference

On 08.04.2019 9:05, Hugh Dickins wrote: On Fri, 5 Apr 2019, Konstantin Khlebnikov wrote: On 05.04.2019 5:12, Hugh Dickins wrote: Hi Alex, could you please give the patch below a try? It fixes a problem, but I'm not sure that it's your problem - please let us know. I've not yet written up the

[REGRESSION] AppArmor module parameter layout changed with c5459b829b716

Hi A recent commit changed how `/sys/module/apparmor/parameters/enabled` looks. It was "Y"/"N" before, now it is an integer. I *think* the commit that changed this was: commit c5459b829b716dafd226ad270f25c9a3050f7586 Author: Kees Cook Date: Thu Sep 13 22:28:48 2018 -0700 LSM: Plumb

Re: [PATCH V2 19/20] DT bindings: spi: document tx/rx clock delay properties

On Thu, Apr 04, 2019 at 05:14:18PM -0700, Sowjanya Komatineni wrote: > Tegra SPI controller has TX and RX trimmers to tuning the delay of > SPI master clock with respect to the data. Please use subject lines matching the style for the subsystem. This makes it easier for people to identify

RE: [PATCH 1/2] dt-bindings: rtc: add battery-low-hw-alarm property

HI, > On 06/04/2019 01:07:13-0500, Rob Herring wrote: > > On Wed, Apr 03, 2019 at 04:52:44PM +0200, Flavio Suligoi wrote: > > > Some RTC devices have a battery-low automatic detection circuit. > > > The battery-low event is usually reported with: > > > > > > - a bit change in a RTC status

Applied "ASoC: Intel: bytcht_es8316: Add quirk for the Teclast X98+ II" to the asoc tree

The patch ASoC: Intel: bytcht_es8316: Add quirk for the Teclast X98+ II 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 "ASoC: wm1133-ev1: Switch to SPDX identifier" to the asoc tree

The patch ASoC: wm1133-ev1: Switch to SPDX identifier 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

Applied "ASoC: phycore-ac97: Switch to SPDX identifier" to the asoc tree

The patch ASoC: phycore-ac97: Switch to SPDX identifier 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

Re: [PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

://github.com/0day-ci/linux/commits/zhong-jiang/mm-memory_hotplug-Do-not-unlock-when-fails-to-take-the-device_hotplug_lock/20190408-142325 config: x86_64-randconfig-x007-201914 (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save the attached .config to linux build tree

Applied "ASoC: p1022_rdk: Switch to SPDX identifier" to the asoc tree

The patch ASoC: p1022_rdk: Switch to SPDX identifier 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

Applied "ASoC: mpc5200_psc_ac97: Switch to SPDX identifier" to the asoc tree

The patch ASoC: mpc5200_psc_ac97: Switch to SPDX identifier 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

Re: [RESENT PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

On Mon, Apr 08, 2019 at 12:07:17PM +0800, zhong jiang wrote: > When adding the memory by probing memory block in sysfs interface, there is an > obvious issue that we will unlock the device_hotplug_lock when fails to takes > it. > > That issue was introduced in Commit 8df1d0e4a265 >

Applied "ASoC: mpc5200_dma: Switch to SPDX identifier" to the asoc tree

The patch ASoC: mpc5200_dma: Switch to SPDX identifier 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

Applied "ASoC: stm32: fix sai driver name initialisation" to the asoc tree

The patch ASoC: stm32: fix sai driver name initialisation 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: fsl-dma: Switch to SPDX identifier" to the asoc tree

The patch ASoC: fsl-dma: Switch to SPDX identifier 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

Applied "regulator: s2mpa01: Convert to use simplified DT parsing" to the regulator tree

The patch regulator: s2mpa01: Convert to use simplified DT parsing 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 "regulator: bd718x7: Use rdev_get_id() to get regulator id" to the regulator tree

The patch regulator: bd718x7: Use rdev_get_id() to get regulator id 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 "ASoC: ab8500: add range to usleep_range" to the regulator tree

The patch ASoC: ab8500: add range to usleep_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) and

Applied "spi: document tx/rx clock delay properties" to the spi tree

The patch spi: document tx/rx clock delay properties 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) and sent to

Applied "spi: add a method for configuring CS timing" to the spi tree

The patch spi: add a method for configuring CS timing 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) and sent to

Applied "spi: tegra114: add 3 wire transfer mode support" to the spi tree

The patch spi: tegra114: add 3 wire transfer mode support 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) and sent to

Applied "spi: bitbang: Introduce spi_bitbang_init()" to the spi tree

The patch spi: bitbang: Introduce spi_bitbang_init() 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) and sent to

Applied "spi: gpio: Use devm_spi_register_master()" to the spi tree

The patch spi: gpio: Use devm_spi_register_master() 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) and sent to Linus

Applied "spi-summary: document set_cs_timing" to the spi tree

The patch spi-summary: document set_cs_timing 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) and sent to Linus

Applied "spi: gpio: Make sure spi_master_put() is called in every error path" to the spi tree

The patch spi: gpio: Make sure spi_master_put() is called in every error path 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

Applied "spi: tegra114: add dual mode support" to the spi tree

The patch spi: tegra114: add dual mode support 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) and sent to Linus

Applied "spi: bcm2835aux: Fix build error without CONFIG_DEBUG_FS" to the spi tree

The patch spi: bcm2835aux: Fix build error without CONFIG_DEBUG_FS 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] lightnvm: pblk: fix crash in pblk_end_partial_read due to multipage bvecs

From: Hans Holmberg Ever since '07173c3ec276 ("block: enable multipage bvecs")' we need to handle bios with multipage bvecs in pblk. Currently, a multipage bvec results in a crash[1]. Fix this by using bvec iterators in stead of direct bvec indexing. Also add a dcache flush, for the same

Applied "spi: pxa2xxx: change "no DMA channels..." msg from debug to warning" to the spi tree

The patch spi: pxa2xxx: change "no DMA channels..." msg from debug to warning 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

Re: Removing pcap? (EZX support in mainline linux)

On Sun, 7 Apr 2019 16:07:41 +0200 Alexandre Belloni wrote: > Hello Antonio, Harald, > Hi everyone, adding Robert to CC as he is listed as the current maintainer of ARM/EZX SMARTPHONES in the MAINTAINERS file. > I've had a look at the PCAP RTC driver because I'm removing a few > deprecated

Re: [PATCH v3 19/36] thunderbolt: Extend tunnel creation to more than 2 adjacent switches

On Sun, Apr 07, 2019 at 06:54:25PM +0200, Lukas Wunner wrote: > On Thu, Mar 28, 2019 at 03:36:16PM +0300, Mika Westerberg wrote: > > +struct tb_path *tb_path_alloc(struct tb *tb, struct tb_port *src, int > > src_hopid, > > + struct tb_port *dst, int dst_hopid, int link_nr,

Re: [PATCH 1/4] clk: meson: mpll: add init callback and regs

On Fri, 2019-04-05 at 13:43 -0700, Stephen Boyd wrote: > Quoting Michael Turquette (2019-04-05 08:43:40) > > Hi Jerome, > > > > On Fri, Mar 29, 2019 at 3:58 PM Jerome Brunet wrote: > > > On Fri, 2019-03-29 at 15:14 -0700, Stephen Boyd wrote: > > > > > > We actively discourage using init

Re: [PATCH] pinctrl:intel: Retain HOSTSW_OWN for requested gpio pin

On Mon, Apr 08, 2019 at 12:21:03PM +0800, Chris Chiu wrote: > +static void > +intel_gpio_update_pad_mode(void __iomem *hostown, u32 mask, u32 value) > +{ > + u32 curr = readl(hostown); > + u32 updated = (curr & ~mask) | (value & mask); I think here we should first complain if the expected

Re: [PATCH] intel-lpss: Set the device in reset state when init

On Mon, Apr 08, 2019 at 01:41:58PM +0800, Binbin Wu wrote: > In virtualized setup, when system reboots due to warm > reset interrupt storm is seen. > > Call Trace: > > dump_stack+0x70/0xa5 > __report_bad_irq+0x2e/0xc0 > note_interrupt+0x248/0x290 > ? add_interrupt_randomness+0x30/0x220 >

Re: [PATCH 0/5] Handle MCA banks in a per_cpu way

On Sun, Apr 07, 2019 at 11:13:47PM +, Ghannam, Yazen wrote: > Yazen Ghannam (5): > x86/MCE: Make struct mce_banks[] static > x86/MCE: Handle MCA controls in a per_cpu way > x86/MCE/AMD: Don't cache block addresses on SMCA systems > x86/MCE: Make number of MCA banks per_cpu > x86/MCE:

Re: [PATCH 08/12] arm64: dts: allwinner: h6: Add MMC1 pins

On Sat, Apr 06, 2019 at 01:45:10AM +0200, meg...@megous.com wrote: > From: Ondrej Jirman > > --- > arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 9 + > 1 file changed, 9 insertions(+) > > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi >

[PATCH] ARM: dts: imx6dl-sabreauto: update opp table for auto part

Update i.MX6DL automotive part's opp table according to i.MX6DL automotive datasheet Rev.9, 11/2018, it adds 996MHz set-point support as below: LDO enabled(min value): 996MHz: VDDARM: 1.275V, VDDSOC: 1.175V; 792MHz: VDDARM: 1.150V, VDDSOC: 1.150V; 396MHz: VDDARM: 1.125V, VDDSOC: 1.150V; Adding

Re: [MD] 4bc034d353: aim7.jobs-per-min -86.0% regression

On Mon, Apr 08 2019, kernel test robot wrote: > Greeting, > > FYI, we noticed a -86.0% regression of aim7.jobs-per-min due to commit: That is expected. The following commit 2bc13b83e6298486371761de503faeffd15b7534 should restore the performance. NeilBrown > > > commit:

Re: [PATCH] sched/core: expand sched_getaffinity(2) to return number of CPUs

* Alexey Dobriyan: >> >> Patch overloads sched_getaffinity(len=0) to simply return "nr_cpu_ids". >> >> This will make gettting CPU mask require at most 2 system calls >> >> and will eliminate unnecessary code. >> >> >> >> len=0 is chosen so that >> >> * passing zeroes is the simplest thing >> >>

Re: [PATCH 1/2] x86/mm/KASLR: Fix the wrong calculation of memory region initial size

On 04/06/19 at 06:43am, Borislav Petkov wrote: > On Sat, Apr 06, 2019 at 09:51:19AM +0800, Baoquan He wrote: > > It's KASLR happened in kernel_randomize_memory() of arch/x86/mm/kaslr.c . > > What is "KASLR happened in"? This doesn't make any sense. When you look > at that function, there's a

[PATCH 3/3] ARM: omap2: move platform-specific asm-offset.h to arch/arm/mach-omap2

is only generated and included by arch/arm/mach-omap2/, so it does not need to reside in the globally visible include/generated/. I moved and renamed it to arch/arm/mach-omap2/pm-asm-offsets.h since the prefix 'omap2-' is just redundant in mach-omap2/. Signed-off-by: Masahiro Yamada --- Can

[PATCH 2/3] ARM: at91: move platform-specific asm-offset.h to arch/arm/mach-at91

is only generated and included by arch/arm/mach-at91/, so it does not need to reside in the globally visible include/generated/. I moved and renamed it to arch/arm/mach-at91/pm_data-offsets.h since the prefix 'at91_' is just redundant in mach-at91/. Signed-off-by: Masahiro Yamada --- Can this

[PATCH 1/3] ARM: visit mach-* and plat-* directories when cleaning

When you run "make clean" for arm, it never visits mach-* or plat-* directories because machine-y and plat-y are just empty. When cleaning, all machine, plat directories are accumulated to machine-, plat-, respectively. So, let's pass them to core- to clean up those directories. Signed-off-by:

[PATCH v3 1/3] ARM: dts: da850: add cpu node and operating points to DT

From: David Lechner This adds a cpu node and operating points to the common da850.dtsi file. Additionally, a regulator is added to the LEGO EV3 board along with some board-specific CPU configuration. Regulators need to be hooked up on other boards to get them working. Signed-off-by: David

[PATCH v3 0/3] ARM: da850: enable cpufreq in DT mode

From: Bartosz Golaszewski This series adds cpufreq-dt operating points for da850 boards supported with device tree (da850-lcdk, da850-lego-ev3, da850-evm). Last patch enables CPUFREQ_DT in davinci_all_defconfig. v1 -> v2: - use the VDCDC3_1.2V regulator as cpu-supply on da850-evm v2 -> v3: -

[PATCH v3 3/3] ARM: davinci_all_defconfig: Enable CPUFREQ_DT

From: David Lechner This sets CONFIG_CPUFREQ_DT=m in davinci_all_defconfig. This is used for frequency scaling on device tree boards. Signed-off-by: David Lechner Signed-off-by: Bartosz Golaszewski --- arch/arm/configs/davinci_all_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v3 2/3] ARM: dts: da850-evm: enable cpufreq

From: Bartosz Golaszewski Enable cpufreq-dt support for da850-evm. The cvdd is supplied by the tps6507 pmic with configurable output voltage, so all operating points can be enabled. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/da850-evm.dts | 13 + 1 file changed, 13

Re: [PATCH 0/4] clk: meson: g12a audio clock controller support

On 29/03/2019 17:06, Jerome Brunet wrote: > This patchset updates the axg audio controller to support the audio > controller of the g12a SoC family. > > Jerome Brunet (3): > dt-bindings: clk: axg-audio: add g12a support > clk: meson: axg_audio: replace prefix axg by aud > clk: meson:

Re: [PATCH v3 3/4] lib: logic_pio: Reject accesses to unregistered CPU MMIO regions

On 05/04/2019 19:06, Bjorn Helgaas wrote: On Fri, Apr 05, 2019 at 09:10:27AM +0100, John Garry wrote: On 04/04/2019 19:58, Bjorn Helgaas wrote: On Thu, Apr 04, 2019 at 10:43:36AM -0700, Guenter Roeck wrote: On Thu, Apr 04, 2019 at 05:52:35PM +0100, John Garry wrote: Note that the f71805f

Re: [PATCH] modpost: make KBUILD_MODPOST_WARN also configurable for external modules

Hi! On 07.04.2019 11:04, Masahiro Yamada wrote: > (+CC Jonas Gorski) > > > On Tue, Mar 26, 2019 at 6:58 PM Wiebe, Wladislav (Nokia - DE/Ulm) > wrote: >> >> Commit ea837f1c0503 ("kbuild: make modpost processing configurable") >> was intended to give KBUILD_MODPOST_WARN flexibility to be

RE: [PATCH] intel-lpss: Set the device in reset state when init

Hi Mika, Will correct the title line in the next version. Thanks. -- Best wishes, Binbin > -Original Message- > From: Mika Westerberg [mailto:mika.westerb...@linux.intel.com] > Sent: Monday, April 8, 2019 3:43 PM > To: Wu, Binbin > Cc: r...@rjwysocki.net; linux...@vger.kernel.org; >

[PATCH v2] Add COMPILE_TEST to CONFIG_ARM_TIMER_SP804

This is only used on arm and arm64 platforms. Add COMPILE_TEST option. Tested with 5.1-rc3+ on Fedora/RISCV. CONFIG_ARM_TIMER_SP804 no more shows up in riscv config. Signed-off-by: David Abdurachmanov --- drivers/clocksource/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH v3 6/9] arm64: dts: qcom: qcs404: Add rpmpd node

On 2019-03-27 18:08, Sibi Sankar wrote: From: Bjorn Andersson Add the rpmpd node on the qcs404 and define the available levels. Signed-off-by: Bjorn Andersson [sibis: fixup available levels] Signed-off-by: Sibi Sankar --- arch/arm64/boot/dts/qcom/qcs404.dtsi | 55

Re: [PATCH v3 9/9] arm64: dts: qcom: msm8998: Add rpmpd node

On 2019-03-27 18:08, Sibi Sankar wrote: Add the rpmpd node on the msm8998 and define the available levels. Signed-off-by: Sibi Sankar --- arch/arm64/boot/dts/qcom/msm8998.dtsi | 51 +++ 1 file changed, 51 insertions(+) diff --git

[RFC PATCH v3 1/4] x86: Add new config symbol to unify conditional definition of hv_irq_callback_count

Now the CONFIG_HYPERV and CONFIG_XEN can be used to control the definition /usage of hv_irq_callback_count. If another linux guest also needs to use the hv_irq_callback_count, current conditional definition looks unreadable. Signed-off-by: Zhao Yakui --- arch/x86/Kconfig | 3 +++

[PATCH v2] mfd: intel-lpss: Set the device in reset state when init

In virtualized setup, when system reboots due to warm reset interrupt storm is seen. Call Trace: dump_stack+0x70/0xa5 __report_bad_irq+0x2e/0xc0 note_interrupt+0x248/0x290 ? add_interrupt_randomness+0x30/0x220 handle_irq_event_percpu+0x54/0x80 handle_irq_event+0x39/0x60

[RFC PATCH v3 0/4] x86: Add the support of ACRN guest under arch/x86

ACRN is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open source platform. It is built for embedded IOT with small footprint and real-time features. More details can be found in

[RFC PATCH v3 4/4] x86: Add hypercall for acrn_guest

When acrn_hypervisor is detected, the hypercall is needed so that the acrn guest can query/config some settings. For example: it can be used to query the resources in hypervisor and manage the CPU/memory/device/ interrupt for Guest system. So the hypercall is added so that the kernel can

[RFC PATCH v3 3/4] x86: Use HYPERVISOR_CALLBACK_VECTOR for acrn_guest upcall vector

Linux kernel uses the HYPERVISOR_CALLBACK_VECTOR for hypervisor upcall vector. And it is already used for Xen and HyperV. After Acrn hypervisor is detected, it will also use this defined vector to notify kernel. Co-developed-by: Jason Chen CJ Signed-off-by: Jason Chen CJ Signed-off-by: Zhao

[RFC PATCH v3 2/4] x86: Add the support of ACRN guest

ACRN is an open-source hypervisor maintained by Linuxfoundation. This is to add the Linux guest support on acrn-hypervisor. Add x86_hyper_acrn into supported hypervisors array, which enables Linux ACRN guest running on ACRN hypervisor. It is restricted to X86_64. Co-developed-by: Jason Chen CJ

[PATCH V3 1/2] trace,x86: Add external_interrupts to the irq_vectors class

Currently, the irq_vectors is showing the entry and exit events for the interrupts of the architecture, but not for external interrupts. Adds the tracepoints for external interrupts. Example of output: -0 [000] d.h. 102.890935: external_interrupt_entry: vector=35 -0 [000] d.h.

Re: [PATCH v2] ARM: sun8i: h3: bluetooth for Banana Pi M2 Zero board

On Sun, Apr 07, 2019 at 10:23:21PM +0200, Andreas Kemnade wrote: > ping > > On Fri, 1 Mar 2019 19:52:12 +0100 > Andreas Kemnade wrote: > > > The Banana Pi M2 Zero board has an AP6212 BT+Wifi combo chip > > with broadcom internals attached to UART1 and some gpios. > > This addition is in line

[PATCH V3 2/2] trace,x86: Add nmi to the irq_vectors class

Currently, the irq_vector class of tracepoints does not include the NMI entry. The NMI was in the first set of tracepoints for IRQs, but it was dropped off because of the logic of switching IDT when enabling trace[1]. However, as the switching IDT logic was removed [2], it is possible to add the

Re: [v3 PATCH 5/6] usb: roles: add USB Type-B GPIO connector driver

Hi, On Thu, 2019-04-04 at 23:35 +0700, Linus Walleij wrote: > On Wed, Apr 3, 2019 at 9:09 AM Chunfeng Yun wrote: > > > Due to the requirement of usb-connector.txt binding, the old way > > using extcon to support USB Dual-Role switch is now deprecated > > when use Type-B connector. > > This patch

Re: linux-next: manual merge of the staging tree with the staging.current tree

On Mon, 8 Apr 2019 13:02:12 +1000 Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the staging tree got a conflict in: > > drivers/iio/industrialio-buffer.c > > between commit: > > 20ea39ef9f2f ("iio: Fix scan mask selection") > > from the staging.current tree and

Re: [PATCH] ACPI / LPSS: Don't skip late system PM ops for hibernate on BYT/CHT

Hi, On 07-04-19 22:58, Robert R. Howell wrote: On 4/3/19 2:54 AM, Hans de Goede wrote: Hi, On 03-04-19 07:43, Kai-Heng Feng wrote: i2c-designware-platdrv fails to work after the system restored from hibernation: [ 272.775692] i2c_designware 80860F41:00: Unknown Synopsys component type:

Re: [PATCH 2/2] arm64: dts: h6: Add watchdog node

On Sun, Apr 07, 2019 at 04:27:36PM +0200, Clément Péron wrote: > Hi, > > On Fri, 5 Apr 2019 at 18:24, Clément Péron wrote: > > > > Hi, > > > > On Fri, 5 Apr 2019 at 17:08, Maxime Ripard > > wrote: > > > > > > On Fri, Apr 05, 2019 at 10:59:35PM +0800, Chen-Yu Tsai wrote: > > > > On Fri, Apr 5,

Re: PRINTER BUG LINUX MINT 19 TARA

On 07.04.19 23:09, Khz2020 wrote: > Please see attached. It was working fine prior to installing Canon linux > drivers. CUPS disconnect maybe? Wrong list. This maillist is about the linux KERNEL, whilst your problem is about CUPS. So, please ask the CUPS folks. --mtx -- Enrico Weigelt, metux

Re: WARN_ON_ONCE() hit at kernel/events/core.c:330

On Mon, Apr 08, 2019 at 09:12:28AM +0200, Thomas-Mich Richter wrote: > > Does the below cure things? It's not exactly pretty, but it could just > > do the trick. > > > > --- > > diff --git a/kernel/events/core.c b/kernel/events/core.c > > index dfc4bab0b02b..d496e6911442 100644 > > ---

I Need An Investment Partner

Assalamu Alaikum Wa Rahmatullahi Wa Barakatuh, Dear Friend, I came across your e-mail contact prior a private search while in need of your assistance. I am Aisha Al-Qaddafi, the only biological Daughter of Former President of Libya Col. Muammar Al-Qaddafi. Am a single Mother and a Widow

[PATCH v2 0/2] Preparing memhotplug for allocating memmap from hot-added range

v1 -> v2: Added David's feedback and his Reviewed-by Hi, these patches were posted as part of patchset [1], but it was agreed that patch#3 must be further discussed. Whole discussion can be seen in the cover letter. But the first two patches make sense by themselves, as the first one is a nice

[PATCH v2 2/2] mm, memory_hotplug: provide a more generic restrictions for memory hotplug

From: Michal Hocko arch_add_memory, __add_pages take a want_memblock which controls whether the newly added memory should get the sysfs memblock user API (e.g. ZONE_DEVICE users do not want/need this interface). Some callers even want to control where do we allocate the memmap from by

[PATCH v2 1/2] mm, memory_hotplug: cleanup memory offline path

From: Michal Hocko check_pages_isolated_cb currently accounts the whole pfn range as being offlined if test_pages_isolated suceeds on the range. This is based on the assumption that all pages in the range are freed which is currently the case in most cases but it won't be with later changes, as

Re: [PATCH v2] ARM: sun8i: h3: bluetooth for Banana Pi M2 Zero board

On Sat, Mar 2, 2019 at 2:53 AM Andreas Kemnade wrote: > > The Banana Pi M2 Zero board has an AP6212 BT+Wifi combo chip > with broadcom internals attached to UART1 and some gpios. ^ Broadcom > This addition is in line with similar boards This sentence is unfinished. > > Signed-off-by:

Re: [PATCH v3 8/9] soc: qcom: rpmpd: Add MSM8998 power-domains

On 2019-04-05 20:38, Marc Gonzalez wrote: On 27/03/2019 13:38, Sibi Sankar wrote: Add the shared cx/mx and sensor sub-system's cx and mx power-domains found on MSM8998. Signed-off-by: Sibi Sankar --- drivers/soc/qcom/rpmpd.c | 36 1 file changed, 36

Re: [v2] Updated locking documentation for transaction_t

Thanks, Ted, for your feedback! I'll submit a modified version. - Alex On 07.04.19 18:52, Theodore Ts'o wrote: > On Mon, Mar 18, 2019 at 07:42:37PM +0100, Alexander Lochmann wrote: >> /*t >> - * Where in the log does this transaction's commit start? [no locking] >> + * Where in the

[PATCH v3] Updated locking documentation for transaction_t

We used LockDoc to derive locking rules for each member of struct transaction_t. Based on those results, we extended the existing documentation by more members of struct transaction_t, and updated the existing documentation. Signed-off-by: Alexander Lochmann Signed-off-by: Horst Schirmeier ---

Re: [PATCH V3 1/2] trace,x86: Add external_interrupts to the irq_vectors class

On 4/8/19 10:14 AM, Daniel Bristot de Oliveira wrote: > Currently, the irq_vectors is showing the entry and exit events for > the interrupts of the architecture, but not for external interrupts. Oops... Sorry... Please, ignore this version... -- Daniel

Re: [PATCH 2/3] arm64: kdump: support more than one crash kernel regions

Hi Mike, On 2019/4/8 14:57, Mike Rapoport wrote: > Hi, > > On Fri, Apr 05, 2019 at 11:47:27AM +0800, Chen Zhou wrote: >> Hi Mike, >> >> On 2019/4/5 10:17, Chen Zhou wrote: >>> Hi Mike, >>> >>> On 2019/4/4 22:44, Mike Rapoport wrote: Hi, On Wed, Apr 03, 2019 at 09:51:27PM +0800,

Re: [PATCH 2/5] clocksource/drivers/timer-microchip-pit64b: add Microchip PIT64B support

Hi Claudiu, On 14/03/2019 17:26, claudiu.bez...@microchip.com wrote: > From: Claudiu Beznea > > Add driver for Microchip PIT64B timer. Timer could be used in continuous > mode or oneshot mode. The hardware has 2x32 bit registers for period > emulating a 64 bit timer. The LSB_PR and MSB_PR

Re: WARN_ON_ONCE() hit at kernel/events/core.c:330

On 4/8/19 10:22 AM, Peter Zijlstra wrote: > On Mon, Apr 08, 2019 at 09:12:28AM +0200, Thomas-Mich Richter wrote: >>> Does the below cure things? It's not exactly pretty, but it could just >>> do the trick. >>> >>> --- >>> diff --git a/kernel/events/core.c b/kernel/events/core.c >>> index

kernel/time/ntp.c: Possible off-by-one error in TAI range check?

Hello, while writing tests for clock adjustment auditing [1] [2], I stumbled upon a strange behavior of adjtimex(2) when setting the TAI offset... Commit 153b5d054ac2 ("ntp: support for TAI") added a possibility to change the TAI offset from userspace via adjtimex(2). The code checks if the

Re: [PATCH v2 1/4] ARM: davinci: fix cpufreq registration on da850-evm

On 04/04/19 4:44 PM, Adam Ford wrote: > On Thu, Apr 4, 2019 at 5:01 AM Bartosz Golaszewski wrote: >> >> śr., 3 kwi 2019 o 17:49 Adam Ford napisał(a): >>> >>> On Wed, Apr 3, 2019 at 7:50 AM Bartosz Golaszewski wrote: śr., 27 mar 2019 o 12:14 Sekhar Nori napisał(a): > > Hi

Re: [PATCH 1/1] rtc: ds3232: get SRAM access using NVMEM Framework

On 4/6/19 12:44 AM, Alexandre Belloni wrote: Hi, On 05/04/2019 11:14:35+, Han Nandor wrote: ` # hexdump -n 10 -C /sys/bus/nvmem/devices/ds3232_sram0/nvmem 74 65 73 74 69 6e 67 0a 00 00|testing...| 000a ` Thanks for that nice description! Glad

[PATCH v2 1/1] rtc: ds3232: get SRAM access using NVMEM Framework

DS3232 RTC has 236 bytes of persistent memory. Add RTC SRAM read and write access using the NVMEM Framework. Signed-off-by: Nandor Han --- Description --- Provides DS3232 RTC SRAM access using NVMEM framework. Testing --- The test was done on a custom board which contains a DS3232

Re: [PATCH v3 19/36] thunderbolt: Extend tunnel creation to more than 2 adjacent switches

On Mon, Apr 08, 2019 at 10:35:17AM +0300, Mika Westerberg wrote: > On Sun, Apr 07, 2019 at 06:54:25PM +0200, Lukas Wunner wrote: > > According to the code comment in struct tb_regs_hop (in tb_regs.h), > > the out_hopid ("next_hop" in struct tb_regs_hop) denotes the > > "hop to take after sending

Re: [PATCH v3 8/9] soc: qcom: rpmpd: Add MSM8998 power-domains

On 08/04/2019 10:30, Sibi Sankar wrote: > On 2019-04-05 20:38, Marc Gonzalez wrote: >> On 27/03/2019 13:38, Sibi Sankar wrote: >> >>> Add the shared cx/mx and sensor sub-system's cx and mx >>> power-domains found on MSM8998. >>> >>> Signed-off-by: Sibi Sankar >>> --- >>> drivers/soc/qcom/rpmpd.c

[PATCH] tools/power turbostat: fix leak of file descriptor on error return path

From: Colin Ian King Currently the error return path does not close the file fp and leaks a file descriptor. Fix this by closing the file. Fixes: 5ea7647b333f ("tools/power turbostat: Warn on bad ACPI LPIT data") Signed-off-by: Colin Ian King --- tools/power/x86/turbostat/turbostat.c | 1 + 1

Re: [PATCH v3 8/9] soc: qcom: rpmpd: Add MSM8998 power-domains

Hey Marc, Thanks for the review! On 2019-04-08 14:24, Marc Gonzalez wrote: On 08/04/2019 10:30, Sibi Sankar wrote: On 2019-04-05 20:38, Marc Gonzalez wrote: On 27/03/2019 13:38, Sibi Sankar wrote: Add the shared cx/mx and sensor sub-system's cx and mx power-domains found on MSM8998.

Re: Regression in suspend-to-ram (TPM related) with 5.1-rc1 (BISECTED)

On 08.04.19 08:59, Paul Zimmerman wrote: > On Sun, Apr 7, 2019 at 10:53 PM Martin Kepplinger > wrote: >> >> On 21.03.19 14:41, Jarkko Sakkinen wrote: >>> On Tue, Mar 19, 2019 at 04:03:37PM -0700, Paul Zimmerman wrote: So I bisected this down to: # first bad commit:

Re: [PATCH v3 19/36] thunderbolt: Extend tunnel creation to more than 2 adjacent switches

On Mon, Apr 08, 2019 at 10:53:37AM +0200, Lukas Wunner wrote: > Hm, what other cases are there, i.e. what is the meaning of a tb_regs_hop's > "next_hop" field if "out_port" doesn't have a remote? (And why does it > need to be tracked on the out_port? In case a remote is added later?) We also

[PATCH -v5] x86/kvm: Implement HWCR support

Hi all, here's v5 which keeps the HWCR functionality in kvm/x86.c so that emulation of AMD guests on Intel hw still can work. -- From: Borislav Petkov The AMD hardware configuration register has some useful bits which can be used by guests. Implement McStatusWrEn which can be used by guests

Re: [PATCH 1/4] rtc: coh901331: set range

On Sun, Apr 7, 2019 at 11:10 PM Alexandre Belloni wrote: > The COH 901 331 is a 32bit seconds counter. > > Signed-off-by: Alexandre Belloni Acked-by: Linus Walleij Yours, Linus Walleij

Re: [PATCH v5 2/7] drm/panel: simple: Add ability to override typical timing

On Mon, 1 Apr 2019 10:17:19 -0700 Douglas Anderson wrote: > From: Sean Paul > > This patch adds the ability to override the typical display timing for a > given panel. This is useful for devices which have timing constraints > that do not apply across the entire display driver (eg: to avoid >

Re: [PATCH 2/4] rtc: coh901331: switch to rtc_time64_to_tm/rtc_tm_to_time64

On Sun, Apr 7, 2019 at 11:10 PM Alexandre Belloni wrote: > Call the 64bit versions of rtc_tm time conversion now that the range is > enforced by the core. > > Signed-off-by: Alexandre Belloni Acked-by: Linus Walleij Yours, Linus Walleij

Re: [PATCH 3/4] rtc: coh901331: use .set_time

On Sun, Apr 7, 2019 at 11:10 PM Alexandre Belloni wrote: > Use .set_time instead of the deprecated .set_mmss. > > Signed-off-by: Alexandre Belloni Acked-by: Linus Walleij Yours, Linus Walleij

  1   2   3   4   5   6   7   8   >