[PATCH V2 2/2] ARM: dts: am57xx-beagle-x15: Add support for rev B1

Latest update to the BeagleBoard-X15 platform (revision B1)[1] updates for allowing UHS SD cards to function with the split of supply to SD card from a dedicated LDO. As a result of this, AM57xx BeagleBoard-X15 now uses gpio2_30 instead of gpio6_28 for HDMI because HDMI_LS_OE should now be

[PATCH V2 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux configurations for erratum i869

Pinmuxing for DRA7x/AM57x family of processors need to be done in IO isolation as part of initial bootloader executed from SRAM. This is done as part of iodelay configuration sequence and is required due to the limitations introduced by erratum ID: i869[1] (IO Glitches can occur when changing IO

[PATCH V2 2/2] ARM: dts: am57xx-beagle-x15: Add support for rev B1

Latest update to the BeagleBoard-X15 platform (revision B1)[1] updates for allowing UHS SD cards to function with the split of supply to SD card from a dedicated LDO. As a result of this, AM57xx BeagleBoard-X15 now uses gpio2_30 instead of gpio6_28 for HDMI because HDMI_LS_OE should now be

[PATCH V2 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux configurations for erratum i869

Pinmuxing for DRA7x/AM57x family of processors need to be done in IO isolation as part of initial bootloader executed from SRAM. This is done as part of iodelay configuration sequence and is required due to the limitations introduced by erratum ID: i869[1] (IO Glitches can occur when changing IO

Re: [PATCH 1/4] Documentation: mmc: sdhci-of-arasan: Add clk_syscon as an optional one

On Fri, Sep 2, 2016 at 11:12 AM, Doug Anderson wrote: > Rob, > > On Fri, Sep 2, 2016 at 7:15 AM, Rob Herring wrote: >> On Mon, Aug 29, 2016 at 04:02:56PM +0800, Shawn Lin wrote: >>> We introduced soc-ctl-syscon to do several things, for instance, update

Re: [PATCH 1/4] Documentation: mmc: sdhci-of-arasan: Add clk_syscon as an optional one

On Fri, Sep 2, 2016 at 11:12 AM, Doug Anderson wrote: > Rob, > > On Fri, Sep 2, 2016 at 7:15 AM, Rob Herring wrote: >> On Mon, Aug 29, 2016 at 04:02:56PM +0800, Shawn Lin wrote: >>> We introduced soc-ctl-syscon to do several things, for instance, update >>> baseclk or update clkmul, etc. In

Re: [PATCH net-next 3/3] net: dsa: mv88e6xxx: make global2 code optional

Hi Andrew, Andrew Lunn writes: >> What do you think? > > I think the probe() needs to fail with a very obvious error message > saying you need to recompile your kernel with option XYZ enabled in > order to support this switch, when the optional stuff is not > optional... I

Re: [PATCH net-next 3/3] net: dsa: mv88e6xxx: make global2 code optional

Hi Andrew, Andrew Lunn writes: >> What do you think? > > I think the probe() needs to fail with a very obvious error message > saying you need to recompile your kernel with option XYZ enabled in > order to support this switch, when the optional stuff is not > optional... I agree. Does the

Re: [PATCH] IB/mlx5: Fix a parameter of find_first_bit

On 8/26/2016 1:16 AM, Christophe JAILLET wrote: > The 2nd parameter of 'find_first_bit' is the number of bits to search. > In this case, we are passing 'sizeof(tmp)' which is likely to be 4 or 8 > because 'tmp' is an 'unsigned long'. > > It is likely that the number of bits of 'tmp' was expected

Re: [PATCH] IB/mlx5: Fix a parameter of find_first_bit

On 8/26/2016 1:16 AM, Christophe JAILLET wrote: > The 2nd parameter of 'find_first_bit' is the number of bits to search. > In this case, we are passing 'sizeof(tmp)' which is likely to be 4 or 8 > because 'tmp' is an 'unsigned long'. > > It is likely that the number of bits of 'tmp' was expected

Re: [PATCH 1/2] IB/hfi1: Fix a parameter of find_first_bit.

On 8/27/2016 1:25 AM, Christophe JAILLET wrote: > Le 26/08/2016 à 15:35, Doug Ledford a écrit : >> On 8/26/2016 12:49 AM, Christophe JAILLET wrote: >>> The 2nd parameter of 'find_first_bit' is the number of bits to search. >>> In this case, we are passing 'sizeof(unsigned long)' which is likely to

Re: [PATCH 1/2] IB/hfi1: Fix a parameter of find_first_bit.

On 8/27/2016 1:25 AM, Christophe JAILLET wrote: > Le 26/08/2016 à 15:35, Doug Ledford a écrit : >> On 8/26/2016 12:49 AM, Christophe JAILLET wrote: >>> The 2nd parameter of 'find_first_bit' is the number of bits to search. >>> In this case, we are passing 'sizeof(unsigned long)' which is likely to

Re: [PATCH v3] iio: humidity: hdc100x: add triggered buffer support for HDC100X

se=auto for > convenience) to record what (public, well-known) commit your patch series was > built on] > [Check https://git-scm.com/docs/git-format-patch for more information] > > url: > https://github.com/0day-ci/linux/commits/Alison-Schofield/iio-humidity-hd

Re: [PATCH v3] iio: humidity: hdc100x: add triggered buffer support for HDC100X

ll-known) commit your patch series was > built on] > [Check https://git-scm.com/docs/git-format-patch for more information] > > url: > https://github.com/0day-ci/linux/commits/Alison-Schofield/iio-humidity-hdc100x-add-triggered-buffer-support-for-HDC100X/20160902-055115 > :

Re: [PATCH 3/4] KVM: x86: introduce get_kvmclock_ns

On Fri, Sep 02, 2016 at 06:57:10PM +0200, Paolo Bonzini wrote: > > > On 02/09/2016 18:55, Roman Kagan wrote: > >> > I'll change patch 4 to store the parameters and use them when accessing > >> > the time reference counter MSR. I'll still keep the procedure that goes > >> > through kvmclock.

Re: [PATCH V2 1/5] Documentation: Add support for TI System Control Interface (TI-SCI) protocol

Rob, On Fri, Sep 2, 2016 at 10:06 AM, Rob Herring wrote: > On Tue, Aug 30, 2016 at 08:06:43AM -0500, Nishanth Menon wrote: [...] >> + >> +TI-SCI Client Device Node: >> + >> + >> +Client nodes refer to the required TI-SCI device using the "ti,sci" >>

Re: [PATCH 3/4] KVM: x86: introduce get_kvmclock_ns

On Fri, Sep 02, 2016 at 06:57:10PM +0200, Paolo Bonzini wrote: > > > On 02/09/2016 18:55, Roman Kagan wrote: > >> > I'll change patch 4 to store the parameters and use them when accessing > >> > the time reference counter MSR. I'll still keep the procedure that goes > >> > through kvmclock.

Re: [PATCH V2 1/5] Documentation: Add support for TI System Control Interface (TI-SCI) protocol

Rob, On Fri, Sep 2, 2016 at 10:06 AM, Rob Herring wrote: > On Tue, Aug 30, 2016 at 08:06:43AM -0500, Nishanth Menon wrote: [...] >> + >> +TI-SCI Client Device Node: >> + >> + >> +Client nodes refer to the required TI-SCI device using the "ti,sci" >> property. > > As I

Re: [PATCH] tpm: invalid self test error message

On Fri, Sep 02, 2016 at 08:56:29AM +0300, Jarkko Sakkinen wrote: > The driver emits invalid self test error message even though the init > succeeds. > > Signed-off-by: Jarkko Sakkinen > Fixes: cae8b441fc20 ("tpm: Factor out common startup code") Reviewed-by:

Re: [PATCH] tpm: invalid self test error message

On Fri, Sep 02, 2016 at 08:56:29AM +0300, Jarkko Sakkinen wrote: > The driver emits invalid self test error message even though the init > succeeds. > > Signed-off-by: Jarkko Sakkinen > Fixes: cae8b441fc20 ("tpm: Factor out common startup code") Reviewed-by: Jason Gunthorpe Reported-by: Petr

Re: [GIT PULL] firmware: add support for TI System Control Interface (TI-SCI) protocol driver

On 9/2/2016 10:03 AM, Nishanth Menon wrote: On Thu, Sep 1, 2016 at 2:24 AM, Tero Kristo wrote: Hi Santosh, The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc: Linux 4.8-rc1 (2016-08-07 18:18:00 -0700) are available in the git repository at:

Re: [GIT PULL] firmware: add support for TI System Control Interface (TI-SCI) protocol driver

On 9/2/2016 10:03 AM, Nishanth Menon wrote: On Thu, Sep 1, 2016 at 2:24 AM, Tero Kristo wrote: Hi Santosh, The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc: Linux 4.8-rc1 (2016-08-07 18:18:00 -0700) are available in the git repository at:

Re: [GIT PULL] firmware: add support for TI System Control Interface (TI-SCI) protocol driver

On Thu, Sep 1, 2016 at 2:24 AM, Tero Kristo wrote: > Hi Santosh, > > The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc: > > Linux 4.8-rc1 (2016-08-07 18:18:00 -0700) > > are available in the git repository at: > >

Re: [GIT PULL] firmware: add support for TI System Control Interface (TI-SCI) protocol driver

On Thu, Sep 1, 2016 at 2:24 AM, Tero Kristo wrote: > Hi Santosh, > > The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc: > > Linux 4.8-rc1 (2016-08-07 18:18:00 -0700) > > are available in the git repository at: > > https://github.com/t-kristo/linux-pm.git

i2c: imx: add slave support. v2 status

Hi Maxim, On 2016-03-04 11:06:10 in the thread "Re: [PATCH] i2c: imx: add slave support. v2" referenced here: https://patchwork.ozlabs.org/patch/573353/ you said: > Hi Wolfram, > I'm now working on creating new driver version. I think I'll be able to > sent it soon. Do you still plan to

i2c: imx: add slave support. v2 status

Hi Maxim, On 2016-03-04 11:06:10 in the thread "Re: [PATCH] i2c: imx: add slave support. v2" referenced here: https://patchwork.ozlabs.org/patch/573353/ you said: > Hi Wolfram, > I'm now working on creating new driver version. I think I'll be able to > sent it soon. Do you still plan to

Re: [PATCH 4/4] kvm: x86: export TSC offset to user-space

On 31/08/2016 19:05, Luiz Capitulino wrote: > vcpu0: 18446742405270834952 > vcpu1: 18446742405270834952 > vcpu2: 18446742405270834952 > vcpu3: 18446742405270834952 > > - We'll probably need to export the TSC multiplier too. >However, I've been using only the TSC offset for now. >

Re: [PATCH 4/4] kvm: x86: export TSC offset to user-space

On 31/08/2016 19:05, Luiz Capitulino wrote: > vcpu0: 18446742405270834952 > vcpu1: 18446742405270834952 > vcpu2: 18446742405270834952 > vcpu3: 18446742405270834952 > > - We'll probably need to export the TSC multiplier too. >However, I've been using only the TSC offset for now. >

Re: [PATCH 3/4] KVM: x86: introduce get_kvmclock_ns

On 02/09/2016 18:55, Roman Kagan wrote: >> > I'll change patch 4 to store the parameters and use them when accessing >> > the time reference counter MSR. I'll still keep the procedure that goes >> > through kvmclock. It's a bit more involved for the scale, but >> > vcpu->last_guest_tsc only

Re: e1000e on Thinkpad x60: gigabit not available due to "SmartSpeed"

On Thu, Sep 01, 2016 at 02:58:13PM -0700, Greg wrote: > On Thu, 2016-09-01 at 22:14 +0200, Pavel Machek wrote: > > Hi! > > > > I have trouble getting 1000mbit out of my ethernet card. > > > > I tried direct connection between two PCs with different cables, and > > no luck. > > > > Today I tried

Re: [PATCH 3/4] KVM: x86: introduce get_kvmclock_ns

On 02/09/2016 18:55, Roman Kagan wrote: >> > I'll change patch 4 to store the parameters and use them when accessing >> > the time reference counter MSR. I'll still keep the procedure that goes >> > through kvmclock. It's a bit more involved for the scale, but >> > vcpu->last_guest_tsc only

Re: e1000e on Thinkpad x60: gigabit not available due to "SmartSpeed"

On Thu, Sep 01, 2016 at 02:58:13PM -0700, Greg wrote: > On Thu, 2016-09-01 at 22:14 +0200, Pavel Machek wrote: > > Hi! > > > > I have trouble getting 1000mbit out of my ethernet card. > > > > I tried direct connection between two PCs with different cables, and > > no luck. > > > > Today I tried

Re: [PATCH v2 1/2] perf: add container identifier entry in perf sample data

On Friday 02 September 2016 07:29 PM, Peter Zijlstra wrote: On Fri, Sep 02, 2016 at 07:25:31PM +0530, Hari Bathini wrote: I'm thinking this value is mostly the same for tasks, just like COMM and I think so, too. Namespaces aren't changed that often for tasks... MMAP. Could we therefore not

Re: [PATCH v2 1/2] perf: add container identifier entry in perf sample data

On Friday 02 September 2016 07:29 PM, Peter Zijlstra wrote: On Fri, Sep 02, 2016 at 07:25:31PM +0530, Hari Bathini wrote: I'm thinking this value is mostly the same for tasks, just like COMM and I think so, too. Namespaces aren't changed that often for tasks... MMAP. Could we therefore not

Re: [PATCH] trivial treewide: Convert dev_set_uevent_suppress argument to bool

On Fri, 2016-09-02 at 08:59 -0700, Bart Van Assche wrote: > How about the following: > > dev_set_uevent_suppress() expects a boolean as second argument. Make  > this clear by passing true/false instead of 1/0 as the second > argument. dev_set_uevent_suppress() doesn't currently expect a boolean.

Re: [PATCH] trivial treewide: Convert dev_set_uevent_suppress argument to bool

On Fri, 2016-09-02 at 08:59 -0700, Bart Van Assche wrote: > How about the following: > > dev_set_uevent_suppress() expects a boolean as second argument. Make  > this clear by passing true/false instead of 1/0 as the second > argument. dev_set_uevent_suppress() doesn't currently expect a boolean.

Re: [PATCH v3 1/2] wcn36xx: Transition driver to SMD client

On Fri 02 Sep 09:24 PDT 2016, Kalle Valo wrote: > Bjorn Andersson writes: > > > The wcn36xx wifi driver follows the life cycle of the WLAN_CTRL SMD > > channel, as such it should be a SMD client. This patch makes this > > transition, now that we have the necessary

Re: [PATCH v3 1/2] wcn36xx: Transition driver to SMD client

On Fri 02 Sep 09:24 PDT 2016, Kalle Valo wrote: > Bjorn Andersson writes: > > > The wcn36xx wifi driver follows the life cycle of the WLAN_CTRL SMD > > channel, as such it should be a SMD client. This patch makes this > > transition, now that we have the necessary frameworks available. > > > >

Re: chipidea: udc: kernel panic in isr_setup_status_phase

On Fri, Sep 02, 2016 at 09:55:52AM +0800, Peter Chen wrote: > Do you have other 5V to USB_H1_VBUS? USB PHY needs 5V input voltage > as the source for USB LDO (3.0v), either from OTG or Host 1. I suspect > the lower vbus voltage causes the USB LDO voltage less than 3.0v, then > cause the unstable

Re: chipidea: udc: kernel panic in isr_setup_status_phase

On Fri, Sep 02, 2016 at 09:55:52AM +0800, Peter Chen wrote: > Do you have other 5V to USB_H1_VBUS? USB PHY needs 5V input voltage > as the source for USB LDO (3.0v), either from OTG or Host 1. I suspect > the lower vbus voltage causes the USB LDO voltage less than 3.0v, then > cause the unstable

RE: [PATCH] ARM: fix linker call for ARM_MODULE_PLTS

> From: Russell King - ARM Linux [mailto:li...@armlinux.org.uk] > Sent: Friday, September 02, 2016 11:25 AM > > On Fri, Sep 02, 2016 at 09:17:58AM +, Wiebe, Wladislav (Nokia - DE/Ulm) > wrote: > > module.lds script doesn't get called when > > CONFIG_ARM_MODULE_PLTS is enabled. > > Use

RE: [PATCH] ARM: fix linker call for ARM_MODULE_PLTS

> From: Russell King - ARM Linux [mailto:li...@armlinux.org.uk] > Sent: Friday, September 02, 2016 11:25 AM > > On Fri, Sep 02, 2016 at 09:17:58AM +, Wiebe, Wladislav (Nokia - DE/Ulm) > wrote: > > module.lds script doesn't get called when > > CONFIG_ARM_MODULE_PLTS is enabled. > > Use

Re: [PATCH] x86/paravirt: Do not trace _paravirt_ident_*() functions

On Fri, Sep 2, 2016 at 7:46 AM, Steven Rostedt wrote: > > Can someone please pull this in. And mark it for stable, it goes > probably as far back as 2.6.32. Applied. Linus

Re: [PATCH] x86/paravirt: Do not trace _paravirt_ident_*() functions

On Fri, Sep 2, 2016 at 7:46 AM, Steven Rostedt wrote: > > Can someone please pull this in. And mark it for stable, it goes > probably as far back as 2.6.32. Applied. Linus

Re: [PATCH v15 04/13] task_isolation: add initial support

On Fri, Sep 02, 2016 at 10:03:52AM -0400, Chris Metcalf wrote: > Any thoughts on the question of "just re-enter the loop" vs. > schedule_timeout()? schedule_timeout() should only be used for things you do not have control over, like things outside of the machine. If you want to actually block

Re: [PATCH v15 04/13] task_isolation: add initial support

On Fri, Sep 02, 2016 at 10:03:52AM -0400, Chris Metcalf wrote: > Any thoughts on the question of "just re-enter the loop" vs. > schedule_timeout()? schedule_timeout() should only be used for things you do not have control over, like things outside of the machine. If you want to actually block

Re: [PATCH v3 1/2] wcn36xx: Transition driver to SMD client

Hi Kalle, >> The wcn36xx wifi driver follows the life cycle of the WLAN_CTRL SMD >> channel, as such it should be a SMD client. This patch makes this >> transition, now that we have the necessary frameworks available. >> >> Signed-off-by: Bjorn Andersson > > [...] >

Re: [PATCH 3/4] KVM: x86: introduce get_kvmclock_ns

On 02/09/2016 16:51, Roman Kagan wrote: > On Fri, Sep 02, 2016 at 04:09:42PM +0200, Paolo Bonzini wrote: >> On 02/09/2016 15:52, Roman Kagan wrote: >> vs. using a single offset as in the TSC ref page is one nanosecond---and >> the ref page only has a resolution of 100 ns. > > AFAICS it's not a

Re: [PATCH v3 1/2] wcn36xx: Transition driver to SMD client

Hi Kalle, >> The wcn36xx wifi driver follows the life cycle of the WLAN_CTRL SMD >> channel, as such it should be a SMD client. This patch makes this >> transition, now that we have the necessary frameworks available. >> >> Signed-off-by: Bjorn Andersson > > [...] > >> ---

Re: [PATCH 3/4] KVM: x86: introduce get_kvmclock_ns

On 02/09/2016 16:51, Roman Kagan wrote: > On Fri, Sep 02, 2016 at 04:09:42PM +0200, Paolo Bonzini wrote: >> On 02/09/2016 15:52, Roman Kagan wrote: >> vs. using a single offset as in the TSC ref page is one nanosecond---and >> the ref page only has a resolution of 100 ns. > > AFAICS it's not a

Re: [GIT PULL 4/4] ARM: defconfig: Exynos for v4.9

On Fri, Sep 02, 2016 at 05:47:11PM +0200, Arnd Bergmann wrote: > On Tuesday, August 30, 2016 11:18:56 AM CEST Krzysztof Kozlowski wrote: > > Expected conflict in multi_v7 - take all the changes: > > > > --- a/arch/arm/configs/multi_v7_defconfig > > +++ b/arch/arm/configs/multi_v7_defconfig > >

Re: [GIT PULL 4/4] ARM: defconfig: Exynos for v4.9

On Fri, Sep 02, 2016 at 05:47:11PM +0200, Arnd Bergmann wrote: > On Tuesday, August 30, 2016 11:18:56 AM CEST Krzysztof Kozlowski wrote: > > Expected conflict in multi_v7 - take all the changes: > > > > --- a/arch/arm/configs/multi_v7_defconfig > > +++ b/arch/arm/configs/multi_v7_defconfig > >

Re: [PATCH 2/5] irqtime: Remove needless IRQs disablement on kcpustat update

On Fri, Sep 02, 2016 at 04:53:47PM +0200, Paolo Bonzini wrote: > > > On 02/09/2016 16:03, Frederic Weisbecker wrote: > > The callers of the functions performing irqtime kcpustat updates have > > IRQS disabled, no need to disable them again. > > They do, but perhaps this should be annotated

Re: [PATCH 2/5] irqtime: Remove needless IRQs disablement on kcpustat update

On Fri, Sep 02, 2016 at 04:53:47PM +0200, Paolo Bonzini wrote: > > > On 02/09/2016 16:03, Frederic Weisbecker wrote: > > The callers of the functions performing irqtime kcpustat updates have > > IRQS disabled, no need to disable them again. > > They do, but perhaps this should be annotated

Re: [GIT PULL 1/4] ARM: exynos: SoC/Mach for v4.9

On Fri, Sep 02, 2016 at 06:26:42PM +0200, Arnd Bergmann wrote: > On Tuesday, August 30, 2016 11:18:59 AM CEST Krzysztof Kozlowski wrote: > > Samsung mach/soc update for v4.9: > > 1. Fix for DMA on S3C24xx. This was probably broken for long time, nobody > > runs > >this code... till now. > >

Re: [GIT PULL 1/4] ARM: exynos: SoC/Mach for v4.9

On Fri, Sep 02, 2016 at 06:26:42PM +0200, Arnd Bergmann wrote: > On Tuesday, August 30, 2016 11:18:59 AM CEST Krzysztof Kozlowski wrote: > > Samsung mach/soc update for v4.9: > > 1. Fix for DMA on S3C24xx. This was probably broken for long time, nobody > > runs > >this code... till now. > >

Re: [PATCH 4/4] kvm: x86: export TSC offset to user-space

On Fri, 2 Sep 2016 12:26:55 -0400 Luiz Capitulino wrote: > I guess that what tools like trace-cmd want to do in those cases > is to warn the user and discard the trace. A simple way of doing > this would be to re-check that the TSC offset are the same after > tracing is

Re: [PATCH 4/4] kvm: x86: export TSC offset to user-space

On Fri, 2 Sep 2016 12:26:55 -0400 Luiz Capitulino wrote: > I guess that what tools like trace-cmd want to do in those cases > is to warn the user and discard the trace. A simple way of doing > this would be to re-check that the TSC offset are the same after > tracing is done. It could also use

Re: [v10,2/2] PCI: Rockchip: Add Rockchip PCIe controller support

Am Freitag, 2. September 2016, 10:44:09 schrieb Bjorn Helgaas: > On Thu, Sep 01, 2016 at 12:48:52PM -0500, Bjorn Helgaas wrote: > > On Thu, Sep 01, 2016 at 10:14:01AM -0700, Brian Norris wrote: > > > The use of HIWORD_UPDATE can indeed be a bit confusing, IMO, but this is > > > really a common

Re: [v10,2/2] PCI: Rockchip: Add Rockchip PCIe controller support

Am Freitag, 2. September 2016, 10:44:09 schrieb Bjorn Helgaas: > On Thu, Sep 01, 2016 at 12:48:52PM -0500, Bjorn Helgaas wrote: > > On Thu, Sep 01, 2016 at 10:14:01AM -0700, Brian Norris wrote: > > > The use of HIWORD_UPDATE can indeed be a bit confusing, IMO, but this is > > > really a common

Re: [GIT PULL 1/4] ARM: exynos: SoC/Mach for v4.9

On Tuesday, August 30, 2016 11:18:59 AM CEST Krzysztof Kozlowski wrote: > Samsung mach/soc update for v4.9: > 1. Fix for DMA on S3C24xx. This was probably broken for long time, nobody runs >this code... till now. Good to know. This reminds me that the s3c24xx DMA code is one of those that

Re: [GIT PULL 1/4] ARM: exynos: SoC/Mach for v4.9

On Tuesday, August 30, 2016 11:18:59 AM CEST Krzysztof Kozlowski wrote: > Samsung mach/soc update for v4.9: > 1. Fix for DMA on S3C24xx. This was probably broken for long time, nobody runs >this code... till now. Good to know. This reminds me that the s3c24xx DMA code is one of those that

Re: [PATCH v2 2/2] arm64: dts: Fix broken architected timer interrupt trigger

On Monday, August 1, 2016 7:00:50 PM CEST Masahiro Yamada wrote: > > Acked-by: Duc Dang > > Acked-by: Carlo Caione > > Acked-by: Michal Simek > > Acked-by: Krzysztof Kozlowski > > Acked-by: Dinh Nguyen

Re: [PATCH v2 2/2] arm64: dts: Fix broken architected timer interrupt trigger

On Monday, August 1, 2016 7:00:50 PM CEST Masahiro Yamada wrote: > > Acked-by: Duc Dang > > Acked-by: Carlo Caione > > Acked-by: Michal Simek > > Acked-by: Krzysztof Kozlowski > > Acked-by: Dinh Nguyen > > Signed-off-by: Marc Zyngier > > --- > >

Re: [PATCH 11/12] power: reset: Add Intel PIIX4 poweroff driver

Hi Paul, The driver looks fine to me, just two notes: On Fri, Sep 02, 2016 at 04:48:57PM +0100, Paul Burton wrote: > Add a driver which allows powering off the system via an Intel PIIX4 > southbridge, by entering the PIIX4 SOff state. This is useful on the > MIPS Malta development board, where

Re: [PATCH][RFC v3] PCI: Workaround to enable poweroff on Mac Pro 11

On Wed, Aug 24, 2016 at 04:17:31PM +0200, Lukas Wunner wrote: > On Fri, Aug 19, 2016 at 04:30:25PM +0800, Chen Yu wrote: > > People reported that they can not do a poweroff nor a > > suspend to ram on their Mac Pro 11. After some investigations > > it was found that, once the PCI bridge

Re: [PATCH 11/12] power: reset: Add Intel PIIX4 poweroff driver

Hi Paul, The driver looks fine to me, just two notes: On Fri, Sep 02, 2016 at 04:48:57PM +0100, Paul Burton wrote: > Add a driver which allows powering off the system via an Intel PIIX4 > southbridge, by entering the PIIX4 SOff state. This is useful on the > MIPS Malta development board, where

Re: [PATCH][RFC v3] PCI: Workaround to enable poweroff on Mac Pro 11

On Wed, Aug 24, 2016 at 04:17:31PM +0200, Lukas Wunner wrote: > On Fri, Aug 19, 2016 at 04:30:25PM +0800, Chen Yu wrote: > > People reported that they can not do a poweroff nor a > > suspend to ram on their Mac Pro 11. After some investigations > > it was found that, once the PCI bridge

Re: [PATCH 4/4] kvm: x86: export TSC offset to user-space

On Fri, 2 Sep 2016 09:43:01 -0400 Stefan Hajnoczi wrote: > On Wed, Aug 31, 2016 at 01:05:45PM -0400, Luiz Capitulino wrote: > > We need to retrieve a VM's TSC offset in order to use > > the host's TSC to merge host and guest traces. This is > > explained in detail in this

Re: [PATCH 4/4] kvm: x86: export TSC offset to user-space

On Fri, 2 Sep 2016 09:43:01 -0400 Stefan Hajnoczi wrote: > On Wed, Aug 31, 2016 at 01:05:45PM -0400, Luiz Capitulino wrote: > > We need to retrieve a VM's TSC offset in order to use > > the host's TSC to merge host and guest traces. This is > > explained in detail in this thread: > > > >

Re: [PATCH v3 1/2] wcn36xx: Transition driver to SMD client

Bjorn Andersson writes: > The wcn36xx wifi driver follows the life cycle of the WLAN_CTRL SMD > channel, as such it should be a SMD client. This patch makes this > transition, now that we have the necessary frameworks available. > > Signed-off-by: Bjorn Andersson

Re: [PATCH] usb: dwc3: host: inherit dma configuration from parent dev

On 09/02/2016 02:08 PM, Felipe Balbi wrote: > > Hi, > > Russell King - ARM Linux writes: >> On Fri, Sep 02, 2016 at 12:43:39PM +0200, Arnd Bergmann wrote: >>> On Thursday, September 1, 2016 5:14:28 PM CEST Leo Li wrote: Hi Felipe and Arnd, It has been

Re: [PATCH v3 1/2] wcn36xx: Transition driver to SMD client

Bjorn Andersson writes: > The wcn36xx wifi driver follows the life cycle of the WLAN_CTRL SMD > channel, as such it should be a SMD client. This patch makes this > transition, now that we have the necessary frameworks available. > > Signed-off-by: Bjorn Andersson [...] > ---

Re: [PATCH] usb: dwc3: host: inherit dma configuration from parent dev

On 09/02/2016 02:08 PM, Felipe Balbi wrote: > > Hi, > > Russell King - ARM Linux writes: >> On Fri, Sep 02, 2016 at 12:43:39PM +0200, Arnd Bergmann wrote: >>> On Thursday, September 1, 2016 5:14:28 PM CEST Leo Li wrote: Hi Felipe and Arnd, It has been a while since the last

Re: [PATCH v2 1/6] rtl8723au: remove declaration of unimplemented functions

Luca Ceresoli writes: > These functions have been declared without any implementation since > the first commit (364e30ebd2dbaccba430c603da03e68746eb932a) and there > has been no mention of them in following commits. > > Signed-off-by: Luca Ceresoli

Re: [PATCH v2 1/6] rtl8723au: remove declaration of unimplemented functions

Luca Ceresoli writes: > These functions have been declared without any implementation since > the first commit (364e30ebd2dbaccba430c603da03e68746eb932a) and there > has been no mention of them in following commits. > > Signed-off-by: Luca Ceresoli > Cc: Larry Finger > Cc: Jes Sorensen > Cc:

[tip:irq/core] irqdomain: Mask irq type in irq_domain_xlate_onetwocell()

Commit-ID: 0c228919e04ddec195402296e7ebf2472ed6caef Gitweb: http://git.kernel.org/tip/0c228919e04ddec195402296e7ebf2472ed6caef Author: Sebastian Frias AuthorDate: Tue, 2 Aug 2016 10:52:45 +0200 Committer: Thomas Gleixner CommitDate: Fri, 2 Sep 2016

[tip:irq/core] genirq/generic_chip: Verify irqs_per_chip <= 32

Commit-ID: 895d3b95ed05f72a94f69ab52cb313915a6b889f Gitweb: http://git.kernel.org/tip/895d3b95ed05f72a94f69ab52cb313915a6b889f Author: Sebastian Frias AuthorDate: Tue, 16 Aug 2016 16:05:08 +0200 Committer: Thomas Gleixner CommitDate: Fri, 2 Sep

[tip:irq/core] irqdomain: Mask irq type in irq_domain_xlate_onetwocell()

Commit-ID: 0c228919e04ddec195402296e7ebf2472ed6caef Gitweb: http://git.kernel.org/tip/0c228919e04ddec195402296e7ebf2472ed6caef Author: Sebastian Frias AuthorDate: Tue, 2 Aug 2016 10:52:45 +0200 Committer: Thomas Gleixner CommitDate: Fri, 2 Sep 2016 18:06:50 +0200 irqdomain: Mask irq

[tip:irq/core] genirq/generic_chip: Verify irqs_per_chip <= 32

Commit-ID: 895d3b95ed05f72a94f69ab52cb313915a6b889f Gitweb: http://git.kernel.org/tip/895d3b95ed05f72a94f69ab52cb313915a6b889f Author: Sebastian Frias AuthorDate: Tue, 16 Aug 2016 16:05:08 +0200 Committer: Thomas Gleixner CommitDate: Fri, 2 Sep 2016 18:06:50 +0200 genirq/generic_chip:

Re: [PATCH] fs/proc/kcore.c: Omit kernel text area for hardened usercopy feature

On Fri, Sep 02, 2016 at 08:17:13AM -0700, Andi Kleen wrote: > On Fri, Sep 02, 2016 at 02:25:45PM +0200, Jiri Olsa wrote: > > One of the bullets for hardened usercopy feature is: > > - object must not overlap with kernel text > > > > which is what we expose via /proc/kcore. We can hit > > this

[tip:irq/core] genirq/generic_chip: Add irq_unmap callback

Commit-ID: ee26c013cdee0b947e29d6cadfb9ff3341c69ff9 Gitweb: http://git.kernel.org/tip/ee26c013cdee0b947e29d6cadfb9ff3341c69ff9 Author: Sebastian Frias AuthorDate: Mon, 1 Aug 2016 16:27:38 +0200 Committer: Thomas Gleixner CommitDate: Fri, 2 Sep 2016

Re: [PATCH] fs/proc/kcore.c: Omit kernel text area for hardened usercopy feature

On Fri, Sep 02, 2016 at 08:17:13AM -0700, Andi Kleen wrote: > On Fri, Sep 02, 2016 at 02:25:45PM +0200, Jiri Olsa wrote: > > One of the bullets for hardened usercopy feature is: > > - object must not overlap with kernel text > > > > which is what we expose via /proc/kcore. We can hit > > this

[tip:irq/core] genirq/generic_chip: Add irq_unmap callback

Commit-ID: ee26c013cdee0b947e29d6cadfb9ff3341c69ff9 Gitweb: http://git.kernel.org/tip/ee26c013cdee0b947e29d6cadfb9ff3341c69ff9 Author: Sebastian Frias AuthorDate: Mon, 1 Aug 2016 16:27:38 +0200 Committer: Thomas Gleixner CommitDate: Fri, 2 Sep 2016 18:06:49 +0200 genirq/generic_chip:

[tip:irq/core] genirq/generic_chip: Get rid of code duplication

Commit-ID: f0c450eaa364cb77c778f2a46ee2aa3ff464b332 Gitweb: http://git.kernel.org/tip/f0c450eaa364cb77c778f2a46ee2aa3ff464b332 Author: Sebastian Frias AuthorDate: Mon, 1 Aug 2016 16:27:53 +0200 Committer: Thomas Gleixner CommitDate: Fri, 2 Sep 2016

[tip:irq/core] genirq/generic_chip: Get rid of code duplication

Commit-ID: f0c450eaa364cb77c778f2a46ee2aa3ff464b332 Gitweb: http://git.kernel.org/tip/f0c450eaa364cb77c778f2a46ee2aa3ff464b332 Author: Sebastian Frias AuthorDate: Mon, 1 Aug 2016 16:27:53 +0200 Committer: Thomas Gleixner CommitDate: Fri, 2 Sep 2016 18:06:49 +0200 genirq/generic_chip:

[tip:irq/core] genirq: Robustify handle_percpu_devid_irq()

Commit-ID: fc590c22f9f056ab50190b797f6cacead29f9b75 Gitweb: http://git.kernel.org/tip/fc590c22f9f056ab50190b797f6cacead29f9b75 Author: Thomas Gleixner AuthorDate: Fri, 2 Sep 2016 14:45:19 +0200 Committer: Thomas Gleixner CommitDate: Fri, 2 Sep

[tip:irq/core] genirq: Robustify handle_percpu_devid_irq()

Commit-ID: fc590c22f9f056ab50190b797f6cacead29f9b75 Gitweb: http://git.kernel.org/tip/fc590c22f9f056ab50190b797f6cacead29f9b75 Author: Thomas Gleixner AuthorDate: Fri, 2 Sep 2016 14:45:19 +0200 Committer: Thomas Gleixner CommitDate: Fri, 2 Sep 2016 18:06:49 +0200 genirq: Robustify

Re: [PATCH 1/4] Documentation: mmc: sdhci-of-arasan: Add clk_syscon as an optional one

Rob, On Fri, Sep 2, 2016 at 7:15 AM, Rob Herring wrote: > On Mon, Aug 29, 2016 at 04:02:56PM +0800, Shawn Lin wrote: >> We introduced soc-ctl-syscon to do several things, for instance, update >> baseclk or update clkmul, etc. In odrder to access this physical block, >> we need

Re: [PATCH 1/4] Documentation: mmc: sdhci-of-arasan: Add clk_syscon as an optional one

Rob, On Fri, Sep 2, 2016 at 7:15 AM, Rob Herring wrote: > On Mon, Aug 29, 2016 at 04:02:56PM +0800, Shawn Lin wrote: >> We introduced soc-ctl-syscon to do several things, for instance, update >> baseclk or update clkmul, etc. In odrder to access this physical block, >> we need to explicitly

Re: [PATCH net-next 3/3] net: dsa: mv88e6xxx: make global2 code optional

Hi Vivien > What do you think? I think the probe() needs to fail with a very obvious error message saying you need to recompile your kernel with option XYZ enabled in order to support this switch, when the optional stuff is not optional... Andrew

Re: [PATCH net-next 3/3] net: dsa: mv88e6xxx: make global2 code optional

Hi Vivien > What do you think? I think the probe() needs to fail with a very obvious error message saying you need to recompile your kernel with option XYZ enabled in order to support this switch, when the optional stuff is not optional... Andrew

Re: [v2] ath9k: mark ath_fill_led_pin() static

Baoyou Xie wrote: > We get 1 warning about global functions without a declaration > in the ath9k gpio driver when building with W=1: > drivers/net/wireless/ath/ath9k/gpio.c:25:6: warning: no previous prototype > for 'ath_fill_led_pin' [-Wmissing-prototypes] > > In fact,

Re: [v2] ath9k: mark ath_fill_led_pin() static

Baoyou Xie wrote: > We get 1 warning about global functions without a declaration > in the ath9k gpio driver when building with W=1: > drivers/net/wireless/ath/ath9k/gpio.c:25:6: warning: no previous prototype > for 'ath_fill_led_pin' [-Wmissing-prototypes] > > In fact, this function is only

Re: [PATCHv2] pwm: lpc-18xx: use pwm_set_chip_data

Hi Olliver, On 08/25/2016 01:47 PM, Olliver Schinagl wrote: > The lpc18xx driver currently manipulates the pwm_device struct directly > rather then using the pwm_set_chip_data. While the current method may > save a clock cycle or two, it is more obvious that data is set to > the local chip data

Re: [PATCHv2] pwm: lpc-18xx: use pwm_set_chip_data

Hi Olliver, On 08/25/2016 01:47 PM, Olliver Schinagl wrote: > The lpc18xx driver currently manipulates the pwm_device struct directly > rather then using the pwm_set_chip_data. While the current method may > save a clock cycle or two, it is more obvious that data is set to > the local chip data

Re: [PATCH 2/2] arm64: Use static keys for CPU features

On 02/09/16 16:52, Catalin Marinas wrote: On Fri, Aug 26, 2016 at 10:22:13AM +0100, Suzuki K. Poulose wrote: On 25/08/16 18:26, Catalin Marinas wrote: Just a heads up. I have a patch [1] which moves the "check_local_cpu_errata()" around to smp_prepare_boot_cpu(). This patch should still

Re: [PATCH 2/2] arm64: Use static keys for CPU features

On 02/09/16 16:52, Catalin Marinas wrote: On Fri, Aug 26, 2016 at 10:22:13AM +0100, Suzuki K. Poulose wrote: On 25/08/16 18:26, Catalin Marinas wrote: Just a heads up. I have a patch [1] which moves the "check_local_cpu_errata()" around to smp_prepare_boot_cpu(). This patch should still

Re: [PATCH 2/4] KVM: x86: initialize kvmclock_offset

On Thu, Sep 01, 2016 at 05:26:13PM +0200, Paolo Bonzini wrote: > Make the guest's kvmclock count up from zero, not from the host boot > time. The guest cannot rely on that anyway because it changes on > migration, the numbers are easier on the eye and finally it matches the > desired semantics of

Re: [PATCH 2/4] KVM: x86: initialize kvmclock_offset

On Thu, Sep 01, 2016 at 05:26:13PM +0200, Paolo Bonzini wrote: > Make the guest's kvmclock count up from zero, not from the host boot > time. The guest cannot rely on that anyway because it changes on > migration, the numbers are easier on the eye and finally it matches the > desired semantics of

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