[PATCH v3 16/27] thunderbolt: Expose make_header() to other files

We will be using this function in files introduced in subsequent patches. While there the function is renamed to tb_cfg_make_header() following tb_cfg_get_route(). Signed-off-by: Mika Westerberg Reviewed-by: Yehezkel Bernat

[PATCH v3 18/27] thunderbolt: Rework control channel to be more reliable

If a request times out the response might arrive right after the request is failed. This response is pushed to the kfifo and next request will read it instead. Since it most likely will not pass our validation checks in parse_header() the next request will fail as well, and response to that

[PATCH v3 16/27] thunderbolt: Expose make_header() to other files

We will be using this function in files introduced in subsequent patches. While there the function is renamed to tb_cfg_make_header() following tb_cfg_get_route(). Signed-off-by: Mika Westerberg Reviewed-by: Yehezkel Bernat Reviewed-by: Michael Jamet Reviewed-by: Andy Shevchenko ---

[PATCH v3 18/27] thunderbolt: Rework control channel to be more reliable

If a request times out the response might arrive right after the request is failed. This response is pushed to the kfifo and next request will read it instead. Since it most likely will not pass our validation checks in parse_header() the next request will fail as well, and response to that

[PATCH v3 05/27] thunderbolt: Add MSI-X support

Intel Thunderbolt controllers support up to 16 MSI-X vectors. Using MSI-X is preferred over MSI or legacy interrupt and may bring additional performance because there is no need to check the status registers which interrupt was triggered. While there we convert comments in structs tb_ring and

Re: [PATCHv2] perf test: Disable breakpoint signal tests for powerpc

Em Fri, Jun 02, 2017 at 11:04:33AM -0300, Arnaldo Carvalho de Melo escreveu: > Em Thu, Jun 01, 2017 at 10:54:50PM +0200, Jiri Olsa escreveu: > > > > + if (t->is_supported && !t->is_supported()) { > > + pr_debug("%2d: %-*s: Disabled\n", i, width, t->desc); > > This

[PATCH v3 00/27] Thunderbolt security levels and NVM firmware upgrade

Hi, This is a third version of the patch series adding support for Thunderbolt security levels and NVM firmware upgrade. PCs running Intel Falcon Ridge or newer need these in order to connect devices if the security level is set to "user(SL1) or secure(SL2)" from BIOS. The security levels were

Re: [PATCHv2] perf test: Disable breakpoint signal tests for powerpc

Em Fri, Jun 02, 2017 at 11:04:33AM -0300, Arnaldo Carvalho de Melo escreveu: > Em Thu, Jun 01, 2017 at 10:54:50PM +0200, Jiri Olsa escreveu: > > > > + if (t->is_supported && !t->is_supported()) { > > + pr_debug("%2d: %-*s: Disabled\n", i, width, t->desc); > > This

[PATCH v3 00/27] Thunderbolt security levels and NVM firmware upgrade

Hi, This is a third version of the patch series adding support for Thunderbolt security levels and NVM firmware upgrade. PCs running Intel Falcon Ridge or newer need these in order to connect devices if the security level is set to "user(SL1) or secure(SL2)" from BIOS. The security levels were

[PATCH v3 05/27] thunderbolt: Add MSI-X support

Intel Thunderbolt controllers support up to 16 MSI-X vectors. Using MSI-X is preferred over MSI or legacy interrupt and may bring additional performance because there is no need to check the status registers which interrupt was triggered. While there we convert comments in structs tb_ring and

Re: [PATCHv2] perf test: Disable breakpoint signal tests for powerpc

Em Thu, Jun 01, 2017 at 10:54:50PM +0200, Jiri Olsa escreveu: > > + if (t->is_supported && !t->is_supported()) { > + pr_debug("%2d: %-*s: Disabled\n", i, width, t->desc); This isn't clear, I'll change this to leave the pr_debug up to the ->is_supported() code

Re: [PATCHv2] perf test: Disable breakpoint signal tests for powerpc

Em Thu, Jun 01, 2017 at 10:54:50PM +0200, Jiri Olsa escreveu: > > + if (t->is_supported && !t->is_supported()) { > + pr_debug("%2d: %-*s: Disabled\n", i, width, t->desc); This isn't clear, I'll change this to leave the pr_debug up to the ->is_supported() code

Re: [PATCH] net: phy: marvell: make two functions static

On 02/06/17 15:00, Andrew Lunn wrote: > On Fri, Jun 02, 2017 at 12:14:24PM +0100, Colin King wrote: >> From: Colin Ian King >> >> functions m88e1510_get_temp_critical and m88e1510_get_temp_alarm can be >> made static as they not need to be in global scope. >> >> Cleans

Re: [PATCH] net: phy: marvell: make two functions static

On 02/06/17 15:00, Andrew Lunn wrote: > On Fri, Jun 02, 2017 at 12:14:24PM +0100, Colin King wrote: >> From: Colin Ian King >> >> functions m88e1510_get_temp_critical and m88e1510_get_temp_alarm can be >> made static as they not need to be in global scope. >> >> Cleans up sparse warnings: >>

Re: [PATCH] net: phy: marvell: make two functions static

On Fri, Jun 02, 2017 at 12:14:24PM +0100, Colin King wrote: > From: Colin Ian King > > functions m88e1510_get_temp_critical and m88e1510_get_temp_alarm can be > made static as they not need to be in global scope. > > Cleans up sparse warnings: > "symbol

Re: [PATCH] net: phy: marvell: make two functions static

On Fri, Jun 02, 2017 at 12:14:24PM +0100, Colin King wrote: > From: Colin Ian King > > functions m88e1510_get_temp_critical and m88e1510_get_temp_alarm can be > made static as they not need to be in global scope. > > Cleans up sparse warnings: > "symbol 'm88e1510_get_temp_alarm' was not

[GIT PULL 00/13] First batch of EFI updates for v4.13

The following changes since commit 5ed02dbb497422bf225783f46e6eadd237d23d6b: Linux 4.12-rc3 (2017-05-28 17:20:53 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-next for you to fetch changes up to

[GIT PULL 00/13] First batch of EFI updates for v4.13

The following changes since commit 5ed02dbb497422bf225783f46e6eadd237d23d6b: Linux 4.12-rc3 (2017-05-28 17:20:53 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-next for you to fetch changes up to

Re: [PATCH v3 3/8] nvmet: implement namespace identify descriptor list

On 06/02/2017 03:46 PM, Sagi Grimberg wrote: >> +uuid_beuuid; > > This should be uuid_le to match the rest of NVMe. Ahm, are you sure? $ PAGER= git grep -E uuid_\(l\|b\)e drivers/nvme drivers/nvme/host/fabrics.c:61: uuid_be_gen(>id); drivers/nvme/host/fabrics.c:78:

Re: [PATCH v3 3/8] nvmet: implement namespace identify descriptor list

On 06/02/2017 03:46 PM, Sagi Grimberg wrote: >> +uuid_beuuid; > > This should be uuid_le to match the rest of NVMe. Ahm, are you sure? $ PAGER= git grep -E uuid_\(l\|b\)e drivers/nvme drivers/nvme/host/fabrics.c:61: uuid_be_gen(>id); drivers/nvme/host/fabrics.c:78:

[PATCH 01/13] x86/efi: Clean up efi CR3 save/restore

From: Andy Lutomirski efi_call_phys_prolog() used to return a "pgd_t *" that meant one of three different things depending on kernel and system configuration. Clean it up so it uses a union and is more explicit about what's going on. Signed-off-by: Andy Lutomirski

[PATCH 01/13] x86/efi: Clean up efi CR3 save/restore

From: Andy Lutomirski efi_call_phys_prolog() used to return a "pgd_t *" that meant one of three different things depending on kernel and system configuration. Clean it up so it uses a union and is more explicit about what's going on. Signed-off-by: Andy Lutomirski Cc: Ard Biesheuvel Cc:

[PATCH 02/13] efi/capsule: Fix return code on failing kmap/vmap

From: Jan Kiszka If kmap or vmap fail, it means we ran out of memory. There are no user-provided addressed involved that would justify EFAULT. Signed-off-by: Jan Kiszka Reviewed-by: Matt Fleming Signed-off-by: Ard

[PATCH 02/13] efi/capsule: Fix return code on failing kmap/vmap

From: Jan Kiszka If kmap or vmap fail, it means we ran out of memory. There are no user-provided addressed involved that would justify EFAULT. Signed-off-by: Jan Kiszka Reviewed-by: Matt Fleming Signed-off-by: Ard Biesheuvel --- drivers/firmware/efi/capsule-loader.c | 4 ++-- 1 file

[PATCH 03/13] efi/capsule: Remove pr_debug on ENOMEM or EFAULT

From: Jan Kiszka Both cases are not worth a debug log message - the error code is telling enough. Signed-off-by: Jan Kiszka Reviewed-by: Matt Fleming Signed-off-by: Ard Biesheuvel ---

[PATCH 03/13] efi/capsule: Remove pr_debug on ENOMEM or EFAULT

From: Jan Kiszka Both cases are not worth a debug log message - the error code is telling enough. Signed-off-by: Jan Kiszka Reviewed-by: Matt Fleming Signed-off-by: Ard Biesheuvel --- drivers/firmware/efi/capsule-loader.c | 11 ++- 1 file changed, 2 insertions(+), 9 deletions(-)

[PATCH 10/13] efi/capsule: Add support for Quark security header

From: Jan Kiszka The firmware for Quark X102x prepends a security header to the capsule which is needed to support the mandatory secure boot on this processor. The header can be detected by checking for the "_CSH" signature and - to avoid any GUID conflict - validating

[PATCH 05/13] efi/capsule: Adjust return type of efi_capsule_setup_info

From: Jan Kiszka We actually expect int at the caller and never return any size information. Signed-off-by: Jan Kiszka Reviewed-by: Matt Fleming Signed-off-by: Ard Biesheuvel ---

[PATCH 10/13] efi/capsule: Add support for Quark security header

From: Jan Kiszka The firmware for Quark X102x prepends a security header to the capsule which is needed to support the mandatory secure boot on this processor. The header can be detected by checking for the "_CSH" signature and - to avoid any GUID conflict - validating its size field to contain

[PATCH 05/13] efi/capsule: Adjust return type of efi_capsule_setup_info

From: Jan Kiszka We actually expect int at the caller and never return any size information. Signed-off-by: Jan Kiszka Reviewed-by: Matt Fleming Signed-off-by: Ard Biesheuvel --- drivers/firmware/efi/capsule-loader.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [PATCH v3 2/5] crypto : stm32 - Add STM32F4 CRC32 support

Hi Fabien, Thanks for your review. On Mon, May 29, 2017 at 07:56:48AM +, Fabien DESSENNE wrote: > Hi Cosar, > > Thank you for the patch > > On 22/05/17 16:34, Cosar Dindar wrote: > > This patch adds CRC (CRC32 Crypto) support for STM32F4 series. > > > > As an hardware limitation polynomial

[PATCH 09/13] efi/capsule-loader: Use page addresses rather than struct page pointers

To give some leeway to code that handles non-standard capsule headers, let's keep an array of page addresses rather than struct page pointers. This gives special implementations of efi_capsule_setup_info() the opportunity to mangle the payload a bit before it is presented to the firmware, without

Re: [PATCH v3 2/5] crypto : stm32 - Add STM32F4 CRC32 support

Hi Fabien, Thanks for your review. On Mon, May 29, 2017 at 07:56:48AM +, Fabien DESSENNE wrote: > Hi Cosar, > > Thank you for the patch > > On 22/05/17 16:34, Cosar Dindar wrote: > > This patch adds CRC (CRC32 Crypto) support for STM32F4 series. > > > > As an hardware limitation polynomial

[PATCH 09/13] efi/capsule-loader: Use page addresses rather than struct page pointers

To give some leeway to code that handles non-standard capsule headers, let's keep an array of page addresses rather than struct page pointers. This gives special implementations of efi_capsule_setup_info() the opportunity to mangle the payload a bit before it is presented to the firmware, without

[PATCH 11/13] efi/efi_test: Use memdup_user() helper

From: Geliang Tang Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang Acked-by: Ivan Hu Cc: Ard Biesheuvel Signed-off-by: Matt Fleming

[PATCH 11/13] efi/efi_test: Use memdup_user() helper

From: Geliang Tang Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang Acked-by: Ivan Hu Cc: Ard Biesheuvel Signed-off-by: Matt Fleming Signed-off-by: Ard Biesheuvel --- drivers/firmware/efi/test/efi_test.c | 11 +++ 1 file changed, 3

[PATCH 07/13] efi/capsule: Remove NULL test on kmap()

From: Fabian Frederick kmap() can't fail. Signed-off-by: Fabian Frederick Cc: Ard Biesheuvel Cc: Kweh Hock Leong Signed-off-by: Matt Fleming Signed-off-by: Ard Biesheuvel

[PATCH 07/13] efi/capsule: Remove NULL test on kmap()

From: Fabian Frederick kmap() can't fail. Signed-off-by: Fabian Frederick Cc: Ard Biesheuvel Cc: Kweh Hock Leong Signed-off-by: Matt Fleming Signed-off-by: Ard Biesheuvel --- drivers/firmware/efi/capsule-loader.c | 4 drivers/firmware/efi/capsule.c| 4 2 files changed, 8

[PATCH 12/13] x86/efi: Add EFI_PGT_DUMP support for x86_32 and kexec

From: Sai Praneeth EFI_PGT_DUMP, as the name suggests dumps efi page tables to dmesg during kernel boot. This feature is very useful while debugging page faults/null pointer dereferences to efi related addresses. Presently, this feature is limited only to x86_64,

[PATCH 12/13] x86/efi: Add EFI_PGT_DUMP support for x86_32 and kexec

From: Sai Praneeth EFI_PGT_DUMP, as the name suggests dumps efi page tables to dmesg during kernel boot. This feature is very useful while debugging page faults/null pointer dereferences to efi related addresses. Presently, this feature is limited only to x86_64, so let's extend it to other efi

[PATCH 06/13] efi/capsule-loader: Use a cached copy of the capsule header

Instead of kmapping the capsule data twice, copy the capsule header into the capsule info struct we keep locally. This is an improvement by itself, but will also enable handling of non-standard header formats more easily. Reviewed-by: Matt Fleming Signed-off-by: Ard

[PATCH 04/13] efi/capsule: Clean up pr_err/info messages

From: Jan Kiszka Avoid __func__, improve the information provided by some of the messages. Signed-off-by: Jan Kiszka Reviewed-by: Matt Fleming Signed-off-by: Ard Biesheuvel ---

[PATCH 08/13] efi/capsule-loader: Redirect calls to efi_capsule_setup_info via weak alias

To allow platform specific code to hook into the capsule loading routines, indirect calls to efi_capsule_setup_info() via a weak alias of __efi_capsule_setup_info(), allowing platforms to redefine the former but still use the latter. Cc: Matt Fleming Tested-by: "Bryan

[PATCH 06/13] efi/capsule-loader: Use a cached copy of the capsule header

Instead of kmapping the capsule data twice, copy the capsule header into the capsule info struct we keep locally. This is an improvement by itself, but will also enable handling of non-standard header formats more easily. Reviewed-by: Matt Fleming Signed-off-by: Ard Biesheuvel ---

[PATCH 04/13] efi/capsule: Clean up pr_err/info messages

From: Jan Kiszka Avoid __func__, improve the information provided by some of the messages. Signed-off-by: Jan Kiszka Reviewed-by: Matt Fleming Signed-off-by: Ard Biesheuvel --- drivers/firmware/efi/capsule-loader.c | 19 --- 1 file changed, 8 insertions(+), 11 deletions(-)

[PATCH 08/13] efi/capsule-loader: Redirect calls to efi_capsule_setup_info via weak alias

To allow platform specific code to hook into the capsule loading routines, indirect calls to efi_capsule_setup_info() via a weak alias of __efi_capsule_setup_info(), allowing platforms to redefine the former but still use the latter. Cc: Matt Fleming Tested-by: "Bryan O'Donoghue" Signed-off-by:

[PATCH 13/13] efi: arm: enable DMI/SMBIOS

Wire up the existing arm64 support for SMBIOS tables (aka DMI) for ARM as well, by moving the arm64 init code to drivers/firmware/efi/arm-runtime.c (which is shared between ARM and arm64), and adding a asm/dmi.h header to ARM that defines the mapping routines for the firmware tables. This allows

[PATCH 13/13] efi: arm: enable DMI/SMBIOS

Wire up the existing arm64 support for SMBIOS tables (aka DMI) for ARM as well, by moving the arm64 init code to drivers/firmware/efi/arm-runtime.c (which is shared between ARM and arm64), and adding a asm/dmi.h header to ARM that defines the mapping routines for the firmware tables. This allows

Re: [PATCH net] net: dsa: Move dsa_switch_{suspend,resume} out of legacy.c

On Thu, Jun 01, 2017 at 07:53:04PM -0700, Florian Fainelli wrote: > dsa_switch_suspend() and dsa_switch_resume() are functions that belong in > net/dsa/dsa.c and are not part of the legacy platform support code. > > Fixes: a6a71f19fe5e ("net: dsa: isolate legacy code") > Signed-off-by: Florian

Re: [PATCH net] net: dsa: Move dsa_switch_{suspend,resume} out of legacy.c

On Thu, Jun 01, 2017 at 07:53:04PM -0700, Florian Fainelli wrote: > dsa_switch_suspend() and dsa_switch_resume() are functions that belong in > net/dsa/dsa.c and are not part of the legacy platform support code. > > Fixes: a6a71f19fe5e ("net: dsa: isolate legacy code") > Signed-off-by: Florian

[GIT PULL] sound fixes for 4.12-rc4

Linus, please pull sound fixes for v4.12-rc4 from: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-4.12-rc4 The topmost commit is d2c3b14e1f0dcebdb695617c0c1342a36b914a47 sound fixes for 4.12-rc4

[GIT PULL] sound fixes for 4.12-rc4

Linus, please pull sound fixes for v4.12-rc4 from: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git tags/sound-4.12-rc4 The topmost commit is d2c3b14e1f0dcebdb695617c0c1342a36b914a47 sound fixes for 4.12-rc4

Re: [PATCH v2 0/7] Improve ap806 clk support on Marvell Armada 7K/8K

Hi Michael, On jeu., juin 01 2017, Michael Turquette wrote: > Hi Gregory, > > Quoting Gregory CLEMENT (2017-05-31 23:07:21) >> Hi, >> >> This series modifies the device tree binding of the clock of the AP806 >> part that we find in the Marvell Armada 7K/8K SoCs. >>

Re: [PATCH v2 0/7] Improve ap806 clk support on Marvell Armada 7K/8K

Hi Michael, On jeu., juin 01 2017, Michael Turquette wrote: > Hi Gregory, > > Quoting Gregory CLEMENT (2017-05-31 23:07:21) >> Hi, >> >> This series modifies the device tree binding of the clock of the AP806 >> part that we find in the Marvell Armada 7K/8K SoCs. >> >> As for the previsous

Re: [PATCH] ahci: qoriq: add ls1088a platforms support

On Fri, Jun 02, 2017 at 03:23:03PM +0800, Yuantian Tang wrote: > Ls1088a is new introduced arm-based soc with sata support with > following features: > > * Complies with the serial ATA 3.0 specification > and the AHCI 1.3.1 specification > * Contains a high-speed descriptor-based DMA controller

Re: [PATCH] ahci: qoriq: add ls1088a platforms support

On Fri, Jun 02, 2017 at 03:23:03PM +0800, Yuantian Tang wrote: > Ls1088a is new introduced arm-based soc with sata support with > following features: > > * Complies with the serial ATA 3.0 specification > and the AHCI 1.3.1 specification > * Contains a high-speed descriptor-based DMA controller

Re: [PATCH v3 00/19] Report power supply from hid-logitech-hidpp

On Jun 02 2017 or thereabouts, Bastien Nocera wrote: > On Fri, 2017-06-02 at 09:29 +0200, Benjamin Tissoires wrote: > > > > > Bastien, is is possible to have a simple udev rule that tells upower > > to > > ignore the battery device if builtin_power_supply is there? > > That way we can tell

Re: [PATCH v3 00/19] Report power supply from hid-logitech-hidpp

On Jun 02 2017 or thereabouts, Bastien Nocera wrote: > On Fri, 2017-06-02 at 09:29 +0200, Benjamin Tissoires wrote: > > > > > Bastien, is is possible to have a simple udev rule that tells upower > > to > > ignore the battery device if builtin_power_supply is there? > > That way we can tell

Re: [PATCH v3 3/8] nvmet: implement namespace identify descriptor list

switch (type) { case NVME_NQN_NVME: diff --git a/drivers/nvme/target/nvmet.h b/drivers/nvme/target/nvmet.h index cfc5c7fb0ab7..4c6cb5ea1186 100644 --- a/drivers/nvme/target/nvmet.h +++ b/drivers/nvme/target/nvmet.h @@ -46,6 +46,7 @@ struct nvmet_ns { u32

Re: [PATCH v3 3/8] nvmet: implement namespace identify descriptor list

switch (type) { case NVME_NQN_NVME: diff --git a/drivers/nvme/target/nvmet.h b/drivers/nvme/target/nvmet.h index cfc5c7fb0ab7..4c6cb5ea1186 100644 --- a/drivers/nvme/target/nvmet.h +++ b/drivers/nvme/target/nvmet.h @@ -46,6 +46,7 @@ struct nvmet_ns { u32

Re: [PATCH V2] ARM: cpuidle: Support asymmetric idle definition

On 02/06/17 11:40, Daniel Lezcano wrote: > On 02/06/2017 12:14, Sudeep Holla wrote: >> >> >> On 02/06/17 11:06, Daniel Lezcano wrote: >>> On 02/06/2017 11:39, Sudeep Holla wrote: On 02/06/17 10:25, Daniel Lezcano wrote: > On 02/06/2017 11:20, Sudeep Holla wrote: >> >>

Re: [PATCH V2] ARM: cpuidle: Support asymmetric idle definition

On 02/06/17 11:40, Daniel Lezcano wrote: > On 02/06/2017 12:14, Sudeep Holla wrote: >> >> >> On 02/06/17 11:06, Daniel Lezcano wrote: >>> On 02/06/2017 11:39, Sudeep Holla wrote: On 02/06/17 10:25, Daniel Lezcano wrote: > On 02/06/2017 11:20, Sudeep Holla wrote: >> >>

Re: [PATCH 0/3] staging:typec: Fix 3 defect of incorrect type

On 06/01/2017 12:20 AM, ? ? wrote: From: Pan Li Pan Li (3): Fix one defect of incorrect type in argument. Fix one defect of incorrect type assignment. Fix one defect of incorrect type assignment. drivers/staging/typec/tcpci.c | 6 +++--- 1 file

Re: [PATCH 0/3] staging:typec: Fix 3 defect of incorrect type

On 06/01/2017 12:20 AM, ? ? wrote: From: Pan Li Pan Li (3): Fix one defect of incorrect type in argument. Fix one defect of incorrect type assignment. Fix one defect of incorrect type assignment. drivers/staging/typec/tcpci.c | 6 +++--- 1 file changed, 3 insertions(+), 3

Re: [LTP] [lkp-robot] [KEYS] bdf7c0f8bf: ltp.add_key02.fail

Eric Biggers wrote: > I'll plan to send a patch. Also, it looks like the testing that LTP does of > add_key() is very sparse, so I'll try to extend it a bit. There's more testing in the testsuite that's with the keyutils package. David

Re: [LTP] [lkp-robot] [KEYS] bdf7c0f8bf: ltp.add_key02.fail

Eric Biggers wrote: > I'll plan to send a patch. Also, it looks like the testing that LTP does of > add_key() is very sparse, so I'll try to extend it a bit. There's more testing in the testsuite that's with the keyutils package. David

Re: [PATCH v4 0/3] clk: rockchip: support clk controller for RK3128 SoC

Hi Elaine, Am Freitag, 2. Juni 2017, 09:47:22 CEST schrieb Elaine Zhang: > The driver and clk ID\SRST ID it's also applies to the RK3126 SoC. applied all 3 for 4.13 (taking Rob's Ack from v1 for the first 2 patches) Thanks Heiko

Re: [PATCH v4 0/3] clk: rockchip: support clk controller for RK3128 SoC

Hi Elaine, Am Freitag, 2. Juni 2017, 09:47:22 CEST schrieb Elaine Zhang: > The driver and clk ID\SRST ID it's also applies to the RK3126 SoC. applied all 3 for 4.13 (taking Rob's Ack from v1 for the first 2 patches) Thanks Heiko

Kernel 3.18.55 compilation fails (missing function declaration)

Hi, kernel 3.18.55 compilation fails with this error: kernel/fork.c: In function ‘dup_task_struct’: kernel/fork.c:341:2: error: implicit declaration of function ‘get_random_long’ [-Werror=implicit-function-declaration] tsk->stack_canary = get_random_long(); Corrected by adding the declaration to

Kernel 3.18.55 compilation fails (missing function declaration)

Hi, kernel 3.18.55 compilation fails with this error: kernel/fork.c: In function ‘dup_task_struct’: kernel/fork.c:341:2: error: implicit declaration of function ‘get_random_long’ [-Werror=implicit-function-declaration] tsk->stack_canary = get_random_long(); Corrected by adding the declaration to

Re: [PATCH 08/10] KVM: arm/arm64: vgic: Handle unshared mapped interrupts

On Wed, May 24, 2017 at 10:13:21PM +0200, Eric Auger wrote: > Virtual interrupts directly mapped to physical interrupts require > some special care. Their pending and active state must be observed > at distributor level and not in the list register. This is not entirely true. There's a

Re: [PATCH 08/10] KVM: arm/arm64: vgic: Handle unshared mapped interrupts

On Wed, May 24, 2017 at 10:13:21PM +0200, Eric Auger wrote: > Virtual interrupts directly mapped to physical interrupts require > some special care. Their pending and active state must be observed > at distributor level and not in the list register. This is not entirely true. There's a

Re: hwmon: pwm-fan: switch to new atomic PWM API

On Mon, Apr 24, 2017 at 03:13:17PM +0200, Bartlomiej Zolnierkiewicz wrote: > Switch pwm-fan driver to new atomic PWM API. > > Signed-off-by: Bartlomiej Zolnierkiewicz > --- > Depends on "[PATCH v2 0/3] pwm: pwm-samsung: fix suspend/resume support" > patchset

Re: hwmon: pwm-fan: switch to new atomic PWM API

On Mon, Apr 24, 2017 at 03:13:17PM +0200, Bartlomiej Zolnierkiewicz wrote: > Switch pwm-fan driver to new atomic PWM API. > > Signed-off-by: Bartlomiej Zolnierkiewicz > --- > Depends on "[PATCH v2 0/3] pwm: pwm-samsung: fix suspend/resume support" > patchset

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On 06/02/2017 12:53 PM, Martin Schwidefsky wrote: > On Fri, 2 Jun 2017 12:19:19 +0200 > Christian Borntraeger wrote: > >> On 06/02/2017 11:46 AM, Martin Schwidefsky wrote: >>> On Fri, 2 Jun 2017 09:02:10 +0200 >>> Heiko Carstens wrote: >>>

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On 06/02/2017 12:53 PM, Martin Schwidefsky wrote: > On Fri, 2 Jun 2017 12:19:19 +0200 > Christian Borntraeger wrote: > >> On 06/02/2017 11:46 AM, Martin Schwidefsky wrote: >>> On Fri, 2 Jun 2017 09:02:10 +0200 >>> Heiko Carstens wrote: >>> On Thu, Jun 01, 2017 at 12:46:51PM +0200,

Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a

Am Freitag, den 02.06.2017, 10:30 +0200 schrieb Richard Weinberger: > Thomas, > > Am 02.06.2017 um 10:04 schrieb Thomas Meyer: > > Am Donnerstag, den 01.06.2017, 22:49 -0700 schrieb Florian > > Fainelli: > > I see this in the kernel log: > > > > [0.00] [ cut here

Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a

Am Freitag, den 02.06.2017, 10:30 +0200 schrieb Richard Weinberger: > Thomas, > > Am 02.06.2017 um 10:04 schrieb Thomas Meyer: > > Am Donnerstag, den 01.06.2017, 22:49 -0700 schrieb Florian > > Fainelli: > > I see this in the kernel log: > > > > [0.00] [ cut here

Re: [PATCH] virtio_net: lower limit on buffer size

On Fri, 2 Jun 2017, Michael S. Tsirkin wrote: > commit d85b758f72b0 "virtio_net: fix support for small rings" > was supposed to increase the buffer size for small rings > but had an unintentional side effect of decreasing > it for large rings. This seems to break some setups - > it's not yet

Re: [PATCH] virtio_net: lower limit on buffer size

On Fri, 2 Jun 2017, Michael S. Tsirkin wrote: > commit d85b758f72b0 "virtio_net: fix support for small rings" > was supposed to increase the buffer size for small rings > but had an unintentional side effect of decreasing > it for large rings. This seems to break some setups - > it's not yet

[PATCH] regmap: make LZO cache optional

Commit 2cbbb579bcbe3 ("regmap: Add the LZO cache support") added support for LZO compression in regcache, but there were never any users added afterwards. Since LZO support itself has its own size, it currently is rather a deoptimization. So make it optional by introducing a symbol that can be

[PATCH] regmap: make LZO cache optional

Commit 2cbbb579bcbe3 ("regmap: Add the LZO cache support") added support for LZO compression in regcache, but there were never any users added afterwards. Since LZO support itself has its own size, it currently is rather a deoptimization. So make it optional by introducing a symbol that can be

Re: [PATCH v2 linux-next 3/3] spi: imx: Add support for SPI Slave mode

Hi Sascha On 05/31/2017 05:10 AM, Sascha Hauer wrote: > On Wed, May 31, 2017 at 02:19:58AM -0700, jiada_w...@mentor.com wrote: >> From: Jiada Wang >> >> Previously i.MX SPI controller only works in Master mode. >> This patch adds support to i.MX51, i.MX53 and i.MX6 ECSPI

Re: [PATCH v2 linux-next 3/3] spi: imx: Add support for SPI Slave mode

Hi Sascha On 05/31/2017 05:10 AM, Sascha Hauer wrote: > On Wed, May 31, 2017 at 02:19:58AM -0700, jiada_w...@mentor.com wrote: >> From: Jiada Wang >> >> Previously i.MX SPI controller only works in Master mode. >> This patch adds support to i.MX51, i.MX53 and i.MX6 ECSPI >> controller to work

Support for RGB/YUV 10, 12 BPC(bits per color/component) image data formats in kernel

Hi all, I have tried searching for RGB/YUV 10, 12 BPC formats in videodev2.h, media-bus-format.h and drm_fourcc.h I could only find RGB 10BPC support in drm_fourcc.h. I guess not much support is present for formats with (BPC > 8) in the kernel. Are there any plans to add fourcc defines for such

Support for RGB/YUV 10, 12 BPC(bits per color/component) image data formats in kernel

Hi all, I have tried searching for RGB/YUV 10, 12 BPC formats in videodev2.h, media-bus-format.h and drm_fourcc.h I could only find RGB 10BPC support in drm_fourcc.h. I guess not much support is present for formats with (BPC > 8) in the kernel. Are there any plans to add fourcc defines for such

Re: hexagon: Use raw_copy_to_user

ping On Tue, May 02, 2017 at 08:52:48PM -0700, Guenter Roeck wrote: > Commit ac4691fac8ad ("hexagon: switch to RAW_COPY_USER") replaced > __copy_to_user_hexagon() with raw_copy_to_user(), but did not catch > all callers, resulting in the following build error. > > arch/hexagon/mm/uaccess.c:

Re: hexagon: Use raw_copy_to_user

ping On Tue, May 02, 2017 at 08:52:48PM -0700, Guenter Roeck wrote: > Commit ac4691fac8ad ("hexagon: switch to RAW_COPY_USER") replaced > __copy_to_user_hexagon() with raw_copy_to_user(), but did not catch > all callers, resulting in the following build error. > > arch/hexagon/mm/uaccess.c:

[PATCH v7 1/3] dt-bindings:phy:Add DT bindings documentation for NS2 USB DRD phy

This patch adds documentation for NS2 DRD Phy driver DT bindings Signed-off-by: Raviteja Garimella Acked-by: Rob Herring --- .../devicetree/bindings/phy/brcm,ns2-drd-phy.txt | 30 ++ 1 file changed, 30 insertions(+)

[PATCH v7 2/3] phy:phy-bcm-ns2-usbdrd:Broadcom USB DRD Phy driver for Northstar2

This is driver for USB DRD Phy used in Broadcom's Northstar2 SoC. The phy can be configured to be in Device mode or Host mode based on the type of cable connected to the port. The driver registers to extcon framework to get appropriate connect events for Host/Device cables connect/disconnect

[PATCH v7 0/3] Support for USB DRD Phy driver for NS2

Changes in v7: = Cleaned up unused variables in phy private data structure that's missed out in v6. Setting of phy mode to device/host is removed from phy power on. routine. Changes in v6: = Removed spin locks which are not required as the references to phy_ops in the same

[PATCH v7 3/3] arm64: dts: NS2: Add USB DRD PHY device tree node

This patch adds device tree node for USB Dual Role Device Phy for Broadcom's Northstar2 SoC. Signed-off-by: Raviteja Garimella --- arch/arm64/boot/dts/broadcom/ns2.dtsi | 14 ++ 1 file changed, 14 insertions(+) diff --git

[PATCH v7 1/3] dt-bindings:phy:Add DT bindings documentation for NS2 USB DRD phy

This patch adds documentation for NS2 DRD Phy driver DT bindings Signed-off-by: Raviteja Garimella Acked-by: Rob Herring --- .../devicetree/bindings/phy/brcm,ns2-drd-phy.txt | 30 ++ 1 file changed, 30 insertions(+) create mode 100644

[PATCH v7 2/3] phy:phy-bcm-ns2-usbdrd:Broadcom USB DRD Phy driver for Northstar2

This is driver for USB DRD Phy used in Broadcom's Northstar2 SoC. The phy can be configured to be in Device mode or Host mode based on the type of cable connected to the port. The driver registers to extcon framework to get appropriate connect events for Host/Device cables connect/disconnect

[PATCH v7 0/3] Support for USB DRD Phy driver for NS2

Changes in v7: = Cleaned up unused variables in phy private data structure that's missed out in v6. Setting of phy mode to device/host is removed from phy power on. routine. Changes in v6: = Removed spin locks which are not required as the references to phy_ops in the same

[PATCH v7 3/3] arm64: dts: NS2: Add USB DRD PHY device tree node

This patch adds device tree node for USB Dual Role Device Phy for Broadcom's Northstar2 SoC. Signed-off-by: Raviteja Garimella --- arch/arm64/boot/dts/broadcom/ns2.dtsi | 14 ++ 1 file changed, 14 insertions(+) diff --git a/arch/arm64/boot/dts/broadcom/ns2.dtsi

[PATCH] kbuild: switch to thin archives

Switch from incremental build to thin archives for packaging built-in.o. binutils version must be bumped to 2.20. Proposed patch for 4.13. Signed-off-by: Nicholas Piggin --- Documentation/process/changes.rst | 9 - Makefile | 3 +++

[PATCH] kbuild: switch to thin archives

Switch from incremental build to thin archives for packaging built-in.o. binutils version must be bumped to 2.20. Proposed patch for 4.13. Signed-off-by: Nicholas Piggin --- Documentation/process/changes.rst | 9 - Makefile | 3 +++ arch/Kconfig

Re: [PATCH v3 00/19] Report power supply from hid-logitech-hidpp

On Fri, 2017-06-02 at 09:29 +0200, Benjamin Tissoires wrote: > > Bastien, is is possible to have a simple udev rule that tells upower > to > ignore the battery device if builtin_power_supply is there? > That way we can tell people running old upower to use this to be sure > to > ignore the

Re: [PATCH v3 00/19] Report power supply from hid-logitech-hidpp

On Fri, 2017-06-02 at 09:29 +0200, Benjamin Tissoires wrote: > > Bastien, is is possible to have a simple udev rule that tells upower > to > ignore the battery device if builtin_power_supply is there? > That way we can tell people running old upower to use this to be sure > to > ignore the

<    6   7   8   9   10   11   12   13   14   15   >