Re: [RFC patch 3/7] printk: Use clock MONOTONIC for timestamps

Hello Thomas, On (11/15/17 19:15), Thomas Gleixner wrote: > local_clock() cannot be reliably correlated to CLOCK_MONOTONIC, which is > used by user space, e.g. systemd, to create correlation timestamps. > > There are multiple reasons: > > - CLOCK_MONOTONIC is NTP adjusted, local_clock() not.

Re: [RFC patch 3/7] printk: Use clock MONOTONIC for timestamps

Hello Thomas, On (11/15/17 19:15), Thomas Gleixner wrote: > local_clock() cannot be reliably correlated to CLOCK_MONOTONIC, which is > used by user space, e.g. systemd, to create correlation timestamps. > > There are multiple reasons: > > - CLOCK_MONOTONIC is NTP adjusted, local_clock() not.

Re: [PATCH] s390/ap_bus: Convert timers to use timer_setup()

On Thu, Nov 2, 2017 at 11:29 PM, Martin Schwidefsky wrote: > On Thu, 2 Nov 2017 16:36:53 -0700 > Kees Cook wrote: > >> On Wed, Oct 25, 2017 at 11:38 PM, Martin Schwidefsky >> wrote: >> > On Wed, 25 Oct 2017 03:27:37 -0700 >>

Re: [PATCH] s390/ap_bus: Convert timers to use timer_setup()

On Thu, Nov 2, 2017 at 11:29 PM, Martin Schwidefsky wrote: > On Thu, 2 Nov 2017 16:36:53 -0700 > Kees Cook wrote: > >> On Wed, Oct 25, 2017 at 11:38 PM, Martin Schwidefsky >> wrote: >> > On Wed, 25 Oct 2017 03:27:37 -0700 >> > Kees Cook wrote: >> > >> >> In preparation for unconditionally

[PATCH] kbuild: define KBUILD_MODNAME even if multiple modules share objects

Currently, KBUILD_MODNAME is defined only when $(modname) contains just one word. If an object is shared between multiple modules, undefined KBUILD_MODNAME causes a build error. A simple test case is as follows: obj-m += foo.o obj-m += bar.o foo-objs := foo-bar-common.o foo-main.o

[PATCH 04/10] x86: jailhouse: Enable PMTIMER

From: Jan Kiszka Jailhouse exposes the PMTIMER as only reference clock to all cells. Pick up its address from the setup data. Allow to enable the Linux support of it by relaxing its strict dependency on ACPI. Signed-off-by: Jan Kiszka ---

[PATCH] kbuild: define KBUILD_MODNAME even if multiple modules share objects

Currently, KBUILD_MODNAME is defined only when $(modname) contains just one word. If an object is shared between multiple modules, undefined KBUILD_MODNAME causes a build error. A simple test case is as follows: obj-m += foo.o obj-m += bar.o foo-objs := foo-bar-common.o foo-main.o

[PATCH 04/10] x86: jailhouse: Enable PMTIMER

From: Jan Kiszka Jailhouse exposes the PMTIMER as only reference clock to all cells. Pick up its address from the setup data. Allow to enable the Linux support of it by relaxing its strict dependency on ACPI. Signed-off-by: Jan Kiszka --- arch/x86/Kconfig| 1 +

[PATCH 07/10] x86: jailhouse: Silence ACPI warning

From: Jan Kiszka Jailhouse support does not depend on ACPI, and does not even use it. But if it should be enabled, avoid warning about its absence in the platform. Signed-off-by: Jan Kiszka --- arch/x86/kernel/jailhouse.c | 6 ++ 1 file

[PATCH 09/10] x86: jailhouse: Wire up IOAPIC for legacy UART ports

From: Jan Kiszka The typical I/O interrupts in non-root cells are MSI-based. However, the platform UARTs do not support MSI. In order to run a non-root cell that shall be use one of them, we need to register the standard IOAPIC and set 1:1 routing for IRQ 3 and 4. If an

[PATCH 07/10] x86: jailhouse: Silence ACPI warning

From: Jan Kiszka Jailhouse support does not depend on ACPI, and does not even use it. But if it should be enabled, avoid warning about its absence in the platform. Signed-off-by: Jan Kiszka --- arch/x86/kernel/jailhouse.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH 09/10] x86: jailhouse: Wire up IOAPIC for legacy UART ports

From: Jan Kiszka The typical I/O interrupts in non-root cells are MSI-based. However, the platform UARTs do not support MSI. In order to run a non-root cell that shall be use one of them, we need to register the standard IOAPIC and set 1:1 routing for IRQ 3 and 4. If an IOAPIC is not available,

[PATCH 05/10] x86: jailhouse: Set up timekeeping

From: Jan Kiszka Calibrate the TSC and, where necessary, the APIC timer against the TMTIMER. We need our own implementation as neither the PIC nor the HPET are available, and the standard calibration routines try to make use of them. Signed-off-by: Jan Kiszka

[PATCH 05/10] x86: jailhouse: Set up timekeeping

From: Jan Kiszka Calibrate the TSC and, where necessary, the APIC timer against the TMTIMER. We need our own implementation as neither the PIC nor the HPET are available, and the standard calibration routines try to make use of them. Signed-off-by: Jan Kiszka --- arch/x86/include/asm/tsc.h |

[PATCH 01/10] x86/apic: Install an empty physflat_init_apic_ldr

From: Jan Kiszka As the comment already stated, there is no need for setting up LDR in physflat mode as it remains unused. flat_init_apic_ldr only served as a placeholder for a nop operation so far, causing no harm. That will change when running over the Jailhouse

[PATCH 01/10] x86/apic: Install an empty physflat_init_apic_ldr

From: Jan Kiszka As the comment already stated, there is no need for setting up LDR in physflat mode as it remains unused. flat_init_apic_ldr only served as a placeholder for a nop operation so far, causing no harm. That will change when running over the Jailhouse hypervisor. Here we must not

[PATCH 03/10] x86: jailhouse: Enable APIC and SMP support

From: Jan Kiszka Register the APIC which Jailhouse always exposes at 0xfee0 if in xAPIC mode or via MSRs as x2APIC. The latter is only available if it was already activated because there is no virtualization to switch its mode during runtime. Jailhouse requires the

[PATCH 03/10] x86: jailhouse: Enable APIC and SMP support

From: Jan Kiszka Register the APIC which Jailhouse always exposes at 0xfee0 if in xAPIC mode or via MSRs as x2APIC. The latter is only available if it was already activated because there is no virtualization to switch its mode during runtime. Jailhouse requires the APIC to be operated in

[PATCH V1 2/4] usb: serial: f81534: add auto RTS direction support

The F81532/534 had auto RTS direction support for RS485 mode. We'll read it from internal Flash with address 0x2f01~0x2f04 for 4 ports. There are 4 conditions below: 0: F81534_PORT_CONF_RS232. 1: F81534_PORT_CONF_RS485. 2: value error, default to F81534_PORT_CONF_RS232.

[PATCH 10/10] x86: jailhouse: Initialize PCI support

From: Jan Kiszka With this change, PCI devices can be detected and used inside a non-root cell. Signed-off-by: Jan Kiszka --- arch/x86/kernel/jailhouse.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/x86/kernel/jailhouse.c

[PATCH V1 2/4] usb: serial: f81534: add auto RTS direction support

The F81532/534 had auto RTS direction support for RS485 mode. We'll read it from internal Flash with address 0x2f01~0x2f04 for 4 ports. There are 4 conditions below: 0: F81534_PORT_CONF_RS232. 1: F81534_PORT_CONF_RS485. 2: value error, default to F81534_PORT_CONF_RS232.

[PATCH 10/10] x86: jailhouse: Initialize PCI support

From: Jan Kiszka With this change, PCI devices can be detected and used inside a non-root cell. Signed-off-by: Jan Kiszka --- arch/x86/kernel/jailhouse.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/x86/kernel/jailhouse.c b/arch/x86/kernel/jailhouse.c index

[PATCH V1 4/4] usb: serial: f81534: add H/W disable port support

The F81532/534 can be disable port by manufacturer with following H/W design. 1: Connect DCD/DSR/CTS/RI pin to ground. 2: Connect RX pin to ground. In driver, we'll implements some detect method likes following: 1: Read MSR. 2: Turn MCR LOOP bit on, off and read LSR after delay

[PATCH V1 4/4] usb: serial: f81534: add H/W disable port support

The F81532/534 can be disable port by manufacturer with following H/W design. 1: Connect DCD/DSR/CTS/RI pin to ground. 2: Connect RX pin to ground. In driver, we'll implements some detect method likes following: 1: Read MSR. 2: Turn MCR LOOP bit on, off and read LSR after delay

[PATCH V1 1/4] usb: serial: f81534: add high baud rate support

The F81532/534 had 4 clocksource 1.846/18.46/14.77/24MHz and baud rates can be up to 1.5Mbits with 24MHz. F81532/534 Clock register (offset +08h) Bit0: UART Enable (always on) Bit2-1: Clock source selector 00: 1.846MHz. 01: 18.46MHz.

[PATCH V1 1/4] usb: serial: f81534: add high baud rate support

The F81532/534 had 4 clocksource 1.846/18.46/14.77/24MHz and baud rates can be up to 1.5Mbits with 24MHz. F81532/534 Clock register (offset +08h) Bit0: UART Enable (always on) Bit2-1: Clock source selector 00: 1.846MHz. 01: 18.46MHz.

[PATCH V1 3/4] usb: serial: f81534: add output pin control

The F81532/534 had 3 output pin (M0/SD, M1, M2) with open-drain mode to control transceiver. We'll read it from internal Flash with address 0x2f05~0x2f08 for 4 ports. The value is range from 0 to 7. The M0/SD is MSB of this value. For a examples, If read value is 6, we'll write M0/SD, M1, M2 as 1,

[PATCH V1 3/4] usb: serial: f81534: add output pin control

The F81532/534 had 3 output pin (M0/SD, M1, M2) with open-drain mode to control transceiver. We'll read it from internal Flash with address 0x2f05~0x2f08 for 4 ports. The value is range from 0 to 7. The M0/SD is MSB of this value. For a examples, If read value is 6, we'll write M0/SD, M1, M2 as 1,

Re: [GIT PULL] usercopy whitelisting for v4.15-rc1

On Sun, Nov 12, 2017 at 11:29 PM, Kees Cook wrote: > Please pull these hardened usercopy whitelisting changes for v4.15-rc1. > This significantly narrows the areas of memory that can be copied to/from > userspace in the face of usercopy bugs. Just wanted to make sure this

Re: [GIT PULL] usercopy whitelisting for v4.15-rc1

On Sun, Nov 12, 2017 at 11:29 PM, Kees Cook wrote: > Please pull these hardened usercopy whitelisting changes for v4.15-rc1. > This significantly narrows the areas of memory that can be copied to/from > userspace in the face of usercopy bugs. Just wanted to make sure this pull request was still

[PATCH 02/10] x86: jailhouse: Add infrastructure for running in non-root cell

From: Jan Kiszka The Jailhouse hypervisor is able to statically partition a multicore system into multiple so-called cells. Linux is used as boot loader and continues to run in the root cell after Jailhouse is enabled. Linux can also run in non-root cells. Jailhouse does

[PATCH 02/10] x86: jailhouse: Add infrastructure for running in non-root cell

From: Jan Kiszka The Jailhouse hypervisor is able to statically partition a multicore system into multiple so-called cells. Linux is used as boot loader and continues to run in the root cell after Jailhouse is enabled. Linux can also run in non-root cells. Jailhouse does not emulate usual x86

[PATCH 06/10] x86: jailhouse: Avoid access of unsupported platform resources

From: Jan Kiszka We don't have CMOS access, thus we can't set the warm-reset vectors in do_boot_cpu. There is no RTC, thus also no wall clock. Furthermore, there are no ISA IRQs and no PIC. So fill the platform callbacks accordingly. Signed-off-by: Jan Kiszka

Re: [PATCH] locking/Documentation: Revise Documentation/locking/crossrelease.txt

On 11/16/2017 4:22 PM, Ingo Molnar wrote: * Byungchul Park wrote: On Sat, Nov 11, 2017 at 10:45:24PM +0900, Byungchul Park wrote: This is the big one including all of version 3. You can take only this. Hello Ingo, Could you consider this? Yeah, I'll have a look

Re: [PATCH] locking/Documentation: Revise Documentation/locking/crossrelease.txt

On 11/16/2017 4:22 PM, Ingo Molnar wrote: * Byungchul Park wrote: On Sat, Nov 11, 2017 at 10:45:24PM +0900, Byungchul Park wrote: This is the big one including all of version 3. You can take only this. Hello Ingo, Could you consider this? Yeah, I'll have a look in a few days, but

[PATCH 06/10] x86: jailhouse: Avoid access of unsupported platform resources

From: Jan Kiszka We don't have CMOS access, thus we can't set the warm-reset vectors in do_boot_cpu. There is no RTC, thus also no wall clock. Furthermore, there are no ISA IRQs and no PIC. So fill the platform callbacks accordingly. Signed-off-by: Jan Kiszka --- arch/x86/kernel/jailhouse.c |

[PATCH 00/10] x86: Add support for running as secondary Jailhouse guest

This series paves the way to run Linux in so-called non-root cells (guest partitions) of the Jailhouse hypervisor. Jailhouse [1] was started 4 years ago as an open-source (GPL) leight- weight hypervisor that statically partitions SMP systems. It's unique in that it uses one Linux instance, the

[PATCH 00/10] x86: Add support for running as secondary Jailhouse guest

This series paves the way to run Linux in so-called non-root cells (guest partitions) of the Jailhouse hypervisor. Jailhouse [1] was started 4 years ago as an open-source (GPL) leight- weight hypervisor that statically partitions SMP systems. It's unique in that it uses one Linux instance, the

[PATCH 08/10] x86: jailhouse: Halt instead of failing to restart

From: Jan Kiszka Jailhouse provides no guest-initiated restart. So, do not even try to. Signed-off-by: Jan Kiszka --- arch/x86/kernel/jailhouse.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/x86/kernel/jailhouse.c

[PATCH 08/10] x86: jailhouse: Halt instead of failing to restart

From: Jan Kiszka Jailhouse provides no guest-initiated restart. So, do not even try to. Signed-off-by: Jan Kiszka --- arch/x86/kernel/jailhouse.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/x86/kernel/jailhouse.c b/arch/x86/kernel/jailhouse.c index

[current linus git] kernel warning : driver forgot to call drm_crtc_vblank_off()

Hi, I'm running current linus git kernel on VMWare Workstation 12 Pro (Host : windows 10, Guest : Fedora 27). commit e60e1ee60630cafef5e430c2ae364877e061d980 : Merge tag 'drm-for-v4.15' of git://people.freedesktop.org/~airlied/linux) When I login via Gnome GDM login screen, following

Re: [RESEND PATCH] ARM: dts: ls1021a: Add support for QSPI with ls1021a SoC

On Wed, Oct 25, 2017 at 04:00:36PM -0500, Li Yang wrote: > On Tue, Sep 12, 2017 at 1:49 AM, SZ Lin wrote: > > Add QSPI node support, and this function is disabled by default > > This setting could be overwritten in board-level definitions > > Adding Shawn Guo. > > > > >

[current linus git] kernel warning : driver forgot to call drm_crtc_vblank_off()

Hi, I'm running current linus git kernel on VMWare Workstation 12 Pro (Host : windows 10, Guest : Fedora 27). commit e60e1ee60630cafef5e430c2ae364877e061d980 : Merge tag 'drm-for-v4.15' of git://people.freedesktop.org/~airlied/linux) When I login via Gnome GDM login screen, following

Re: [RESEND PATCH] ARM: dts: ls1021a: Add support for QSPI with ls1021a SoC

On Wed, Oct 25, 2017 at 04:00:36PM -0500, Li Yang wrote: > On Tue, Sep 12, 2017 at 1:49 AM, SZ Lin wrote: > > Add QSPI node support, and this function is disabled by default > > This setting could be overwritten in board-level definitions > > Adding Shawn Guo. > > > > > Signed-off-by: SZ Lin >

Re: [PATCH] coccinelle: flags.cocci: reorganize patterns to improve efficiency

On Wed, 15 Nov 2017, Joe Perches wrote: > On Wed, 2017-11-15 at 22:55 +0100, Julia Lawall wrote: > > What version of Coccinelle do you have? > > > I tried 1.0.4 and 1.0.6, > > > but both failed. > > For me, it also fails for 1.0.6. It should be OK for 1.0.7. > > Then likely this patch should

Re: [PATCH] coccinelle: flags.cocci: reorganize patterns to improve efficiency

On Wed, 15 Nov 2017, Joe Perches wrote: > On Wed, 2017-11-15 at 22:55 +0100, Julia Lawall wrote: > > What version of Coccinelle do you have? > > > I tried 1.0.4 and 1.0.6, > > > but both failed. > > For me, it also fails for 1.0.6. It should be OK for 1.0.7. > > Then likely this patch should

RE: [PATCH] Input: ALPS - fix DualPoint flag for 74 03 28 devices

Hi, Pali, Aaron, Current code is correct device setting, previous code is wrong. If the trackstick does not work(DUALPOINT flag disable), Device Firmware setting is wrong. But recently I received the same report from Thinkpad L570 user, and I checked this device and found this device Firmware

RE: [PATCH] Input: ALPS - fix DualPoint flag for 74 03 28 devices

Hi, Pali, Aaron, Current code is correct device setting, previous code is wrong. If the trackstick does not work(DUALPOINT flag disable), Device Firmware setting is wrong. But recently I received the same report from Thinkpad L570 user, and I checked this device and found this device Firmware

Re: [PATCH] arm: Remove unused __readwrite_bug function

On Wed, Nov 15, 2017 at 07:33:22PM +, Corentin Labbe wrote: > The function __readwrite_bug() is not used at all, so this patch remove > it. This function seems unused since 5621caac1d95 ("ARM: kill off __mem_pci"). Adding Rob as author to Cc. Best regards Uwe > Signed-off-by: Corentin Labbe

Re: [PATCH] arm: Remove unused __readwrite_bug function

On Wed, Nov 15, 2017 at 07:33:22PM +, Corentin Labbe wrote: > The function __readwrite_bug() is not used at all, so this patch remove > it. This function seems unused since 5621caac1d95 ("ARM: kill off __mem_pci"). Adding Rob as author to Cc. Best regards Uwe > Signed-off-by: Corentin Labbe

Re: [PATCH] locking/Documentation: Revise Documentation/locking/crossrelease.txt

* Byungchul Park wrote: > On Sat, Nov 11, 2017 at 10:45:24PM +0900, Byungchul Park wrote: > > This is the big one including all of version 3. > > > > You can take only this. > > Hello Ingo, > > Could you consider this? Yeah, I'll have a look in a few days, but right

Re: [PATCH] locking/Documentation: Revise Documentation/locking/crossrelease.txt

* Byungchul Park wrote: > On Sat, Nov 11, 2017 at 10:45:24PM +0900, Byungchul Park wrote: > > This is the big one including all of version 3. > > > > You can take only this. > > Hello Ingo, > > Could you consider this? Yeah, I'll have a look in a few days, but right now we are in the middle

Re: [PATCH V13 03/10] mmc: block: Add blk-mq support

On 15 November 2017 at 14:07, Adrian Hunter wrote: > On 15/11/17 12:55, Ulf Hansson wrote: >> Linus, Adrian, >> >> Apologize for sidetracking the discussion, just wanted to add some >> minor comments. >> >> [...] >> >>> > But what I think is nice in doing it around

Re: [PATCH V13 03/10] mmc: block: Add blk-mq support

On 15 November 2017 at 14:07, Adrian Hunter wrote: > On 15/11/17 12:55, Ulf Hansson wrote: >> Linus, Adrian, >> >> Apologize for sidetracking the discussion, just wanted to add some >> minor comments. >> >> [...] >> >>> > But what I think is nice in doing it around > each request is that

[PATCH] soc: qcom: smp2p: Access APCS as mailbox client

Attempt to acquire the APCS IPC through the mailbox framework and fall back to the old syscon based approach, to allow us to move away from using the syscon. Signed-off-by: Bjorn Andersson --- drivers/soc/qcom/Kconfig | 1 + drivers/soc/qcom/smp2p.c | 38

[PATCH] soc: qcom: smp2p: Access APCS as mailbox client

Attempt to acquire the APCS IPC through the mailbox framework and fall back to the old syscon based approach, to allow us to move away from using the syscon. Signed-off-by: Bjorn Andersson --- drivers/soc/qcom/Kconfig | 1 + drivers/soc/qcom/smp2p.c | 38 --

Re: [PATCH] mac80211: mwl8k: Expand non-DFS 5G channels

Weixiao Zhang writes: > Signed-off-by: Weixiao Zhang No empty commit logs, please. And use v2, v3 to clearly mark what's the version of the patch: https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#patch_version_missing

Re: [PATCH] mac80211: mwl8k: Expand non-DFS 5G channels

Weixiao Zhang writes: > Signed-off-by: Weixiao Zhang No empty commit logs, please. And use v2, v3 to clearly mark what's the version of the patch: https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#patch_version_missing > drivers/net/wireless/marvell/mwl8k.c | 7

Re: [GIT pull] printk updates for 4.15

On Wed, 15 Nov 2017, Linus Torvalds wrote: > On Wed, Nov 15, 2017 at 4:37 PM, Thomas Gleixner wrote: > > > > This broke stuff because the historic behaviour was to not advance on > > resume and the change caused massive timer expiries right after resume > > which confused the

Re: [GIT pull] printk updates for 4.15

On Wed, 15 Nov 2017, Linus Torvalds wrote: > On Wed, Nov 15, 2017 at 4:37 PM, Thomas Gleixner wrote: > > > > This broke stuff because the historic behaviour was to not advance on > > resume and the change caused massive timer expiries right after resume > > which confused the hell out of things,

Re: [ANNOUNCE] Call for Papers - linux.conf.au Kernel Miniconf, Sydney, 22 January 2018

On 18/10/17 15:34, Andrew Donnellan wrote: Greetings, * TL;DR     - LCA Kernel Miniconf, Sydney, Australia, 22 Jan 2018     - Submissions by 30 November 2017, 23:59 (AEDT/UTC+11)     - Wanted: anything interesting to kernel hackers! Speakers from   diverse backgrounds

Re: [ANNOUNCE] Call for Papers - linux.conf.au Kernel Miniconf, Sydney, 22 January 2018

On 18/10/17 15:34, Andrew Donnellan wrote: Greetings, * TL;DR     - LCA Kernel Miniconf, Sydney, Australia, 22 Jan 2018     - Submissions by 30 November 2017, 23:59 (AEDT/UTC+11)     - Wanted: anything interesting to kernel hackers! Speakers from   diverse backgrounds

[PATCH] rpmsg: qcom_smd: Access APCS through mailbox framework

Attempt to acquire the APCS IPC through the mailbox framework and fall back to the old syscon based approach, to allow us to move away from using the syscon. Signed-off-by: Bjorn Andersson --- drivers/rpmsg/qcom_smd.c | 62

[PATCH] rpmsg: qcom_smd: Access APCS through mailbox framework

Attempt to acquire the APCS IPC through the mailbox framework and fall back to the old syscon based approach, to allow us to move away from using the syscon. Signed-off-by: Bjorn Andersson --- drivers/rpmsg/qcom_smd.c | 62 +--- 1 file changed, 43

Re: [PATCH v5 1/2] x86/mm: add a function to check if a pfn is UC/UC-

On 11/15/17 11:44 +0100, David Hildenbrand wrote: > On 08.11.2017 08:56, Haozhong Zhang wrote: > > It will be used by KVM to check whether a pfn should be > > mapped to guest as UC. > > > > Signed-off-by: Haozhong Zhang > > --- > > arch/x86/include/asm/pat.h | 2 ++ >

Re: [PATCH v5 1/2] x86/mm: add a function to check if a pfn is UC/UC-

On 11/15/17 11:44 +0100, David Hildenbrand wrote: > On 08.11.2017 08:56, Haozhong Zhang wrote: > > It will be used by KVM to check whether a pfn should be > > mapped to guest as UC. > > > > Signed-off-by: Haozhong Zhang > > --- > > arch/x86/include/asm/pat.h | 2 ++ > > arch/x86/mm/pat.c

Re: [PATCH v2] arm64: dts: ls1088a: Add USB support

On Tue, Nov 14, 2017 at 08:00:00AM +, Yinbo Zhu wrote: > On Wed, Sep 13, 2017 at 05:10:09PM +0800, yinbo@nxp.com wrote: > > From: "yinbo.zhu" > > > > Fix the issue that usb is not detected on ls1088ardb > > >It's not really about fixing issue but adding support. > >

Re: [PATCH v2] arm64: dts: ls1088a: Add USB support

On Tue, Nov 14, 2017 at 08:00:00AM +, Yinbo Zhu wrote: > On Wed, Sep 13, 2017 at 05:10:09PM +0800, yinbo@nxp.com wrote: > > From: "yinbo.zhu" > > > > Fix the issue that usb is not detected on ls1088ardb > > >It's not really about fixing issue but adding support. > > The patch had been

Re: [project-aspen-dev] Re: [PATCH 1/3] clk: hisilicon: add hisi phase clock support

On Thu, Nov 16, 2017 at 11:40:18AM +0800, Jiancheng Xue wrote: > >> +struct clk_hisi_phase { > >> + struct clk_hw hw; > >> + void __iomem*reg; > >> + u32 *phase_values; > >> + u32 *phase_regs; > >> + u8 phase_num; > > > > I do not think this

Re: [project-aspen-dev] Re: [PATCH 1/3] clk: hisilicon: add hisi phase clock support

On Thu, Nov 16, 2017 at 11:40:18AM +0800, Jiancheng Xue wrote: > >> +struct clk_hisi_phase { > >> + struct clk_hw hw; > >> + void __iomem*reg; > >> + u32 *phase_values; > >> + u32 *phase_regs; > >> + u8 phase_num; > > > > I do not think this

RE: [patches] Re: [PATCH v9 05/12] RISC-V: Atomic and Locking Code

> > In that case, maybe we should just start out having a fence on both > > sides for > > Actually, given your architecture is RCsc rather than RCpc, so I think maybe > you could follow the way that ARM uses(i.e. relaxed load + release store + a > full barrier). You can see the commit log of

RE: [patches] Re: [PATCH v9 05/12] RISC-V: Atomic and Locking Code

> > In that case, maybe we should just start out having a fence on both > > sides for > > Actually, given your architecture is RCsc rather than RCpc, so I think maybe > you could follow the way that ARM uses(i.e. relaxed load + release store + a > full barrier). You can see the commit log of

[PATCH] drivers/perf: arm_pmu: save/restore cpu cycle counter in cpu_pm_pmu_notify

Sometimes userspace need a high resolution cycle counter by reading pmccntr_el0. In commit da4e4f18afe0 ("drivers/perf: arm_pmu: implement CPU_PM notifier"), it resets all the counters even when the pmcr_el0.E and pmcntenset_el0.C are both 1 . That is incorrect. We need to save the registers and

[PATCH] drivers/perf: arm_pmu: save/restore cpu cycle counter in cpu_pm_pmu_notify

Sometimes userspace need a high resolution cycle counter by reading pmccntr_el0. In commit da4e4f18afe0 ("drivers/perf: arm_pmu: implement CPU_PM notifier"), it resets all the counters even when the pmcr_el0.E and pmcntenset_el0.C are both 1 . That is incorrect. We need to save the registers and

Re: PROBLEM: Asus C201 video mode problems on HDMI hotplug (regression)

Hi, Any ideas on this issue? Are there any additional tests I can perform to help debug this? On 2017-11-05 11:41 -0500, Nick Bowler wrote: > I completed bisecting this issue. See below. > > On 2017-11-02, Nick Bowler wrote: > > ~50% of the time after a hotplug, there is

Re: PROBLEM: Asus C201 video mode problems on HDMI hotplug (regression)

Hi, Any ideas on this issue? Are there any additional tests I can perform to help debug this? On 2017-11-05 11:41 -0500, Nick Bowler wrote: > I completed bisecting this issue. See below. > > On 2017-11-02, Nick Bowler wrote: > > ~50% of the time after a hotplug, there is a vertical pink bar

[PATCH] arm64: defconfig: Select schedutil as default cpufreq governor

Currently performance governor is getting selected by default, which is surely not a very good choice as its pretty much power hungry. Select schedutil instead. Signed-off-by: Viresh Kumar --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff

[PATCH] arm64: defconfig: Select schedutil as default cpufreq governor

Currently performance governor is getting selected by default, which is surely not a very good choice as its pretty much power hungry. Select schedutil instead. Signed-off-by: Viresh Kumar --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH] soc: qcom: smsm: fix child-node lookup

On Wed 15 Nov 03:07 PST 2017, Johan Hovold wrote: > Fix child-node lookup during probe, which ended up searching the whole > device tree depth-first starting at the parent rather than just matching > on its children. > > Note that the original premature free of the parent node has already > been

Re: [PATCH] soc: qcom: smsm: fix child-node lookup

On Wed 15 Nov 03:07 PST 2017, Johan Hovold wrote: > Fix child-node lookup during probe, which ended up searching the whole > device tree depth-first starting at the parent rather than just matching > on its children. > > Note that the original premature free of the parent node has already > been

[PATCHi v2] dt-bindings: add device tree binding for Arm TrustZone CryptoCell crypto engine

The Arm TrustZone CryptoCell is a hardware security engine. This patch adds DT bindings for its Rich Execution Environment crypto engine. A driver supporting this device is already present in the staging tree. Signed-off-by: Gilad Ben-Yossef Acked-by: Rob Herring

[PATCHi v2] dt-bindings: add device tree binding for Arm TrustZone CryptoCell crypto engine

The Arm TrustZone CryptoCell is a hardware security engine. This patch adds DT bindings for its Rich Execution Environment crypto engine. A driver supporting this device is already present in the staging tree. Signed-off-by: Gilad Ben-Yossef Acked-by: Rob Herring --- Changes from v1: - Change

Re: [PATCH v5 1/2] x86/mm: add a function to check if a pfn is UC/UC-

On 11/15/17 07:17 -0800, Dan Williams wrote: > On Tue, Nov 7, 2017 at 11:56 PM, Haozhong Zhang > wrote: > > It will be used by KVM to check whether a pfn should be > > mapped to guest as UC. > > > > Signed-off-by: Haozhong Zhang > > --- > >

Re: [PATCH v5 1/2] x86/mm: add a function to check if a pfn is UC/UC-

On 11/15/17 07:17 -0800, Dan Williams wrote: > On Tue, Nov 7, 2017 at 11:56 PM, Haozhong Zhang > wrote: > > It will be used by KVM to check whether a pfn should be > > mapped to guest as UC. > > > > Signed-off-by: Haozhong Zhang > > --- > > arch/x86/include/asm/pat.h | 2 ++ > >

[PATCH] rpmsg: qcom: The mbox clients knows_txdone

As both the GLINK and SMD drivers are ticking the txdone of the mailbox (to implement the doorbell) they should set knows_txdone. Signed-off-by: Bjorn Andersson --- drivers/rpmsg/qcom_glink_native.c | 1 + drivers/rpmsg/qcom_smd.c | 1 + 2 files changed, 2

[PATCH] rpmsg: qcom: The mbox clients knows_txdone

As both the GLINK and SMD drivers are ticking the txdone of the mailbox (to implement the doorbell) they should set knows_txdone. Signed-off-by: Bjorn Andersson --- drivers/rpmsg/qcom_glink_native.c | 1 + drivers/rpmsg/qcom_smd.c | 1 + 2 files changed, 2 insertions(+) diff --git

Re: [PATCH 2/2] drm/rockchip: vop: add rk3126 vop support

On 2017年11月14日 19:27, Sandy Huang wrote: RK3126 vop register layout is similar with rk3036, so some feature can reuse with rk3036. RK3126 support two overlay plane and one hwc plane, max output resolution is 1080p. it support IOMMU, and its IOMMU same as rk3288's Signed-off-by: Sandy Huang

Re: [PATCH 2/2] drm/rockchip: vop: add rk3126 vop support

On 2017年11月14日 19:27, Sandy Huang wrote: RK3126 vop register layout is similar with rk3036, so some feature can reuse with rk3036. RK3126 support two overlay plane and one hwc plane, max output resolution is 1080p. it support IOMMU, and its IOMMU same as rk3288's Signed-off-by: Sandy Huang

Re: [PATCH 2/2] drm/rockchip: vop: add rk3126 vop support

On 2017年11月14日 19:27, Sandy Huang wrote: RK3126 vop register layout is similar with rk3036, so some feature can reuse with rk3036. RK3126 support two overlay plane and one hwc plane, max output resolution is 1080p. it support IOMMU, and its IOMMU same as rk3288's Signed-off-by: Sandy Huang

Re: [PATCH 2/2] drm/rockchip: vop: add rk3126 vop support

On 2017年11月14日 19:27, Sandy Huang wrote: RK3126 vop register layout is similar with rk3036, so some feature can reuse with rk3036. RK3126 support two overlay plane and one hwc plane, max output resolution is 1080p. it support IOMMU, and its IOMMU same as rk3288's Signed-off-by: Sandy Huang

[PATCH v2] rtc: Add tracepoints for RTC system

It will be more helpful to add some tracepoints to track RTC actions when debugging RTC driver. Below sample is that we set/read the RTC time, then set 2 alarms, so we can see the trace logs: set/read RTC time: kworker/0:1-67 [000] 21.814245: rtc_set_time: 2017-11-10 08:13:00 UTC (1510301580)

[PATCH v2] rtc: Add tracepoints for RTC system

It will be more helpful to add some tracepoints to track RTC actions when debugging RTC driver. Below sample is that we set/read the RTC time, then set 2 alarms, so we can see the trace logs: set/read RTC time: kworker/0:1-67 [000] 21.814245: rtc_set_time: 2017-11-10 08:13:00 UTC (1510301580)

Re: [PATCH 1/2] x86,kvm: move qemu/guest FPU switching out to vcpu_run

2017-11-15 22:40 GMT+08:00 Rik van Riel : > On Wed, 2017-11-15 at 12:33 +0800, Wanpeng Li wrote: >> 2017-11-15 11:03 GMT+08:00 Rik van Riel : >> > On Wed, 2017-11-15 at 08:47 +0800, Wanpeng Li wrote: >> > > 2017-11-15 5:54 GMT+08:00 : >> > > >

Re: [PATCH 1/2] x86,kvm: move qemu/guest FPU switching out to vcpu_run

2017-11-15 22:40 GMT+08:00 Rik van Riel : > On Wed, 2017-11-15 at 12:33 +0800, Wanpeng Li wrote: >> 2017-11-15 11:03 GMT+08:00 Rik van Riel : >> > On Wed, 2017-11-15 at 08:47 +0800, Wanpeng Li wrote: >> > > 2017-11-15 5:54 GMT+08:00 : >> > > > From: Rik van Riel >> > > > >> > > > Currently,

HELLO

-- Am Mr.Sare Ouedraogo. i work in one of the prime bank here in burkina faso, i want the bank to transfer the money left by our late customer is a foreigner from Korea. can you investment this money and also help the poor' the amount value at $13,300,000.00 (Thirteen Million Three Hundred

HELLO

-- Am Mr.Sare Ouedraogo. i work in one of the prime bank here in burkina faso, i want the bank to transfer the money left by our late customer is a foreigner from Korea. can you investment this money and also help the poor' the amount value at $13,300,000.00 (Thirteen Million Three Hundred

Re: [PATCH v3 1/5] soc: qcom: Introduce QMI encoder/decoder

On Wed 15 Nov 12:10 PST 2017, Bjorn Andersson wrote: > diff --git a/drivers/soc/qcom/qmi_encdec.c b/drivers/soc/qcom/qmi_encdec.c [..] > +void *qmi_encode_message(int type, unsigned int msg_id, size_t *len, > + unsigned int txn_id, struct qmi_elem_info *ei, > +

Re: [PATCH v3 1/5] soc: qcom: Introduce QMI encoder/decoder

On Wed 15 Nov 12:10 PST 2017, Bjorn Andersson wrote: > diff --git a/drivers/soc/qcom/qmi_encdec.c b/drivers/soc/qcom/qmi_encdec.c [..] > +void *qmi_encode_message(int type, unsigned int msg_id, size_t *len, > + unsigned int txn_id, struct qmi_elem_info *ei, > +

Re: [PATCH v5 2/4] KVM: X86: Add paravirt remote TLB flush

2017-11-13 18:01 GMT+08:00 Wanpeng Li : > From: Wanpeng Li > > Remote flushing api's does a busy wait which is fine in bare-metal > scenario. But with-in the guest, the vcpus might have been pre-empted > or blocked. In this scenario, the initator vcpu

[PATCH] mailbox: txdone_method shouldn't always be reset

A client that knows how to drive txdone would temporarily "upgrade" the method to TXDONE_BY_ACK. But with the introduction of commit 33cd7123ac0ba ("mailbox: reset txdone_method TXDONE_BY_POLL if client knows_txdone") there is no longer a distinction between a channel in "upgraded" state or a

  1   2   3   4   5   6   7   8   9   10   >