Re: [PATCH v2 1/2] mfd: arizona: Update reset pin to use GPIOD

Hi Charles, Thank you for the patch! Yet something to improve: [auto build test ERROR on ljones-mfd/for-mfd-next] [also build test ERROR on v4.16-rc2 next-20180220] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [PATCH v2 1/2] mfd: arizona: Update reset pin to use GPIOD

Hi Charles, Thank you for the patch! Yet something to improve: [auto build test ERROR on ljones-mfd/for-mfd-next] [also build test ERROR on v4.16-rc2 next-20180220] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [PATCH 6/6] sched/isolation: Update nohz documentation to explain tick offload

On Sat, Feb 17, 2018 at 11:53:22AM +0100, Thomas Gleixner wrote: > On Thu, 15 Feb 2018, Frederic Weisbecker wrote: > > > Update the documentation to reflect the 1Hz tick offload changes. > > > > Signed-off-by: Frederic Weisbecker > > Cc: Chris Metcalf

Re: [PATCH 6/6] sched/isolation: Update nohz documentation to explain tick offload

On Sat, Feb 17, 2018 at 11:53:22AM +0100, Thomas Gleixner wrote: > On Thu, 15 Feb 2018, Frederic Weisbecker wrote: > > > Update the documentation to reflect the 1Hz tick offload changes. > > > > Signed-off-by: Frederic Weisbecker > > Cc: Chris Metcalf > > Cc: Christoph Lameter > > Cc: Luiz

Re: [PATCH v4] reset: add support for non-DT systems

On 02/20/2018 04:39 AM, Philipp Zabel wrote: Hi Bartosz, David, On Mon, 2018-02-19 at 18:21 -0600, David Lechner wrote: On 02/19/2018 10:58 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski The reset framework only supports device-tree. There are some

Re: [PATCH v4] reset: add support for non-DT systems

On 02/20/2018 04:39 AM, Philipp Zabel wrote: Hi Bartosz, David, On Mon, 2018-02-19 at 18:21 -0600, David Lechner wrote: On 02/19/2018 10:58 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski The reset framework only supports device-tree. There are some platforms however, which need to

[PATCH v3 12/15] memory: tegra: Add Tegra124 memory controller hot resets

Define the table of memory controller hot resets for Tegra124. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/tegra124.c | 42 + 1 file changed, 42 insertions(+) diff --git a/drivers/memory/tegra/tegra124.c

[PATCH v3 12/15] memory: tegra: Add Tegra124 memory controller hot resets

Define the table of memory controller hot resets for Tegra124. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/tegra124.c | 42 + 1 file changed, 42 insertions(+) diff --git a/drivers/memory/tegra/tegra124.c b/drivers/memory/tegra/tegra124.c

[PATCH-next] staging: rtl8188eu: Remove unneeded cast

Fix Coccinelle alert: drivers/staging//rtl8188eu/os_dep/usb_intf.c:336:13-27: WARNING: casting value returned by memory allocation function to (struct adapter *) is useless. This issue was detected by using the Coccinelle software. Signed-off-by: Christopher Diaz Riveros

[PATCH-next] staging: rtl8188eu: Remove unneeded cast

Fix Coccinelle alert: drivers/staging//rtl8188eu/os_dep/usb_intf.c:336:13-27: WARNING: casting value returned by memory allocation function to (struct adapter *) is useless. This issue was detected by using the Coccinelle software. Signed-off-by: Christopher Diaz Riveros ---

[PATCH v3 13/15] memory: tegra: Add Tegra114 memory controller hot resets

Define the table of memory controller hot resets for Tegra114. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/tegra114.c | 33 + 1 file changed, 33 insertions(+) diff --git a/drivers/memory/tegra/tegra114.c

[PATCH v3 13/15] memory: tegra: Add Tegra114 memory controller hot resets

Define the table of memory controller hot resets for Tegra114. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/tegra114.c | 33 + 1 file changed, 33 insertions(+) diff --git a/drivers/memory/tegra/tegra114.c b/drivers/memory/tegra/tegra114.c index

[PATCH v3 10/15] memory: tegra: Introduce memory client hot reset

In order to reset busy HW properly, memory controller needs to be involved, otherwise it is possible to get corrupted memory or hang machine if HW was reset during DMA. Introduce memory client 'hot reset' that will be used for resetting of busy HW. Signed-off-by: Dmitry Osipenko

[PATCH v3 10/15] memory: tegra: Introduce memory client hot reset

In order to reset busy HW properly, memory controller needs to be involved, otherwise it is possible to get corrupted memory or hang machine if HW was reset during DMA. Introduce memory client 'hot reset' that will be used for resetting of busy HW. Signed-off-by: Dmitry Osipenko ---

[PATCH v3 15/15] memory: tegra: Add Tegra20 memory controller hot resets

Define the table of memory controller hot resets for Tegra20 and add specific to Tegra20 hot reset operations. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/tegra20.c | 118 + 1 file changed, 118 insertions(+) diff --git

[PATCH v3 15/15] memory: tegra: Add Tegra20 memory controller hot resets

Define the table of memory controller hot resets for Tegra20 and add specific to Tegra20 hot reset operations. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/tegra20.c | 118 + 1 file changed, 118 insertions(+) diff --git

[PATCH v3 14/15] memory: tegra: Add Tegra30 memory controller hot resets

Define the table of memory controller hot resets for Tegra30. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/tegra30.c | 33 + 1 file changed, 33 insertions(+) diff --git a/drivers/memory/tegra/tegra30.c

[PATCH v3 14/15] memory: tegra: Add Tegra30 memory controller hot resets

Define the table of memory controller hot resets for Tegra30. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/tegra30.c | 33 + 1 file changed, 33 insertions(+) diff --git a/drivers/memory/tegra/tegra30.c b/drivers/memory/tegra/tegra30.c index

[PATCH v3 1/2] mfd: arizona: Update reset pin to use GPIOD

Now GPIOD has support for both pdata systems and for non-standard DT bindings the Arizona reset GPIO can be converted to use it. Signed-off-by: Charles Keepax --- Changes since v2: - Kept null check in arizona_enable_reset, although gpiod_set_value_cansleep

[PATCH v3 1/2] mfd: arizona: Update reset pin to use GPIOD

Now GPIOD has support for both pdata systems and for non-standard DT bindings the Arizona reset GPIO can be converted to use it. Signed-off-by: Charles Keepax --- Changes since v2: - Kept null check in arizona_enable_reset, although gpiod_set_value_cansleep does its own null check it will

Re: [PATCH 05/17] trace doc: convert trace/ftrace.txt to rst format

On Tue, 20 Feb 2018 10:26:44 -0500 Steven Rostedt wrote: > One it should be a separate patch. Two, how does SPDX deal with dual > licenses? Separate them with "OR" on a single line. See Documentation/process/license-rules.rst for details. jon

Re: [PATCH 05/17] trace doc: convert trace/ftrace.txt to rst format

On Tue, 20 Feb 2018 10:26:44 -0500 Steven Rostedt wrote: > One it should be a separate patch. Two, how does SPDX deal with dual > licenses? Separate them with "OR" on a single line. See Documentation/process/license-rules.rst for details. jon

[PATCH v3 11/15] memory: tegra: Add Tegra210 memory controller hot resets

From: Thierry Reding Define the table of memory controller hot resets for Tegra210. Signed-off-by: Thierry Reding --- drivers/memory/tegra/tegra210.c | 45 + 1 file changed, 45 insertions(+) diff --git

[PATCH v3 11/15] memory: tegra: Add Tegra210 memory controller hot resets

From: Thierry Reding Define the table of memory controller hot resets for Tegra210. Signed-off-by: Thierry Reding --- drivers/memory/tegra/tegra210.c | 45 + 1 file changed, 45 insertions(+) diff --git a/drivers/memory/tegra/tegra210.c

[PATCH-next] staging: emxx_udc: Remove unneeded cast

Fix Coccinelle alert: drivers/staging//emxx_udc/emxx_udc.c:2689:19-21: WARNING: casting value returned by memory allocation function to (u8 *) is useless. This issue was detected by using the Coccinelle software. Signed-off-by: Christopher Diaz Riveros ---

[PATCH-next] staging: emxx_udc: Remove unneeded cast

Fix Coccinelle alert: drivers/staging//emxx_udc/emxx_udc.c:2689:19-21: WARNING: casting value returned by memory allocation function to (u8 *) is useless. This issue was detected by using the Coccinelle software. Signed-off-by: Christopher Diaz Riveros --- drivers/staging/emxx_udc/emxx_udc.c

[PATCH v3 2/2] mfd: arizona: Update DT doc to support more standard reset binding

Signed-off-by: Charles Keepax Reviewed-by: Rob Herring --- No changes since v2. Thanks, Charles Documentation/devicetree/bindings/mfd/arizona.txt | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

[PATCH v3 2/2] mfd: arizona: Update DT doc to support more standard reset binding

Signed-off-by: Charles Keepax Reviewed-by: Rob Herring --- No changes since v2. Thanks, Charles Documentation/devicetree/bindings/mfd/arizona.txt | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt

Re: [RFCv4 16/21] v4l2: video_device: support for creating requests

On 02/20/2018 05:44 AM, Alexandre Courbot wrote: > Add a new VIDIOC_NEW_REQUEST ioctl, which allows to instanciate requests > on devices that support the request API. Requests created that way can > only control the device they originate from, making them suitable for > simple devices, but not

Re: [RFCv4 16/21] v4l2: video_device: support for creating requests

On 02/20/2018 05:44 AM, Alexandre Courbot wrote: > Add a new VIDIOC_NEW_REQUEST ioctl, which allows to instanciate requests > on devices that support the request API. Requests created that way can > only control the device they originate from, making them suitable for > simple devices, but not

Re: [PATCH v2] usb: host: ehci-platform: add support for optional external vbus supply

On 20/02/18 16:46, Amelie DELAUNAY wrote: > Hi, > > On 02/20/2018 03:00 PM, Roger Quadros wrote: >> Hi, >> >> On 20/02/18 14:58, Amelie Delaunay wrote: >>> On some boards, especially when vbus supply requires large current, >>> and the charge pump on the PHY isn't enough, an external vbus power

Re: [PATCH v2] usb: host: ehci-platform: add support for optional external vbus supply

On 20/02/18 16:46, Amelie DELAUNAY wrote: > Hi, > > On 02/20/2018 03:00 PM, Roger Quadros wrote: >> Hi, >> >> On 20/02/18 14:58, Amelie Delaunay wrote: >>> On some boards, especially when vbus supply requires large current, >>> and the charge pump on the PHY isn't enough, an external vbus power

Re: [PATCH 4/7] sched/fair: Avoid unnecessary balancing of asymmetric capacity groups

On Mon, Feb 19, 2018 at 04:10:11PM +0100, Peter Zijlstra wrote: > On Thu, Feb 15, 2018 at 04:20:51PM +, Morten Rasmussen wrote: > > +/* > > + * group_similar_cpu_capacity: Returns true if the minimum capacity of the > > + * compared groups differ by less than 12.5%. > > + */ > > +static inline

[PATCH-next] staging: rtl8723bs: Remove unneeded cast

Fix Coccinelle alert: drivers/staging//rtl8723bs/os_dep/sdio_intf.c:340:13-27: WARNING: casting value returned by memory allocation function to (struct adapter *) is useless. This issue was detected by using the Coccinelle software. Signed-off-by: Christopher Diaz Riveros

Re: [PATCH 4/7] sched/fair: Avoid unnecessary balancing of asymmetric capacity groups

On Mon, Feb 19, 2018 at 04:10:11PM +0100, Peter Zijlstra wrote: > On Thu, Feb 15, 2018 at 04:20:51PM +, Morten Rasmussen wrote: > > +/* > > + * group_similar_cpu_capacity: Returns true if the minimum capacity of the > > + * compared groups differ by less than 12.5%. > > + */ > > +static inline

[PATCH-next] staging: rtl8723bs: Remove unneeded cast

Fix Coccinelle alert: drivers/staging//rtl8723bs/os_dep/sdio_intf.c:340:13-27: WARNING: casting value returned by memory allocation function to (struct adapter *) is useless. This issue was detected by using the Coccinelle software. Signed-off-by: Christopher Diaz Riveros ---

Re: [PATCH v2] kbuild: Don't source kernel config

2018-02-21 1:16 GMT+09:00 Richard Weinberger : > Am Dienstag, 20. Februar 2018, 17:00:39 CET schrieb Masahiro Yamada: >> 2018-02-21 0:25 GMT+09:00 Richard Weinberger : >> > Am Dienstag, 20. Februar 2018, 16:18:11 CET schrieb Masahiro Yamada: >> >> 2018-02-19 18:22

Re: [PATCH v2] kbuild: Don't source kernel config

2018-02-21 1:16 GMT+09:00 Richard Weinberger : > Am Dienstag, 20. Februar 2018, 17:00:39 CET schrieb Masahiro Yamada: >> 2018-02-21 0:25 GMT+09:00 Richard Weinberger : >> > Am Dienstag, 20. Februar 2018, 16:18:11 CET schrieb Masahiro Yamada: >> >> 2018-02-19 18:22 GMT+09:00 Richard Weinberger : >>

Re: [PATCH] locking/ww_mutex: add ww_mutex_is_owned_by function v4

On Tue, Feb 20, 2018 at 03:49:46PM +0100, Christian König wrote: > amdgpu needs to verify if userspace sends us valid addresses and the simplest > way of doing this is to check if the buffer object is locked with the ticket > of the current submission. > > Clean up the access to the ww_mutex

[PATCH-next] staging: net: netlogic: Remove unneeded cast

Fix Coccinelle alert: drivers/staging//netlogic/xlr_net.c:996:12-30: WARNING: casting value returned by memory allocation function to (struct xlr_adapter *) is useless. This issue was detected by using the Coccinelle software. Signed-off-by: Christopher Diaz Riveros ---

Re: [PATCH] locking/ww_mutex: add ww_mutex_is_owned_by function v4

On Tue, Feb 20, 2018 at 03:49:46PM +0100, Christian König wrote: > amdgpu needs to verify if userspace sends us valid addresses and the simplest > way of doing this is to check if the buffer object is locked with the ticket > of the current submission. > > Clean up the access to the ww_mutex

[PATCH-next] staging: net: netlogic: Remove unneeded cast

Fix Coccinelle alert: drivers/staging//netlogic/xlr_net.c:996:12-30: WARNING: casting value returned by memory allocation function to (struct xlr_adapter *) is useless. This issue was detected by using the Coccinelle software. Signed-off-by: Christopher Diaz Riveros ---

[PATCH v3 01/15] dt-bindings: arm: tegra: Remove duplicated Tegra30+ MC binding

There are two bindings for the same Memory Controller. One of the bindings became obsolete long time ago and probably was left unnoticed, remove it for consistency. Signed-off-by: Dmitry Osipenko --- .../bindings/arm/tegra/nvidia,tegra30-mc.txt | 18

[PATCH v3 01/15] dt-bindings: arm: tegra: Remove duplicated Tegra30+ MC binding

There are two bindings for the same Memory Controller. One of the bindings became obsolete long time ago and probably was left unnoticed, remove it for consistency. Signed-off-by: Dmitry Osipenko --- .../bindings/arm/tegra/nvidia,tegra30-mc.txt | 18 -- 1 file changed,

[PATCH v3 04/15] dt-bindings: memory: tegra: Add hot resets definitions

Add definitions for the Tegra20+ memory controller hot resets. Signed-off-by: Dmitry Osipenko --- include/dt-bindings/memory/tegra114-mc.h | 19 +++ include/dt-bindings/memory/tegra124-mc.h | 25 + include/dt-bindings/memory/tegra20-mc.h

[PATCH v3 04/15] dt-bindings: memory: tegra: Add hot resets definitions

Add definitions for the Tegra20+ memory controller hot resets. Signed-off-by: Dmitry Osipenko --- include/dt-bindings/memory/tegra114-mc.h | 19 +++ include/dt-bindings/memory/tegra124-mc.h | 25 + include/dt-bindings/memory/tegra20-mc.h | 21

[PATCH v3 02/15] dt-bindings: memory: tegra: Document #reset-cells property of the Tegra30 MC

Memory Controller has a memory client "hot reset" functionality, which resets the DMA interface of a memory client. So MC is a reset controller in addition to IOMMU. Documentation the new property. Signed-off-by: Dmitry Osipenko ---

[PATCH v3 02/15] dt-bindings: memory: tegra: Document #reset-cells property of the Tegra30 MC

Memory Controller has a memory client "hot reset" functionality, which resets the DMA interface of a memory client. So MC is a reset controller in addition to IOMMU. Documentation the new property. Signed-off-by: Dmitry Osipenko ---

[PATCH v3 00/15] Memory controller hot reset

Tegra's memory controller has a "memory hot reset" functionality that blocks all memory transactions for the memory client, which is required for a proper HW resetting. HW could perform DMA while being reset and this could lead to a system hang or memory corruption, so here comes the memory hot

[PATCH v3 00/15] Memory controller hot reset

Tegra's memory controller has a "memory hot reset" functionality that blocks all memory transactions for the memory client, which is required for a proper HW resetting. HW could perform DMA while being reset and this could lead to a system hang or memory corruption, so here comes the memory hot

Re: arm64 physmap (was Re: [kernel-hardening] [PATCH 4/6] Protectable Memory)

On 14/02/18 21:29, Kees Cook wrote: > On Wed, Feb 14, 2018 at 11:06 AM, Laura Abbott wrote: [...] >> Kernel code should be fine, if it isn't that is a bug that should be >> fixed. Modules yes are not fully protected. The conclusion from past > > I think that's a pretty

Re: arm64 physmap (was Re: [kernel-hardening] [PATCH 4/6] Protectable Memory)

On 14/02/18 21:29, Kees Cook wrote: > On Wed, Feb 14, 2018 at 11:06 AM, Laura Abbott wrote: [...] >> Kernel code should be fine, if it isn't that is a bug that should be >> fixed. Modules yes are not fully protected. The conclusion from past > > I think that's a pretty serious problem: we

[PATCH v3 07/15] memory: tegra: Apply interrupts mask per SoC

Currently we are enabling handling of interrupts specific to Tegra124+ which happen to overlap with previous generations. Let's specify interrupts mask per SoC generation for consistency and in a preparation of squashing of Tegra20 driver into the common one that will enable handling of GART

[PATCH v3 07/15] memory: tegra: Apply interrupts mask per SoC

Currently we are enabling handling of interrupts specific to Tegra124+ which happen to overlap with previous generations. Let's specify interrupts mask per SoC generation for consistency and in a preparation of squashing of Tegra20 driver into the common one that will enable handling of GART

[PATCH v3 05/15] memory: tegra: Do not handle spurious interrupts

The ISR reads interrupts-enable mask, but doesn't utilize it. Apply the mask to the interrupt status and don't handle interrupts that MC driver haven't asked for. Kernel would disable spurious MC IRQ and report the error. This would happen only in a case of a very severe bug. Signed-off-by:

[PATCH v3 05/15] memory: tegra: Do not handle spurious interrupts

The ISR reads interrupts-enable mask, but doesn't utilize it. Apply the mask to the interrupt status and don't handle interrupts that MC driver haven't asked for. Kernel would disable spurious MC IRQ and report the error. This would happen only in a case of a very severe bug. Signed-off-by:

Re: [PATCH] blk: optimization for classic polling

On Tue, Feb 20, 2018 at 02:21:37PM +0100, Peter Zijlstra wrote: > Also, set_current_state(TASK_RUNNING) is dodgy (similarly in > __blk_mq_poll), why do you need that memory barrier? You're right. The subsequent revision that was committed removed the barrier. The commit is here:

Re: [PATCH] blk: optimization for classic polling

On Tue, Feb 20, 2018 at 02:21:37PM +0100, Peter Zijlstra wrote: > Also, set_current_state(TASK_RUNNING) is dodgy (similarly in > __blk_mq_poll), why do you need that memory barrier? You're right. The subsequent revision that was committed removed the barrier. The commit is here:

Re: [PATCH v4 1/2] ACPI / x86: boot: Not all platforms require acpi_reduced_hw_init()

On Tue, Feb 20, 2018 at 5:03 PM, Andy Shevchenko wrote: > Some platforms might take care of legacy devices on theirs own. Due to this, > export acpi_reduced_hw_init() and put it into struct x86_init_acpi. IMO this completely doesn't explain what really happens

Re: [PATCH v4 1/2] ACPI / x86: boot: Not all platforms require acpi_reduced_hw_init()

On Tue, Feb 20, 2018 at 5:03 PM, Andy Shevchenko wrote: > Some platforms might take care of legacy devices on theirs own. Due to this, > export acpi_reduced_hw_init() and put it into struct x86_init_acpi. IMO this completely doesn't explain what really happens here. You basically want to

Re: net: hang in unregister_netdevice: waiting for lo to become free

On Tue, Feb 20, 2018 at 09:14:41AM +0100, Dmitry Vyukov wrote: > On Tue, Feb 20, 2018 at 8:56 AM, Tommi Rantala > wrote: > > On 19.02.2018 20:59, Dmitry Vyukov wrote: > >> > >> On Sat, Feb 3, 2018 at 1:15 PM, Xin Long wrote: > > > > On

Re: net: hang in unregister_netdevice: waiting for lo to become free

On Tue, Feb 20, 2018 at 09:14:41AM +0100, Dmitry Vyukov wrote: > On Tue, Feb 20, 2018 at 8:56 AM, Tommi Rantala > wrote: > > On 19.02.2018 20:59, Dmitry Vyukov wrote: > >> > >> On Sat, Feb 3, 2018 at 1:15 PM, Xin Long wrote: > > > > On 1/30/18 1:57 PM, David Ahern wrote: > >> >

[PATCH v3 08/15] memory: tegra: Remove unused headers inclusions

Tegra210 contains some unused leftover headers, remove them for consistency. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/tegra210.c | 5 - 1 file changed, 5 deletions(-) diff --git a/drivers/memory/tegra/tegra210.c b/drivers/memory/tegra/tegra210.c index

[PATCH v3 08/15] memory: tegra: Remove unused headers inclusions

Tegra210 contains some unused leftover headers, remove them for consistency. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/tegra210.c | 5 - 1 file changed, 5 deletions(-) diff --git a/drivers/memory/tegra/tegra210.c b/drivers/memory/tegra/tegra210.c index

[PATCH 3/3] ARM: davinci: mark spi_board_info arrays as const

Building with LTO revealed that three spi_board_info arrays are marked __initconst, but not const: arch/arm/mach-davinci/board-dm365-evm.c: In function 'dm365_evm_init': arch/arm/mach-davinci/board-dm365-evm.c:729:30: error: 'dm365_evm_spi_info' causes a section type conflict with

[PATCH 3/3] ARM: davinci: mark spi_board_info arrays as const

Building with LTO revealed that three spi_board_info arrays are marked __initconst, but not const: arch/arm/mach-davinci/board-dm365-evm.c: In function 'dm365_evm_init': arch/arm/mach-davinci/board-dm365-evm.c:729:30: error: 'dm365_evm_spi_info' causes a section type conflict with

Re: [PATCH v2] kbuild: Don't source kernel config

On Tue, 20 Feb 2018, Richard Weinberger wrote: > An alternate approach would be this: > diff --git a/scripts/kconfig/confdata.c b/scripts/kconfig/confdata.c > index 5c12dc91ef34..ff0a7c62344b 100644 > --- a/scripts/kconfig/confdata.c > +++ b/scripts/kconfig/confdata.c > @@ -161,6 +161,13 @@

Re: [PATCH v2] kbuild: Don't source kernel config

On Tue, 20 Feb 2018, Richard Weinberger wrote: > An alternate approach would be this: > diff --git a/scripts/kconfig/confdata.c b/scripts/kconfig/confdata.c > index 5c12dc91ef34..ff0a7c62344b 100644 > --- a/scripts/kconfig/confdata.c > +++ b/scripts/kconfig/confdata.c > @@ -161,6 +161,13 @@

[PATCH v3 09/15] memory: tegra: Squash tegra20-mc into common tegra-mc driver

Tegra30+ has some minor differences in registers / bits layout compared to Tegra20. Let's squash Tegra20 driver into the common tegra-mc driver in a preparation for the upcoming MC hot reset controls implementation, avoiding code duplication. Signed-off-by: Dmitry Osipenko ---

[PATCH v3 09/15] memory: tegra: Squash tegra20-mc into common tegra-mc driver

Tegra30+ has some minor differences in registers / bits layout compared to Tegra20. Let's squash Tegra20 driver into the common tegra-mc driver in a preparation for the upcoming MC hot reset controls implementation, avoiding code duplication. Signed-off-by: Dmitry Osipenko ---

[PATCH v3 06/15] memory: tegra: Setup interrupts mask before requesting IRQ

This avoids unwanted interrupt during MC driver probe. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/mc.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/drivers/memory/tegra/mc.c b/drivers/memory/tegra/mc.c index

[PATCH 2/3] ARM: orion: mark orion_ge00_mvmdio_bus_name as const

A section type mismatch warning shows up when building with LTO, since orion_ge00_mvmdio_bus_name was put in __initconst but not marked const itself: include/linux/of.h: In function 'spear_setup_of_timer': arch/arm/mach-spear/time.c:207:34: error: 'timer_of_match' causes a section type conflict

[PATCH v3 06/15] memory: tegra: Setup interrupts mask before requesting IRQ

This avoids unwanted interrupt during MC driver probe. Signed-off-by: Dmitry Osipenko --- drivers/memory/tegra/mc.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/drivers/memory/tegra/mc.c b/drivers/memory/tegra/mc.c index d2005b995821..e55b9733bd83 100644

[PATCH 2/3] ARM: orion: mark orion_ge00_mvmdio_bus_name as const

A section type mismatch warning shows up when building with LTO, since orion_ge00_mvmdio_bus_name was put in __initconst but not marked const itself: include/linux/of.h: In function 'spear_setup_of_timer': arch/arm/mach-spear/time.c:207:34: error: 'timer_of_match' causes a section type conflict

[PATCH v3 03/15] dt-bindings: arm: tegra: Document #reset-cells property of the Tegra20 MC

Memory Controller has a memory client "hot reset" functionality, which resets the DMA interface of a memory client, so MC is a reset controller. Documentation the new property. Signed-off-by: Dmitry Osipenko --- .../devicetree/bindings/arm/tegra/nvidia,tegra20-mc.txt | 12

[PATCH v3 03/15] dt-bindings: arm: tegra: Document #reset-cells property of the Tegra20 MC

Memory Controller has a memory client "hot reset" functionality, which resets the DMA interface of a memory client, so MC is a reset controller. Documentation the new property. Signed-off-by: Dmitry Osipenko --- .../devicetree/bindings/arm/tegra/nvidia,tegra20-mc.txt | 12 +++- 1

[PATCH 1/3] ARM: clps711x: mark clps711x_compat as const

The array of string pointers is put in __initconst, and the strings themselves are marke 'const' but the the pointers are not, which caused a warning when built with LTO: arch/arm/mach-clps711x/board-dt.c:72:20: error: 'clps711x_compat' causes a section type conflict with 'feroceon_ids' static

[PATCH 1/3] ARM: clps711x: mark clps711x_compat as const

The array of string pointers is put in __initconst, and the strings themselves are marke 'const' but the the pointers are not, which caused a warning when built with LTO: arch/arm/mach-clps711x/board-dt.c:72:20: error: 'clps711x_compat' causes a section type conflict with 'feroceon_ids' static

Re: [PATCH 4/7] sched/fair: Avoid unnecessary balancing of asymmetric capacity groups

On Mon, Feb 19, 2018 at 03:53:35PM +0100, Peter Zijlstra wrote: > On Mon, Feb 19, 2018 at 03:50:12PM +0100, Peter Zijlstra wrote: > > On Thu, Feb 15, 2018 at 04:20:51PM +, Morten Rasmussen wrote: > > > On systems with asymmetric cpu capacities, a skewed load distribution > > > might yield

Re: [PATCH 4/7] sched/fair: Avoid unnecessary balancing of asymmetric capacity groups

On Mon, Feb 19, 2018 at 03:53:35PM +0100, Peter Zijlstra wrote: > On Mon, Feb 19, 2018 at 03:50:12PM +0100, Peter Zijlstra wrote: > > On Thu, Feb 15, 2018 at 04:20:51PM +, Morten Rasmussen wrote: > > > On systems with asymmetric cpu capacities, a skewed load distribution > > > might yield

[PATCH 5/6] powerpc: Implement DISCONTIGMEM and allow selection on PPC32

The implementation of pfn_to_nid and pfn_valid in mmzone.h is based on arch/metag's implementation. Signed-off-by: Jonathan Neuschäfer --- NOTE: Checking NODE_DATA(nid) in pfn_to_nid appears to be uncommon. Running up to MAX_NUMNODES instead of checking NODE_DATA(nid)

[PATCH 5/6] powerpc: Implement DISCONTIGMEM and allow selection on PPC32

The implementation of pfn_to_nid and pfn_valid in mmzone.h is based on arch/metag's implementation. Signed-off-by: Jonathan Neuschäfer --- NOTE: Checking NODE_DATA(nid) in pfn_to_nid appears to be uncommon. Running up to MAX_NUMNODES instead of checking NODE_DATA(nid) would require the

[PATCH 2/6] powerpc: numa: Fix overshift on PPC32

When read_n_cells is compiled for PPC32, "result << 32" causes an overshift, which GCC doesn't like. Fix this by using u64 instead of unsigned long. Signed-off-by: Jonathan Neuschäfer --- arch/powerpc/mm/numa.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

[PATCH 2/6] powerpc: numa: Fix overshift on PPC32

When read_n_cells is compiled for PPC32, "result << 32" causes an overshift, which GCC doesn't like. Fix this by using u64 instead of unsigned long. Signed-off-by: Jonathan Neuschäfer --- arch/powerpc/mm/numa.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [RFCv4 13/21] media: videobuf2-v4l2: support for requests

On 02/20/2018 05:44 AM, Alexandre Courbot wrote: > Add a new vb2_qbuf_request() (a request-aware version of vb2_qbuf()) > that request-aware drivers can call to queue a buffer into a request > instead of directly into the vb2 queue if relevent. > > This function expects that drivers invoking it

Re: [RFCv4 13/21] media: videobuf2-v4l2: support for requests

On 02/20/2018 05:44 AM, Alexandre Courbot wrote: > Add a new vb2_qbuf_request() (a request-aware version of vb2_qbuf()) > that request-aware drivers can call to queue a buffer into a request > instead of directly into the vb2 queue if relevent. > > This function expects that drivers invoking it

[PATCH 4/6] powerpc: numa: Restrict fake NUMA enulation to CONFIG_NUMA systems

Signed-off-by: Jonathan Neuschäfer --- arch/powerpc/mm/numa.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c index df03a65b658f..dfe279529463 100644 --- a/arch/powerpc/mm/numa.c +++

[PATCH 4/6] powerpc: numa: Restrict fake NUMA enulation to CONFIG_NUMA systems

Signed-off-by: Jonathan Neuschäfer --- arch/powerpc/mm/numa.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c index df03a65b658f..dfe279529463 100644 --- a/arch/powerpc/mm/numa.c +++ b/arch/powerpc/mm/numa.c @@ -738,7 +738,8

[PATCH 1/6] powerpc/mm/32: Use pfn_valid to check if pointer is in RAM

The Nintendo Wii has a memory layout that places two chunks of RAM at non-adjacent addresses, and MMIO between them. Currently, the allocation of these MMIO areas is made possible by declaring the MMIO hole as reserved memory and allowing reserved memory to be allocated (cf. wii_memory_fixups).

[PATCH 1/6] powerpc/mm/32: Use pfn_valid to check if pointer is in RAM

The Nintendo Wii has a memory layout that places two chunks of RAM at non-adjacent addresses, and MMIO between them. Currently, the allocation of these MMIO areas is made possible by declaring the MMIO hole as reserved memory and allowing reserved memory to be allocated (cf. wii_memory_fixups).

[PATCH 3/6] powerpc: numa: Use the right #ifdef guards around functions

of_node_to_nid and dump_numa_cpu_topology are declared inline in their respective header files, if CONFIG_NUMA is not set. Thus it is only valid to define these functions in numa.c if CONFIG_NUMA is set. (numa.c, despite the name, isn't conditionalized on CONFIG_NUMA, but

[PATCH 6/6] powerpc: wii: Don't rely on reserved memory hack if DISCONTIGMEM is set

Signed-off-by: Jonathan Neuschäfer --- arch/powerpc/platforms/embedded6xx/wii.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/arch/powerpc/platforms/embedded6xx/wii.c b/arch/powerpc/platforms/embedded6xx/wii.c index

[PATCH 3/6] powerpc: numa: Use the right #ifdef guards around functions

of_node_to_nid and dump_numa_cpu_topology are declared inline in their respective header files, if CONFIG_NUMA is not set. Thus it is only valid to define these functions in numa.c if CONFIG_NUMA is set. (numa.c, despite the name, isn't conditionalized on CONFIG_NUMA, but

[PATCH 6/6] powerpc: wii: Don't rely on reserved memory hack if DISCONTIGMEM is set

Signed-off-by: Jonathan Neuschäfer --- arch/powerpc/platforms/embedded6xx/wii.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/arch/powerpc/platforms/embedded6xx/wii.c b/arch/powerpc/platforms/embedded6xx/wii.c index 4682327f76a9..589ac87a3ce0 100644 ---

[PATCH 0/6] DISCONTIGMEM support for PPC32

This patchset adds support for DISCONTIGMEM on 32-bit PowerPC. This is required to properly support the Nintendo Wii's memory layout, in which there are two blocks of RAM and MMIO in the middle. Previously, this memory layout was handled by code that joins the two RAM blocks into one, reserves

[PATCH 0/6] DISCONTIGMEM support for PPC32

This patchset adds support for DISCONTIGMEM on 32-bit PowerPC. This is required to properly support the Nintendo Wii's memory layout, in which there are two blocks of RAM and MMIO in the middle. Previously, this memory layout was handled by code that joins the two RAM blocks into one, reserves

Re: [PATCH v19 00/10] Add backlight helper functions

On Wed, Jan 24, 2018 at 11:32 AM, Meghana Madhyastha wrote: > Move drm helper functions from tinydrm-helpers to linux/backlight for > ease of use by callers in other drivers. > It was a long time coming, but this has finally been applied to -misc-next. Thanks for

Re: [PATCH v19 00/10] Add backlight helper functions

On Wed, Jan 24, 2018 at 11:32 AM, Meghana Madhyastha wrote: > Move drm helper functions from tinydrm-helpers to linux/backlight for > ease of use by callers in other drivers. > It was a long time coming, but this has finally been applied to -misc-next. Thanks for sticking with it! Sean >

Re: [PATCH v2] kbuild: Don't source kernel config

Am Dienstag, 20. Februar 2018, 17:00:39 CET schrieb Masahiro Yamada: > 2018-02-21 0:25 GMT+09:00 Richard Weinberger : > > Am Dienstag, 20. Februar 2018, 16:18:11 CET schrieb Masahiro Yamada: > >> 2018-02-19 18:22 GMT+09:00 Richard Weinberger : > >> > Don't source

Re: [PATCH v2] kbuild: Don't source kernel config

Am Dienstag, 20. Februar 2018, 17:00:39 CET schrieb Masahiro Yamada: > 2018-02-21 0:25 GMT+09:00 Richard Weinberger : > > Am Dienstag, 20. Februar 2018, 16:18:11 CET schrieb Masahiro Yamada: > >> 2018-02-19 18:22 GMT+09:00 Richard Weinberger : > >> > Don't source the kernel config file in shell

<    4   5   6   7   8   9   10   11   12   13   >