RE: [PATCH][v3] ACPI: Do not report _OSI("Darwin") when acpi_osi=!Darwin provided

Hi, Yu > From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi- > ow...@vger.kernel.org] On Behalf Of Chen Yu > Subject: [PATCH][v3] ACPI: Do not report _OSI("Darwin") when > acpi_osi=!Darwin provided > > Commit 7bc5a2bad0b8 ("ACPI: Support _OSI("Darwin") correctly") always > reports

Re: [PATCH v2 0/8] EC-based USB Power Delivery support for Chrome machines

On 20 February 2016 at 17:22, Pavel Machek wrote: > Hi! > >> this series contains a driver that exposes a power_supply to userspace >> representing a port that support USB PD charging. > > Well, if this is meant for userspace, should it add some > documentation, too? Hi Pavel, in

Re: [PATCH v2 0/8] EC-based USB Power Delivery support for Chrome machines

On 20 February 2016 at 17:22, Pavel Machek wrote: > Hi! > >> this series contains a driver that exposes a power_supply to userspace >> representing a port that support USB PD charging. > > Well, if this is meant for userspace, should it add some > documentation, too? Hi Pavel, in v3 I have

RE: [PATCH][v3] ACPI: Do not report _OSI("Darwin") when acpi_osi=!Darwin provided

Hi, Yu > From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi- > ow...@vger.kernel.org] On Behalf Of Chen Yu > Subject: [PATCH][v3] ACPI: Do not report _OSI("Darwin") when > acpi_osi=!Darwin provided > > Commit 7bc5a2bad0b8 ("ACPI: Support _OSI("Darwin") correctly") always > reports

[PATCH v3 3/3] ARM: dts: use syscon in cygnus touchscreen dt node

In Cygnus SOC touch screen controller registers are shared with ADC and flex timer. Using readl/writel could lead to race condition. So in such case register access is handled through syscon framework API's in the touch screen driver. This feature is enabled if "brcm,iproc-touchscreen-syscon"

[PATCH v3 3/3] ARM: dts: use syscon in cygnus touchscreen dt node

In Cygnus SOC touch screen controller registers are shared with ADC and flex timer. Using readl/writel could lead to race condition. So in such case register access is handled through syscon framework API's in the touch screen driver. This feature is enabled if "brcm,iproc-touchscreen-syscon"

[PATCH v3 2/3] input: syscon support in bcm_iproc_tsc driver

In Cygnus SOC touch screen controller registers are shared with ADC and flex timer. Using readl/writel could lead to race condition. So touch screen driver is enhanced to support 1. If touchscreen register's are not shared. Register access is handled through readl/writel if

[PATCH v3 2/3] input: syscon support in bcm_iproc_tsc driver

In Cygnus SOC touch screen controller registers are shared with ADC and flex timer. Using readl/writel could lead to race condition. So touch screen driver is enhanced to support 1. If touchscreen register's are not shared. Register access is handled through readl/writel if

[PATCH v3 0/3] Syscon support for iProc touchscreen driver

This patchset is based on v4.5-rc3 tag and its tested on Broadcom Cygnus SoC. The patches can be fetched from iproc-tsc-v3 branch of https://github.com/Broadcom/arm64-linux.git Changes since v2: - Omitted '0x' in "tsc node" definition in dt documentation file - Omitted '0x' in "ts_adc_syscon"

[PATCH v3 0/3] Syscon support for iProc touchscreen driver

This patchset is based on v4.5-rc3 tag and its tested on Broadcom Cygnus SoC. The patches can be fetched from iproc-tsc-v3 branch of https://github.com/Broadcom/arm64-linux.git Changes since v2: - Omitted '0x' in "tsc node" definition in dt documentation file - Omitted '0x' in "ts_adc_syscon"

[PATCH v3 1/3] input: cygnus-update touchscreen dt node document

In Cygnus SOC touch screen controller registers are shared with ADC and flex timer. Using readl/writel could lead to race condition. So touch screen driver is enhanced to support 1. If touchscreen register's are not shared. Register access is handled through readl/writel if

[PATCH v3 1/3] input: cygnus-update touchscreen dt node document

In Cygnus SOC touch screen controller registers are shared with ADC and flex timer. Using readl/writel could lead to race condition. So touch screen driver is enhanced to support 1. If touchscreen register's are not shared. Register access is handled through readl/writel if

[PATCH v16 2/8] perf config: Add 'list-all' option to perf-config

'list-all' option is to display both current config variables and all possible config variables with default values. The syntax examples are like below perf config [] [options] display all perf config with default values. # perf config -a | --list-all Cc: Namhyung Kim

[PATCH v16 4/8] perf config: Add --verbose option for showing config description

To explain what each of variable options configures, this option can be used with 'skel', 'list' and 'list-all' options, i.e. print the possible config variables with comments over each of them. # perf config -vk | --verbose --skel or print all or current config variables with

[PATCH v16 2/8] perf config: Add 'list-all' option to perf-config

'list-all' option is to display both current config variables and all possible config variables with default values. The syntax examples are like below perf config [] [options] display all perf config with default values. # perf config -a | --list-all Cc: Namhyung Kim Cc: Jiri Olsa

[PATCH v16 4/8] perf config: Add --verbose option for showing config description

To explain what each of variable options configures, this option can be used with 'skel', 'list' and 'list-all' options, i.e. print the possible config variables with comments over each of them. # perf config -vk | --verbose --skel or print all or current config variables with

[PATCH v16 5/8] perf config: Add 'get' functionality

This patch consists of functions which can get specific config variables. For the syntax examples, perf config [] [section.name ...] display key-value pairs of specific config variables # perf config report.queue-size report.children In addition, the functionality can work with

[PATCH v16 5/8] perf config: Add 'get' functionality

This patch consists of functions which can get specific config variables. For the syntax examples, perf config [] [section.name ...] display key-value pairs of specific config variables # perf config report.queue-size report.children In addition, the functionality can work with

[PATCH v16 6/8] perf config: Add 'set' functionality

This patch consists of functions which can set specific config variables. For the syntax examples, perf config [] [options] [section.name[=value] ...] set specific config variables # perf config report.queue-size=100M report.children=true Cc: Namhyung Kim Cc:

[PATCH v16 8/8] perf config: Add a option 'remove' to perf-config

A option 'remove' is to remove specific config variables. For the syntax examples, # perf config [] -r | --remove [section.name ...] Cc: Namhyung Kim Cc: Jiri Olsa Signed-off-by: Taeung Song ---

[PATCH v16 6/8] perf config: Add 'set' functionality

This patch consists of functions which can set specific config variables. For the syntax examples, perf config [] [options] [section.name[=value] ...] set specific config variables # perf config report.queue-size=100M report.children=true Cc: Namhyung Kim Cc: Jiri Olsa

[PATCH v16 8/8] perf config: Add a option 'remove' to perf-config

A option 'remove' is to remove specific config variables. For the syntax examples, # perf config [] -r | --remove [section.name ...] Cc: Namhyung Kim Cc: Jiri Olsa Signed-off-by: Taeung Song --- tools/perf/Documentation/perf-config.txt | 6 ++ tools/perf/builtin-config.c

[PATCH v16 7/8] perf config: normalize a value depending on default type of it

Whether or not user mis-type wrong data type to set config, normalize the value. If a config user enter isn't contained in default configs, just pass as it is. For the examples, # perf config report.queue-size=1M # perf config report.queue-size report.queue-size=1048576 Cc: Namhyung Kim

[PATCH v16 1/8] perf config: Collect configs to handle config variables

Collecting configs into list because of two reason. First of all, if there are same variables both user and system config file, they all will be printed when 'list' command work. But if config variables are duplicated, user config variables should only be printed because it has priority. Lastly,

[PATCH v16 3/8] perf config: Add a option 'skel' to perf-config

Produce an skeleton with the possible config variables so that one could then use $EDITOR ~/.perfconfig or $(sysconfdir)/perfconfigand go on setting the knobs. For the syntax examples, # perf config -k | --skel Initialize the possible config variables on config file. # perf config

[PATCH v16 7/8] perf config: normalize a value depending on default type of it

Whether or not user mis-type wrong data type to set config, normalize the value. If a config user enter isn't contained in default configs, just pass as it is. For the examples, # perf config report.queue-size=1M # perf config report.queue-size report.queue-size=1048576 Cc: Namhyung Kim

[PATCH v16 1/8] perf config: Collect configs to handle config variables

Collecting configs into list because of two reason. First of all, if there are same variables both user and system config file, they all will be printed when 'list' command work. But if config variables are duplicated, user config variables should only be printed because it has priority. Lastly,

[PATCH v16 3/8] perf config: Add a option 'skel' to perf-config

Produce an skeleton with the possible config variables so that one could then use $EDITOR ~/.perfconfig or $(sysconfdir)/perfconfigand go on setting the knobs. For the syntax examples, # perf config -k | --skel Initialize the possible config variables on config file. # perf config

[PATCHSET v16 0/8] perf config: Add several functionalities into perf-config

Hello, This patchset implements new functionalities for perf-config subcommand. Add options (list-all, skel, verbose, remove) and getting and setting functionalities into perf-config subcommand to more useful. Changes in v16: - rebased onto the current tip/perf/core Changes in v15:

[PATCHSET v16 0/8] perf config: Add several functionalities into perf-config

Hello, This patchset implements new functionalities for perf-config subcommand. Add options (list-all, skel, verbose, remove) and getting and setting functionalities into perf-config subcommand to more useful. Changes in v16: - rebased onto the current tip/perf/core Changes in v15:

[PATCH 1/6] ARM: decompressor: drop unneeded assignments to "targets"

The "targets" exists to specify which files need the corresponding ".*_cmd" files to be included during the build. In other words, it is used for files that need to detect the change of the command line by if_changed, if_changed_dep, and if_changed_rule. While, these files are just copied by

[PATCH 2/6] ARM: decompressor: drop more unneeded assignments to "targets"

The objects "font.o" and "misc.o" are contained in $(OBJS), and it is already added to the "targets". Signed-off-by: Masahiro Yamada --- arch/arm/boot/compressed/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 5/6] ARM: decompressor: merge piggy.*.S and simplify Makefile

The files piggy.$(suffix).S are similar enough to be merged into a single file. This also allows clean up of the Makefile. Signed-off-by: Masahiro Yamada --- arch/arm/boot/compressed/.gitignore| 6 +- arch/arm/boot/compressed/Makefile

Re: Nokia N900: musb is in wrong state after boot

Pali Rohár writes: > On Tuesday 26 January 2016 18:26:32 Tony Lindgren wrote: >> * Pali Rohár [160126 06:35]: >> > On Thursday 21 January 2016 12:30:13 Tony Lindgren wrote: >> > > * joerg Reisenweber [160121 11:35]: >> > > > On

[PATCH 2/6] ARM: decompressor: drop more unneeded assignments to "targets"

The objects "font.o" and "misc.o" are contained in $(OBJS), and it is already added to the "targets". Signed-off-by: Masahiro Yamada --- arch/arm/boot/compressed/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/compressed/Makefile

[PATCH 5/6] ARM: decompressor: merge piggy.*.S and simplify Makefile

The files piggy.$(suffix).S are similar enough to be merged into a single file. This also allows clean up of the Makefile. Signed-off-by: Masahiro Yamada --- arch/arm/boot/compressed/.gitignore| 6 +- arch/arm/boot/compressed/Makefile | 14 ++

Re: Nokia N900: musb is in wrong state after boot

Pali Rohár writes: > On Tuesday 26 January 2016 18:26:32 Tony Lindgren wrote: >> * Pali Rohár [160126 06:35]: >> > On Thursday 21 January 2016 12:30:13 Tony Lindgren wrote: >> > > * joerg Reisenweber [160121 11:35]: >> > > > On Thu 21 January 2016 11:21:13 Tony Lindgren wrote: >> > > > > Do

[PATCH 1/6] ARM: decompressor: drop unneeded assignments to "targets"

The "targets" exists to specify which files need the corresponding ".*_cmd" files to be included during the build. In other words, it is used for files that need to detect the change of the command line by if_changed, if_changed_dep, and if_changed_rule. While, these files are just copied by

[PATCH 0/6] ARM: decompressor: several cleanups

Masahiro Yamada (6): ARM: decompressor: drop unneeded assignments to "targets" ARM: decompressor: drop more unneeded assignments to "targets" ARM: decompressor: use clean-files instead of extra-y to clean files ARM: decompressor: drop redundant FORCE in Makefile ARM: decompressor:

[PATCH 0/6] ARM: decompressor: several cleanups

Masahiro Yamada (6): ARM: decompressor: drop unneeded assignments to "targets" ARM: decompressor: drop more unneeded assignments to "targets" ARM: decompressor: use clean-files instead of extra-y to clean files ARM: decompressor: drop redundant FORCE in Makefile ARM: decompressor:

[PATCH 3/6] ARM: decompressor: use clean-files instead of extra-y to clean files

This code works fine here, but it is tricky to use "extra-y" for specifying files to be removed during "make clean". Kbuild provides "clean-files" for this purpose. Signed-off-by: Masahiro Yamada --- arch/arm/boot/compressed/Makefile | 3 +-- 1 file changed, 1

[PATCH 3/6] ARM: decompressor: use clean-files instead of extra-y to clean files

This code works fine here, but it is tricky to use "extra-y" for specifying files to be removed during "make clean". Kbuild provides "clean-files" for this purpose. Signed-off-by: Masahiro Yamada --- arch/arm/boot/compressed/Makefile | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

[PATCH 6/6] ARM: decompressor: rename suffix_y to compress-y

The "$(suffix_y)" no longer appears in the file names, but it just specifies the method of the file compression. The "compress-y" sounds more suitable. Signed-off-by: Masahiro Yamada --- arch/arm/boot/compressed/Makefile | 12 ++-- 1 file changed, 6

[PATCH 6/6] ARM: decompressor: rename suffix_y to compress-y

The "$(suffix_y)" no longer appears in the file names, but it just specifies the method of the file compression. The "compress-y" sounds more suitable. Signed-off-by: Masahiro Yamada --- arch/arm/boot/compressed/Makefile | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff

[PATCH 4/6] ARM: decompressor: drop redundant FORCE in Makefile

The object "piggy.$(suffix_y).o" is created from "piggy.$(suffix).S" by the following pattern rule defined in scripts/Makefile.build: $(obj)/%.o: $(src)/%.S FORCE $(call if_changed_dep,as_o_S) FORCE is already added to the prerequisite of the object there. Signed-off-by: Masahiro

[PATCH 4/6] ARM: decompressor: drop redundant FORCE in Makefile

The object "piggy.$(suffix_y).o" is created from "piggy.$(suffix).S" by the following pattern rule defined in scripts/Makefile.build: $(obj)/%.o: $(src)/%.S FORCE $(call if_changed_dep,as_o_S) FORCE is already added to the prerequisite of the object there. Signed-off-by: Masahiro

RE: [PATCH] ACPI / button: Avoid using broken _LID on Surface tablet

Hi, Yu > From: Chen, Yu C > Subject: RE: [PATCH] ACPI / button: Avoid using broken _LID on Surface tablet > > Hi Lv, > > > From: Zheng, Lv > > Subject: RE: [PATCH] ACPI / button: Avoid using broken _LID on Surface > > tablet > > > > Hi, Yu > > > > > From: linux-acpi-ow...@vger.kernel.org > > >

RE: [PATCH] ACPI / button: Avoid using broken _LID on Surface tablet

Hi, Yu > From: Chen, Yu C > Subject: RE: [PATCH] ACPI / button: Avoid using broken _LID on Surface tablet > > Hi Lv, > > > From: Zheng, Lv > > Subject: RE: [PATCH] ACPI / button: Avoid using broken _LID on Surface > > tablet > > > > Hi, Yu > > > > > From: linux-acpi-ow...@vger.kernel.org > > >

Re: [PATCH 1/2] ARM: OMAP1: DMA: Provide dma_slave_map to omap-dma

On 2016-02-19 23:44, Aaro Koskinen wrote: > On Tue, Feb 02, 2016 at 04:27:06PM +0200, Peter Ujfalusi wrote: >> OMAP1 can not boot in DT mode and to be able to clean up the driver >> regarding to the dmaengine API use (switching to the new API) the >> device/slave -> filter mapping needs to be

Re: [PATCH 1/2] ARM: OMAP1: DMA: Provide dma_slave_map to omap-dma

On 2016-02-19 23:44, Aaro Koskinen wrote: > On Tue, Feb 02, 2016 at 04:27:06PM +0200, Peter Ujfalusi wrote: >> OMAP1 can not boot in DT mode and to be able to clean up the driver >> regarding to the dmaengine API use (switching to the new API) the >> device/slave -> filter mapping needs to be

Re: [PATCH v6] serial: rewrite pxa2xx-uart to use 8250_core

Sergei Ianovich writes: > On Sat, 2016-02-06 at 22:22 -0800, Greg Kroah-Hartman wrote: >> On Thu, Dec 24, 2015 at 06:15:14PM +0300, Sergei Ianovich wrote: >> > pxa2xx-uart was a separate uart platform driver. It was declaring >> > the same device names and numbers as 8250

Re: [PATCH v6] serial: rewrite pxa2xx-uart to use 8250_core

Sergei Ianovich writes: > On Sat, 2016-02-06 at 22:22 -0800, Greg Kroah-Hartman wrote: >> On Thu, Dec 24, 2015 at 06:15:14PM +0300, Sergei Ianovich wrote: >> > pxa2xx-uart was a separate uart platform driver. It was declaring >> > the same device names and numbers as 8250 driver. As a result, >>

linux-next: Tree for Feb 22

Hi all, Changes since 20160219: The net-next tree lost its build failure. The wireless-drivers-next tree lost its build failure. The crypto tree gained conflicts against Linus' tree. The drm tree gained conflicts against Linus' tree and a build failure for which I applied a merge fix patch.

linux-next: Tree for Feb 22

Hi all, Changes since 20160219: The net-next tree lost its build failure. The wireless-drivers-next tree lost its build failure. The crypto tree gained conflicts against Linus' tree. The drm tree gained conflicts against Linus' tree and a build failure for which I applied a merge fix patch.

Re: [PATCH] rtlwifi: pass struct rtl_stats by reference as it is more efficient

On Saturday 20 February 2016 22:10:27, Colin King wrote: > From: Colin Ian King > > passing rtl_stats by value is inefficient; the structure is over 300 > bytes in size and generally just one field (packet_report_type) > is being accessed, so the pass by value is a

Re: [PATCH] rtlwifi: pass struct rtl_stats by reference as it is more efficient

On Saturday 20 February 2016 22:10:27, Colin King wrote: > From: Colin Ian King > > passing rtl_stats by value is inefficient; the structure is over 300 > bytes in size and generally just one field (packet_report_type) > is being accessed, so the pass by value is a relatively large overhead. >

Re: [PATCH v2 3/5] perf tools: Update srcline/file if needed

On Mon, Feb 22, 2016 at 09:31:51AM +0900, Namhyung Kim wrote: > Normally the hist entry's srcline and/or srcfile is set during sorting. > However sometime it's possible to a hist entry's srcline is not set yet > after the sorting. This is because the entry is so unique and other > sort keys

Re: [PATCH v2 3/5] perf tools: Update srcline/file if needed

On Mon, Feb 22, 2016 at 09:31:51AM +0900, Namhyung Kim wrote: > Normally the hist entry's srcline and/or srcfile is set during sorting. > However sometime it's possible to a hist entry's srcline is not set yet > after the sorting. This is because the entry is so unique and other > sort keys

Re: mmc: Add CONFIG_MMC_BLOCK_MAX_SPEED

Hi! On Thu 2016-02-04 12:29:07, Mark Salyzyn wrote: > When CONFIG_MMC_BLOCK_MAX_SPEED is enabled, Expose max_read_speed, > max_write_speed and cache_size controls to simulate a slow eMMC device. > The boot default values for each respectively are > CONFIG_MMC_BLOCK_MAX_READ_SPEED,

Re: mmc: Add CONFIG_MMC_BLOCK_MAX_SPEED

Hi! On Thu 2016-02-04 12:29:07, Mark Salyzyn wrote: > When CONFIG_MMC_BLOCK_MAX_SPEED is enabled, Expose max_read_speed, > max_write_speed and cache_size controls to simulate a slow eMMC device. > The boot default values for each respectively are > CONFIG_MMC_BLOCK_MAX_READ_SPEED,

Re: [PATCH v3 3/3] pci: dra7xx: use pdata callbacks to perform reset

Kishon, On Mon, 22 Feb 2016, Kishon Vijay Abraham I wrote: > Sekhar, > > On Thursday 18 February 2016 07:51 PM, Sekhar Nori wrote: > > On Friday 12 February 2016 10:50 PM, Suman Anna wrote: > >> Sekhar, > >> Will you be following up with above suggestion since Kishon is gonna be > >> out? > >

Re: [PATCH v3 3/3] pci: dra7xx: use pdata callbacks to perform reset

Kishon, On Mon, 22 Feb 2016, Kishon Vijay Abraham I wrote: > Sekhar, > > On Thursday 18 February 2016 07:51 PM, Sekhar Nori wrote: > > On Friday 12 February 2016 10:50 PM, Suman Anna wrote: > >> Sekhar, > >> Will you be following up with above suggestion since Kishon is gonna be > >> out? > >

Re: [PATCH v3 3/3] pci: dra7xx: use pdata callbacks to perform reset

Sekhar, On Thursday 18 February 2016 07:51 PM, Sekhar Nori wrote: > On Friday 12 February 2016 10:50 PM, Suman Anna wrote: >> Sekhar, >> Will you be following up with above suggestion since Kishon is gonna be out? > > Alright, noticed this action for me :) Went through the thread, and > looks

Re: [PATCH v3 3/3] pci: dra7xx: use pdata callbacks to perform reset

Sekhar, On Thursday 18 February 2016 07:51 PM, Sekhar Nori wrote: > On Friday 12 February 2016 10:50 PM, Suman Anna wrote: >> Sekhar, >> Will you be following up with above suggestion since Kishon is gonna be out? > > Alright, noticed this action for me :) Went through the thread, and > looks

Re: [PATCH] usb: chipidea: Configure DMA properties and ops from DT

On Sun 21 Feb 22:02 PST 2016, Peter Chen wrote: > On Sun, Feb 21, 2016 at 09:32:13PM -0800, Bjorn Andersson wrote: > > On certain platforms (e.g. ARM64) the dma_ops needs to be explicitly set > > to be able to do DMA allocations, so use the of_dma_configure() helper > > to populate the dma

Re: [PATCH] usb: chipidea: Configure DMA properties and ops from DT

On Sun 21 Feb 22:02 PST 2016, Peter Chen wrote: > On Sun, Feb 21, 2016 at 09:32:13PM -0800, Bjorn Andersson wrote: > > On certain platforms (e.g. ARM64) the dma_ops needs to be explicitly set > > to be able to do DMA allocations, so use the of_dma_configure() helper > > to populate the dma

Re: [linux-sunxi] Re: [PATCH v7 0/2] ASoC: Add SPDIF support for Allwinner SoCs

On 22 February 2016 at 04:12, Mark Brown wrote: > On Sun, Feb 21, 2016 at 12:13:36PM +0100, codekip...@gmail.com wrote: >> From: Marcus Cooper >> >> For now just the SPDIF transmitter has been tested on a Mele A2000(A10) >> and a Itead Ibox(A20). > >

Re: [linux-sunxi] Re: [PATCH v7 0/2] ASoC: Add SPDIF support for Allwinner SoCs

On 22 February 2016 at 04:12, Mark Brown wrote: > On Sun, Feb 21, 2016 at 12:13:36PM +0100, codekip...@gmail.com wrote: >> From: Marcus Cooper >> >> For now just the SPDIF transmitter has been tested on a Mele A2000(A10) >> and a Itead Ibox(A20). > > This was already applied. If any updates are

Re: [Xen-devel] [PATCH 8/9] x86/rtc: replace paravirt_enabled() check with subarch check

On Fri, Feb 19, 2016 at 03:48:41PM +0100, Luis R. Rodriguez wrote: > On Fri, Feb 19, 2016 at 02:22:12PM +0100, Juergen Gross wrote: > > On 19/02/16 14:08, Luis R. Rodriguez wrote: > > > The current check is a super long winded way of asking if this > > > is on lguest. The flags is used for legacy

Re: [Xen-devel] [PATCH 8/9] x86/rtc: replace paravirt_enabled() check with subarch check

On Fri, Feb 19, 2016 at 03:48:41PM +0100, Luis R. Rodriguez wrote: > On Fri, Feb 19, 2016 at 02:22:12PM +0100, Juergen Gross wrote: > > On 19/02/16 14:08, Luis R. Rodriguez wrote: > > > The current check is a super long winded way of asking if this > > > is on lguest. The flags is used for legacy

Re: [PATCH] usb: chipidea: Configure DMA properties and ops from DT

On Sun, Feb 21, 2016 at 09:32:13PM -0800, Bjorn Andersson wrote: > On certain platforms (e.g. ARM64) the dma_ops needs to be explicitly set > to be able to do DMA allocations, so use the of_dma_configure() helper > to populate the dma properties and assign an appropriate dma_ops. > >

Re: [PATCH] usb: chipidea: Configure DMA properties and ops from DT

On Sun, Feb 21, 2016 at 09:32:13PM -0800, Bjorn Andersson wrote: > On certain platforms (e.g. ARM64) the dma_ops needs to be explicitly set > to be able to do DMA allocations, so use the of_dma_configure() helper > to populate the dma properties and assign an appropriate dma_ops. > >

[PATCH v2 2/4] dmaengine: xilinx_vdma: Simplify spin lock handling

This patch simplifies the spin lock handling in the driver. Signed-off-by: Kedareswara rao Appana --- Changes for v2: ---> splitted the changes into multiple patches. drivers/dma/xilinx/xilinx_vdma.c | 27 ++- 1 file changed, 10 insertions(+), 17

[PATCH v2 2/4] dmaengine: xilinx_vdma: Simplify spin lock handling

This patch simplifies the spin lock handling in the driver. Signed-off-by: Kedareswara rao Appana --- Changes for v2: ---> splitted the changes into multiple patches. drivers/dma/xilinx/xilinx_vdma.c | 27 ++- 1 file changed, 10 insertions(+), 17 deletions(-) diff

[PATCH v2 4/4] dmaengine: xilinx_vdma: Improve channel idle checking

This patch improves the channel idle cheking by introduing a new varibale in chan private structure. Signed-off-by: Kedareswara rao Appana --- Changes for v2: ---> splitted the changes into multiple patches. drivers/dma/xilinx/xilinx_vdma.c | 41

[PATCH v2 4/4] dmaengine: xilinx_vdma: Improve channel idle checking

This patch improves the channel idle cheking by introduing a new varibale in chan private structure. Signed-off-by: Kedareswara rao Appana --- Changes for v2: ---> splitted the changes into multiple patches. drivers/dma/xilinx/xilinx_vdma.c | 41 1 file

[PATCH v2 1/4] dmaengine: xilinx_vdma: Improve SG engine handling

The current driver allows user to queue up multiple segments on to a single transaction descriptor. User will submit this single desc and in the issue_pending() we decode multiple segments and submit to SG HW engine. We free up the allocated_desc when it is submitted to the HW. Existing code

[PATCH v2 1/4] dmaengine: xilinx_vdma: Improve SG engine handling

The current driver allows user to queue up multiple segments on to a single transaction descriptor. User will submit this single desc and in the issue_pending() we decode multiple segments and submit to SG HW engine. We free up the allocated_desc when it is submitted to the HW. Existing code

[PATCH v2 3/4] dmaengine: xilinx_vdma: Fix issues with non-parking mode

This patch fixes issues with the Non-parking mode(Cirular mode). With the existing driver in cirular mode if we submit frames less than h/w configured we simply end-up having misconfigured vdma h/w. This patch fixes this issue by configuring the frame count register. Signed-off-by: Kedareswara

[PATCH v2 3/4] dmaengine: xilinx_vdma: Fix issues with non-parking mode

This patch fixes issues with the Non-parking mode(Cirular mode). With the existing driver in cirular mode if we submit frames less than h/w configured we simply end-up having misconfigured vdma h/w. This patch fixes this issue by configuring the frame count register. Signed-off-by: Kedareswara

Re: [PATCH v2 2/8] arm64: dts: qcom: apq8016-sbc: add usb support

On Wed 10 Feb 03:36 PST 2016, Srinivas Kandagatla wrote: > Signed-off-by: Srinivas Kandagatla > --- > arch/arm64/boot/dts/qcom/apq8016-sbc-soc-pins.dtsi | 15 ++ > arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi | 35 > ++ > 2

Re: [PATCH v2 2/8] arm64: dts: qcom: apq8016-sbc: add usb support

On Wed 10 Feb 03:36 PST 2016, Srinivas Kandagatla wrote: > Signed-off-by: Srinivas Kandagatla > --- > arch/arm64/boot/dts/qcom/apq8016-sbc-soc-pins.dtsi | 15 ++ > arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi | 35 > ++ > 2 files changed, 50 insertions(+) > >

Processes attached to shared memory

Given a struct shmid_kernel, is it possible to find each process/task_struct which is attached to the shared memory? I have been trying to use find_get_pages(shmid->shm_file->f_mapping, ...) along with rmap_walk(...). But what I have come up with seems a little convoluted and also triggers "BUG:

Processes attached to shared memory

Given a struct shmid_kernel, is it possible to find each process/task_struct which is attached to the shared memory? I have been trying to use find_get_pages(shmid->shm_file->f_mapping, ...) along with rmap_walk(...). But what I have come up with seems a little convoluted and also triggers "BUG:

Re: [PATCH v3 1/5] ACPI: change __init to __ref for early_acpi_os_unmap_memory()

On 02/19/2016 09:20 AM, Christopher Covington wrote: > > > On February 19, 2016 10:25:50 AM EST, Peter Hurley > wrote: >> On 02/19/2016 02:42 AM, Aleksey Makarov wrote: >>> Hi Peter, >>> >>> Thank you for review. >>> >>> On 02/19/2016 01:03 AM, Peter Hurley wrote:

Re: [PATCH v3 1/5] ACPI: change __init to __ref for early_acpi_os_unmap_memory()

On 02/19/2016 09:20 AM, Christopher Covington wrote: > > > On February 19, 2016 10:25:50 AM EST, Peter Hurley > wrote: >> On 02/19/2016 02:42 AM, Aleksey Makarov wrote: >>> Hi Peter, >>> >>> Thank you for review. >>> >>> On 02/19/2016 01:03 AM, Peter Hurley wrote: On 02/17/2016 07:36 PM,

Re: [patch] sched,rt: __always_inline preemptible_lazy()

> > sched,rt: __always_inline preemptible_lazy() > > Functions called within a notrace function must either also be > notrace or be inlined, lest recursion blow the stack. > > homer: # nm kernel/sched/core.o|grep preemptible_lazy > 00b5 t preemptible_lazy > > echo wakeup_rt >

Re: [patch] sched,rt: __always_inline preemptible_lazy()

> > sched,rt: __always_inline preemptible_lazy() > > Functions called within a notrace function must either also be > notrace or be inlined, lest recursion blow the stack. > > homer: # nm kernel/sched/core.o|grep preemptible_lazy > 00b5 t preemptible_lazy > > echo wakeup_rt >

Re: [PATCH] cpufreq: simplify for_each_suitable_policy() macro

On 21-02-16, 12:53, Eric Biggers wrote: > Signed-off-by: Eric Biggers > --- > drivers/cpufreq/cpufreq.c | 44 +++- > 1 file changed, 3 insertions(+), 41 deletions(-) > > diff --git a/drivers/cpufreq/cpufreq.c

Re: [PATCH] cpufreq: simplify for_each_suitable_policy() macro

On 21-02-16, 12:53, Eric Biggers wrote: > Signed-off-by: Eric Biggers > --- > drivers/cpufreq/cpufreq.c | 44 +++- > 1 file changed, 3 insertions(+), 41 deletions(-) > > diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c > index

[PATCH] usb: chipidea: Configure DMA properties and ops from DT

On certain platforms (e.g. ARM64) the dma_ops needs to be explicitly set to be able to do DMA allocations, so use the of_dma_configure() helper to populate the dma properties and assign an appropriate dma_ops. Signed-off-by: Bjorn Andersson ---

[PATCH] usb: chipidea: Configure DMA properties and ops from DT

On certain platforms (e.g. ARM64) the dma_ops needs to be explicitly set to be able to do DMA allocations, so use the of_dma_configure() helper to populate the dma properties and assign an appropriate dma_ops. Signed-off-by: Bjorn Andersson --- drivers/usb/chipidea/core.c | 4 1 file

RE: [PATCH] nati_x86_64_defconfig: Enable some net QoS modules

This is an internal patch, it's just destined for internal folks, please ignore it if you have no interest in it. Sorry for the spam. Best Regards! Sheng Wang NI Shanghai, Bld43 sheng.w...@ni.com -Original Message- From: Gangfeng Huang [mailto:gangfeng.hu...@ni.com] Sent: Monday,

RE: [PATCH] nati_x86_64_defconfig: Enable some net QoS modules

This is an internal patch, it's just destined for internal folks, please ignore it if you have no interest in it. Sorry for the spam. Best Regards! Sheng Wang NI Shanghai, Bld43 sheng.w...@ni.com -Original Message- From: Gangfeng Huang [mailto:gangfeng.hu...@ni.com] Sent: Monday,

Re: [PATCH] cpufreq: fix comment about return value of cpufreq_register_driver()

On 20-02-16, 21:50, Eric Biggers wrote: > The comment has been incorrect since commit 4dea5806d332 > ("cpufreq: return EEXIST instead of EBUSY for second registering"). > > Signed-off-by: Eric Biggers > --- > drivers/cpufreq/cpufreq.c | 2 +- > 1 file changed, 1

Re: [PATCH] cpufreq: fix comment about return value of cpufreq_register_driver()

On 20-02-16, 21:50, Eric Biggers wrote: > The comment has been incorrect since commit 4dea5806d332 > ("cpufreq: return EEXIST instead of EBUSY for second registering"). > > Signed-off-by: Eric Biggers > --- > drivers/cpufreq/cpufreq.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >

Re: [PATCH 2/2] cpufreq: governor: Make gov_set_update_util() static

On 21-02-16, 03:15, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The gov_set_update_util() routine is only used internally by the > common governor code and it doesn't need to be exported, so make > it static. > > No functional changes. > > Signed-off-by:

Re: [PATCH 2/2] cpufreq: governor: Make gov_set_update_util() static

On 21-02-16, 03:15, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The gov_set_update_util() routine is only used internally by the > common governor code and it doesn't need to be exported, so make > it static. > > No functional changes. > > Signed-off-by: Rafael J. Wysocki > --- >

Re: [PATCH 1/2] cpufreq: governor: Fix race in dbs_update_util_handler()

On 21-02-16, 03:14, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > There is a scenarion that may lead to undesired results in scenario > dbs_update_util_handler(). Namely, if two CPUs sharing a policy > enter the funtion at the same time, pass

Re: [PATCH 1/2] cpufreq: governor: Fix race in dbs_update_util_handler()

On 21-02-16, 03:14, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > There is a scenarion that may lead to undesired results in scenario > dbs_update_util_handler(). Namely, if two CPUs sharing a policy > enter the funtion at the same time, pass the sample delay check > and

  1   2   3   4   5   6   7   >