[PATCH v8 05/28] x86/asm: annotate local pseudo-functions

Use the newly added SYM_CODE_START_LOCAL* to annotate starts of all pseudo-functions (those ending END until now) which do not have ".globl" annotation. This is needed to balance END for tools that generate debuginfo. Note that we switch from END to SYM_CODE_END too so that everybody can see the pa

[PATCH v8 08/28] x86/uaccess: annotate local function

copy_user_handle_tail is a self-standing local function, annotate it as such using SYM_FUNC_START_LOCAL. Signed-off-by: Jiri Slaby Cc: "H. Peter Anvin" Cc: Thomas Gleixner Cc: Borislav Petkov Cc: Ingo Molnar Cc: x...@kernel.org --- arch/x86/lib/copy_user_64.S | 5 ++--- 1 file changed, 2 ins

[PATCH v8 02/28] x86/asm/suspend: use SYM_DATA for data

Some global data in the suspend code were marked as `ENTRY'. ENTRY was intended for functions and shall be paired with ENDPROC. ENTRY also aligns symbols which creates unnecessary holes here between data. Since we are dropping historical markings, make proper use of newly added SYM_DATA in this cod

Re: [PATCH v4 0/3] DCMI bridge support

Hi Hans, On 8/8/19 11:41 AM, Hans Verkuil wrote: > Hi Hugues, > > On 8/8/19 11:38 AM, Hugues FRUCHET wrote: >> Hi Hans, >> >> You're welcome, here it is: >> >> 1) v4l-utils master branch, commit >> 6aa15f7447d4aeca6af1ed7ee9644a0c7e891ece "v4l2-ctl: fix double >> decrementing of stream_count" >>

[PATCH v8 01/28] linkage: new macros for assembler symbols

Introduce new C macros for annotations of functions and data in assembly. There is a long-standing mess in macros like ENTRY, END, ENDPROC and similar. They are used in different manners and sometimes incorrectly. So introduce macros with clear use to annotate assembly as follows: a) Support macr

[PATCH v8 07/28] x86/boot/compressed: annotate local functions

relocated, paging_enabled, and no_longmode are self-standing local functions, annotate them as such. paging_enabled is annotated as NOALIGN, since the trampoline code has to be compact. Signed-off-by: Jiri Slaby Cc: "H. Peter Anvin" Cc: Thomas Gleixner Cc: Ingo Molnar Cc: x...@kernel.org ---

[PATCH v8 03/28] x86/asm: annotate relocate_kernel

There are functions in relocate_kernel which are not annotated. This makes automatic annotations rather hard. So annotate all the functions now. Note that these are not C-like functions, so we do not use FUNC, but CODE markers. Also they are not aligned, so we use the NOALIGN versions: - SYM_CODE_

[PATCH v8 06/28] x86/asm/crypto: annotate local functions

Use the newly added SYM_FUNC_START_LOCAL to annotate starts of all functions which do not have ".globl" annotation, but their ends are annotated by ENDPROC. This is needed to balance ENDPROC for tools that generate debuginfo. To be symmetric, we also convert their ENDPROCs to the new SYM_FUNC_END.

[PATCH v8 00/28] New macros for assembler symbols

So this is an updated version (v8) of the series based on comments provided mostly by Boris and rebased on the top of current tree (quite a few conflicting changes in assembly happened lately). See respective patches for changes done in them since the last submission. Now the summary: This series

Re: [PATCH 2/3] sched/fair: Prevent active LB from preempting higher sched classes

On 08/08/2019 10:24, Qais Yousef wrote: >> @@ -8834,6 +8834,10 @@ static inline enum alb_status >> active_load_balance(struct lb_env *env) >> >> raw_spin_lock_irqsave(&busiest->lock, flags); >> >> +/* Make sure we're not about to stop a task from a higher sched class */ >> +if (bu

[tip:sched/core] sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices

Commit-ID: de53fd7aedb100f03e5d2231cfce0e4993282425 Gitweb: https://git.kernel.org/tip/de53fd7aedb100f03e5d2231cfce0e4993282425 Author: Dave Chiluk AuthorDate: Tue, 23 Jul 2019 11:44:26 -0500 Committer: Peter Zijlstra CommitDate: Thu, 8 Aug 2019 09:09:30 +0200 sched/fair: Fix low cpu u

[tip:sched/core] stop_machine: Fix stop_cpus_in_progress ordering

Commit-ID: 99d84bf8c65a7a0dbc9e166ca0a58ed949ac4f37 Gitweb: https://git.kernel.org/tip/99d84bf8c65a7a0dbc9e166ca0a58ed949ac4f37 Author: Peter Zijlstra AuthorDate: Wed, 29 May 2019 20:36:37 + Committer: Peter Zijlstra CommitDate: Thu, 8 Aug 2019 09:09:30 +0200 stop_machine: Fix stop

[tip:sched/core] sched: Fix kerneldoc comment for ia64_set_curr_task

Commit-ID: 5feeb7837a448f659e0aaa19fb446b1d9a4b323a Gitweb: https://git.kernel.org/tip/5feeb7837a448f659e0aaa19fb446b1d9a4b323a Author: Peter Zijlstra AuthorDate: Wed, 29 May 2019 20:36:38 + Committer: Peter Zijlstra CommitDate: Thu, 8 Aug 2019 09:09:30 +0200 sched: Fix kerneldoc c

Re: [PATCH v1] Bluetooth: hci_qca: wait for Pre shutdown to command complete event before sending the Power off pulse

Hi Harish, On 2019-08-08 14:55, Harish Bandi wrote: When SoC receives pre shut down command, it share the same with other COEX shared clients. So SoC needs a short time after sending VS pre shutdown command before turning off the regulators and sending the power off pulse. Signed-off-by: Harish

[tip:sched/core] sched/{rt,deadline}: Fix set_next_task vs pick_next_task

Commit-ID: f95d4eaee6d0207bff2dc93371133d31227d4cfb Gitweb: https://git.kernel.org/tip/f95d4eaee6d0207bff2dc93371133d31227d4cfb Author: Peter Zijlstra AuthorDate: Wed, 29 May 2019 20:36:40 + Committer: Peter Zijlstra CommitDate: Thu, 8 Aug 2019 09:09:30 +0200 sched/{rt,deadline}: F

[tip:sched/core] sched: Add task_struct pointer to sched_class::set_curr_task

Commit-ID: 03b7fad167efca3b7a39733933f9df56e79c Gitweb: https://git.kernel.org/tip/03b7fad167efca3b7a39733933f9df56e79c Author: Peter Zijlstra AuthorDate: Wed, 29 May 2019 20:36:41 + Committer: Peter Zijlstra CommitDate: Thu, 8 Aug 2019 09:09:31 +0200 sched: Add task_struct

[tip:sched/core] sched/fair: Expose newidle_balance()

Commit-ID: 5ba553eff0c3a7c099b1e29a740277a82c0c3314 Gitweb: https://git.kernel.org/tip/5ba553eff0c3a7c099b1e29a740277a82c0c3314 Author: Peter Zijlstra AuthorDate: Wed, 29 May 2019 20:36:42 + Committer: Peter Zijlstra CommitDate: Thu, 8 Aug 2019 09:09:31 +0200 sched/fair: Expose new

Re: [PATCH v3 8/8] PCI: dw: Add support for PCI_PROBE_ONLY/PCI_REASSIGN_ALL_BUS flags

Side note, run: git log --oneline on drivers/pci/controller/dwc existing files and make sure commit subjects are in line with those. Eg PCI: dw: should be PCI: dwc: On Thu, Aug 08, 2019 at 09:30:05AM +, Chocron, Jonathan wrote: > On Wed, 2019-08-07 at 17:36 +0100, Lorenzo Pieralisi wrote: >

[tip:sched/core] sched: Allow put_prev_task() to drop rq->lock

Commit-ID: 5f2a45fc9e89e022233085e6f0f352eb6ff770bb Gitweb: https://git.kernel.org/tip/5f2a45fc9e89e022233085e6f0f352eb6ff770bb Author: Peter Zijlstra AuthorDate: Wed, 29 May 2019 20:36:43 + Committer: Peter Zijlstra CommitDate: Thu, 8 Aug 2019 09:09:31 +0200 sched: Allow put_prev_

[tip:sched/core] sched: Rework pick_next_task() slow-path

Commit-ID: 67692435c411e5c53a1c588ecca2037aebd81f2e Gitweb: https://git.kernel.org/tip/67692435c411e5c53a1c588ecca2037aebd81f2e Author: Peter Zijlstra AuthorDate: Wed, 29 May 2019 20:36:44 + Committer: Peter Zijlstra CommitDate: Thu, 8 Aug 2019 09:09:31 +0200 sched: Rework pick_nex

[tip:sched/core] cpufreq: schedutil: fix equation in comment

Commit-ID: 5c3ceef9ad7b340b0acee6c26d0c9e6429decb2c Gitweb: https://git.kernel.org/tip/5c3ceef9ad7b340b0acee6c26d0c9e6429decb2c Author: Qais Yousef AuthorDate: Fri, 2 Aug 2019 11:46:28 +0100 Committer: Peter Zijlstra CommitDate: Thu, 8 Aug 2019 09:09:31 +0200 cpufreq: schedutil: fix eq

[tip:sched/core] sched/fair: Use rq_lock/unlock in online_fair_sched_group

Commit-ID: 6b8fd01b21f5f2701b407a7118f236ba4c41226d Gitweb: https://git.kernel.org/tip/6b8fd01b21f5f2701b407a7118f236ba4c41226d Author: Phil Auld AuthorDate: Thu, 1 Aug 2019 09:37:49 -0400 Committer: Peter Zijlstra CommitDate: Thu, 8 Aug 2019 09:09:31 +0200 sched/fair: Use rq_lock/unlo

Re: [PATCH 1/3] mm/mlock.c: convert put_page() to put_user_page*()

On 8/8/19 8:21 AM, Michal Hocko wrote: > On Wed 07-08-19 16:32:08, John Hubbard wrote: >> On 8/7/19 4:01 AM, Michal Hocko wrote: >>> On Mon 05-08-19 15:20:17, john.hubb...@gmail.com wrote: From: John Hubbard For pages that were retained via get_user_pages*(), release those pages >>>

Re: [PATCH 2/2] clk: samsung: exynos5800: Move MAU subsystem clocks to MAU sub-CMU

Tested-by: Jaafar Ali On Thu, 8 Aug 2019 at 12:24, Sylwester Nawrocki wrote: > > This patch fixes broken sound on Exynos5422/5800 platforms after > system/suspend resume cycle in cases where the audio root clock > is derived from MAU_EPLL_CLK. > > In order to preserve state of the USER_MUX_MAU_E

Re: [PATCH V38 19/29] Lock down module params that specify hardware parameters (eg. ioport)

+++ Matthew Garrett [07/08/19 17:07 -0700]: From: David Howells Provided an annotation for module parameters that specify hardware parameters (such as io ports, iomem addresses, irqs, dma channels, fixed dma buffers and other types). Suggested-by: Alan Cox Signed-off-by: David Howells Signed

Re: [PATCH 1/2] clk: samsung: Change signature of exynos5_subcmus_init() function

Tested-by: Jaafar Ali On Thu, 8 Aug 2019 at 12:24, Sylwester Nawrocki wrote: > > In order to make it easier in subsequent patch to create different subcmu > lists for exynos5420 and exynos5800 SoCs the code is rewritten so we pass > an array of pointers to the subcmus initialization function. >

Re: [PATCH 0/2] intel-hid: intel-vbtn: Suspend-related fix and update

On Thu, Aug 08, 2019 at 10:40:19AM +0200, Rafael J. Wysocki wrote: > Hi, > > These two patches fix a minor issue related to system suspend in the intel-hid > and intel-vbtn drivers and update the suspend/resume handling in intel-hid to > reduce special-casing in it somewhat. > AFAIR the original

Re: [PATCH v2 1/3] serial: lantiq: Use proper DT compatible string

On Thu, Aug 08, 2019 at 06:02:06PM +0800, Rahul Tanwar wrote: > Use explicit string instead of a macro for devicetree compatible string. > > This series of patches is to add support for multiple SoCs which reuse the > same > serial controller IP. The following patches will add another compatible

[PATCH v2] kbuild: show hint if subdir-y/m is used to visit module Makefile

Since commit ff9b45c55b26 ("kbuild: modpost: read modules.order instead of $(MODVERDIR)/*.mod"), a module is no longer built in the following pattern: [Makefile] subdir-y := some-module [some-module/Makefile] obj-m := some-module.o You cannot write Makefile this way in upstream because m

Re: [PATCH v2 2/3] serial: lantiq: Make IRQ & ISR assignment dynamic

On Thu, Aug 08, 2019 at 06:02:07PM +0800, Rahul Tanwar wrote: > This driver/IP is reused across multiple SoCs. Older SoCs supported three > separate IRQs for tx, rx & err interrupts. Newer Lightning Mountain SoC > supports single IRQ for all of tx/rx/err interrupts. This patch modifies > the driver

Re: [PATCH] net: ethernet: et131x: Use GFP_KERNEL instead of GFP_ATOMIC when allocating tx_ring->tcb_ring

On Wed, Aug 07, 2019 at 10:23:46PM -0700, Jesse Brandeburg wrote: > On Wed, 31 Jul 2019 09:38:42 +0200 > Christophe JAILLET wrote: > > > There is no good reason to use GFP_ATOMIC here. Other memory allocations > > are performed with GFP_KERNEL (see other 'dma_alloc_coherent()' below and > > 'kzal

Re: [PATCH v2 3/3] serial: lantiq: Add support for Lightning Mountain SoC

On Thu, Aug 08, 2019 at 06:02:08PM +0800, Rahul Tanwar wrote: > This patch adds IRQ & ISR support in the driver for Lightning Mountain SoC. > I dunno if DT binding should go first, otherwise, FWIW, Reviewed-by: Andy Shevchenko > Signed-off-by: Rahul Tanwar > --- > drivers/tty/serial/lantiq.c

Re: [PATCH 1/2] s390/extmem: Use refcount_t for refcount

On Thu, Aug 08, 2019 at 03:18:17PM +0800, Chuhong Yuan wrote: > Reference counters are preferred to use refcount_t instead of > atomic_t. > This is because the implementation of refcount_t can prevent > overflows and detect possible use-after-free. > So convert atomic_t ref counters to refcount_t.

Re: [PATCH 2/2] s390/mm: Use refcount_t for refcount

On Thu, Aug 08, 2019 at 03:18:26PM +0800, Chuhong Yuan wrote: > Reference counters are preferred to use refcount_t instead of > atomic_t. > This is because the implementation of refcount_t can prevent > overflows and detect possible use-after-free. > So convert atomic_t ref counters to refcount_t.

[PATCH v2 1/2] virtio_console: free unused buffers with port delete

The commit a7a69ec0d8e4 ("virtio_console: free buffers after reset") deferred detaching of unused buffer to virtio device unplug time. This causes unplug/replug of single port in virtio device with an error "Error allocating inbufs\n". As we don't free the unused buffers attached with th

[PATCH v2 2/2] virtio_ring: packed ring: fix virtqueue_detach_unused_buf

This patch makes packed ring code compatible with split ring in function 'virtqueue_detach_unused_buf_*'. Signed-off-by: Pankaj Gupta --- drivers/virtio/virtio_ring.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c index c8be1c

[PATCH v2 0/2] virtio_console: fix replug of virtio console port

This patch series fixes the issue with unplug/replug of a port in virtio console device, which fails with an error "Error allocating inbufs\n". Patch 2 makes virtio packed ring code compatible with virtio split ring. Tested the packed ring code with the qemu virtio 1.1 device code posted here [1].

[PATCH v3 0/2] dt-bindings: net: meson-dwmac: convert to yaml

This patchsets converts the Amlogic Meson DWMAC glue bindings over to YAML schemas using the already converted dwmac bindings. The first patch is needed because the Amlogic glue needs a supplementary reg cell to access the DWMAC glue registers. Changes since v2: - Added review tags - Updated allw

[PATCH v3 2/2] dt-bindings: net: meson-dwmac: convert to yaml

Now that we have the DT validation in place, let's convert the device tree bindings for the Synopsys DWMAC Glue for Amlogic SoCs over to a YAML schemas. Reviewed-by: Rob Herring Reviewed-by: Martin Blumenstingl Signed-off-by: Neil Armstrong --- .../bindings/net/amlogic,meson-dwmac.yaml | 1

[PATCH v3 1/2] dt-bindings: net: snps,dwmac: update reg minItems maxItems

The Amlogic Meson DWMAC glue bindings needs a second reg cells for the glue registers, thus update the reg minItems/maxItems to allow more than a single reg cell. Also update the allwinner,sun7i-a20-gmac.yaml derivative schema to specify maxItems to 1. Signed-off-by: Neil Armstrong Acked-by: Rob

Re: [RFC][Patch v11 1/2] mm: page_hinting: core infrastructure

On 7/12/19 12:22 PM, Alexander Duyck wrote: > On Thu, Jul 11, 2019 at 6:13 PM Nitesh Narayan Lal wrote: >> >> On 7/11/19 7:20 PM, Alexander Duyck wrote: >>> On Thu, Jul 11, 2019 at 10:58 AM Nitesh Narayan Lal >>> wrote: On 7/10/19 5:56 PM, Alexander Duyck wrote: > On Wed, Jul 10, 2019

Re: [PATCH] cpufreq: schedutil: fix equation in comment

On 08/07/19 11:42, Rafael J. Wysocki wrote: > On Monday, August 5, 2019 3:06:20 PM CEST Peter Zijlstra wrote: > > On Fri, Aug 02, 2019 at 11:46:28AM +0100, Qais Yousef wrote: > > > scale_irq_capacity() call in schedutil_cpu_util() does > > > > > > util *= (max - irq) > > > util /= max > > > >

Re: [PATCH 2/2] clk: samsung: exynos5800: Move MAU subsystem clocks to MAU sub-CMU

Hi Sylwester, On 2019-08-07 18:24, Sylwester Nawrocki wrote: > This patch fixes broken sound on Exynos5422/5800 platforms after > system/suspend resume cycle in cases where the audio root clock > is derived from MAU_EPLL_CLK. > > In order to preserve state of the USER_MUX_MAU_EPLL_CLK clock mux >

Re: Let's talk about the elephant in the room - the Linux kernel's inability to gracefully handle low memory pressure

On Wed 07-08-19 16:51:38, Johannes Weiner wrote: [...] > >From 9efda85451062dea4ea287a886e515efefeb1545 Mon Sep 17 00:00:00 2001 > From: Johannes Weiner > Date: Mon, 5 Aug 2019 13:15:16 -0400 > Subject: [PATCH] psi: trigger the OOM killer on severe thrashing > > Over the last few years we have ha

Re: [PATCH 1/2] clk: samsung: Change signature of exynos5_subcmus_init() function

On 2019-08-07 18:24, Sylwester Nawrocki wrote: > In order to make it easier in subsequent patch to create different subcmu > lists for exynos5420 and exynos5800 SoCs the code is rewritten so we pass > an array of pointers to the subcmus initialization function. > > Signed-off-by: Sylwester Nawroc

Re: [PATCH] epoll: optimize epmutex in ep_free and eventpoll_release_file

Hi, Zhou Xiong test it on 2 sockets 128 cores ARM64 box, and get the following numbers: seconds, smaller is better: concurrency 5.3-rc2 patched diff (smaller is better) 10 6.983 4.6

Re: [PATCH v2 1/2] virtio_console: free unused buffers with port delete

On Thu, Aug 08, 2019 at 05:06:05PM +0530, Pankaj Gupta wrote: > The commit a7a69ec0d8e4 ("virtio_console: free buffers after reset") > deferred detaching of unused buffer to virtio device unplug time. > > This causes unplug/replug of single port in virtio device with an > error "Error allo

Re: [PATCH v2 2/2] virtio_ring: packed ring: fix virtqueue_detach_unused_buf

On Thu, Aug 08, 2019 at 05:06:06PM +0530, Pankaj Gupta wrote: > This patch makes packed ring code compatible with split ring in function > 'virtqueue_detach_unused_buf_*'. What does that mean? What does this "fix"? thanks, greg k-h

[PATCH 0/2] introduce update_irq_devid and optimize VFIO irq ops

Currently, VFIO takes a lot of free-then-request-irq actions whenever a VM (with device passthru via VFIO) sets irq affinity or mask/unmask irq. Those actions only change the cookie data of irqaction or even change nothing. The free-then-request-irq not only add more latency, but also increases the

[PATCH 1/2] genirq: introduce update_irq_devid()

Sometimes, only the dev_id field of irqaction need to be changed. E.g. KVM VM with device passthru via VFIO may switch irq injection path between KVM irqfd and userspace eventfd. These two paths share the same irq num and handler for the same vector of a device, only with different dev_id referenci

Re: [PATCH v2 1/9] soc: samsung: Add exynos chipid driver support

On 7/23/19 14:57, Krzysztof Kozlowski wrote: >> diff --git a/drivers/soc/samsung/exynos-chipid.c >> b/drivers/soc/samsung/exynos-chipid.c >> --- /dev/null >> +++ b/drivers/soc/samsung/exynos-chipid.c >> @@ -0,0 +1,111 @@ >> +// SPDX-License-Identifier: GPL-2.0 >> +#include >> +#include >> +#in

[PATCH 2/2] vfio_pci: make use of update_irq_devid and optimize irq ops

When userspace (e.g. qemu) triggers a switch between KVM irqfd and userspace eventfd, only dev_id of irq action (i.e. the "trigger" in this patch's context) will be changed, but a free-then-request-irq action is taken in current code. And, irq affinity setting in VM will also trigger a free-then-re

Re: [PATCH v2 2/9] soc: samsung: Convert exynos-chipid driver to use the regmap API

On 7/23/19 15:01, Krzysztof Kozlowski wrote: > On Thu, 18 Jul 2019 at 16:31, Sylwester Nawrocki > wrote: >> >> Convert the driver to use regmap API in order to allow other >> drivers, like ASV, to access the CHIPID registers. >> >> This patch adds definition of selected CHIPID register offsets >>

Re: [PATCH v2 3/9] soc: samsung: Add Exynos Adaptive Supply Voltage driver

On 7/23/19 15:38, Krzysztof Kozlowski wrote: > On Thu, 18 Jul 2019 at 16:31, Sylwester Nawrocki > wrote: >> >> The Adaptive Supply Voltage (ASV) driver adjusts CPU cluster operating >> points depending on exact revision of an SoC retrieved from the CHIPID >> block or the OTP memory. This allows

Re: [linux-sunxi] [PATCH 0/3] Add basic support for RTC on Allwinner H6 SoC

On Wed, Aug 07, 2019 at 12:55:02PM +0200, Alexandre Belloni wrote: > Hi, > > On 06/08/2019 20:30:45+0200, Ondřej Jirman wrote: > > Maybe whether XO or DCXO is used also matters if you want to do some fine > > tunning of DCXO (control register has pletny of options), but that's > > probably > > be

Re: [PATCH 2/2] clk: samsung: exynos5800: Move MAU subsystem clocks to MAU sub-CMU

On 8/8/19 13:48, Marek Szyprowski wrote: >> +static struct exynos5_subcmu_reg_dump exynos5800_mau_suspend_regs[] = { >> +{ SRC_TOP9, 0, BIT(8) }, > I would like to add a following comment: > > /* MUX mout_user_mau_epll */ > > to the above line to indicate which clock it refers (like it is don

Re: [PATCH] riscv: kbuild: drop CONFIG_RISCV_ISA_C

Please do not drop it. Compressed instruction extension has some specific overhead in small RISC-V FPGA softcore, especialy in the ones which can't implement the register file read in a asynchronous manner because of the FPGA technology. What are reasons to enforce RVC ? On Wed, Aug 7, 2019 at 2:

Re: [PATCH v2 1/2] virtio_console: free unused buffers with port delete

> > On Thu, Aug 08, 2019 at 05:06:05PM +0530, Pankaj Gupta wrote: > > The commit a7a69ec0d8e4 ("virtio_console: free buffers after reset") > > deferred detaching of unused buffer to virtio device unplug time. > > > > This causes unplug/replug of single port in virtio device with an > >

Re: [PATCH v3 03/24] dmaengine: imx-sdma: Remove call to memset after dma_alloc_coherent

On 15-07-19, 11:17, Fuqian Huang wrote: > In commit 518a2f1925c3 > ("dma-mapping: zero memory returned from dma_alloc_*"), > dma_alloc_coherent has already zeroed the memory. > So memset is not needed. Applied, thanks -- ~Vinod

Re: [PATCH v3 04/24] dmaengine: qcom_hidma: Remove call to memset after dmam_alloc_coherent

On 15-07-19, 11:17, Fuqian Huang wrote: > In commit 518a2f1925c3 > ("dma-mapping: zero memory returned from dma_alloc_*"), > dma_alloc_coherent has already zeroed the memory. > So memset is not needed. Applied, thanks -- ~Vinod

[PATCH] habanalabs: Expose devices after initialization is done

The char devices are currently exposed to user before the device and driver initialization are done. This patch moves the cdev and device adding to the system to the end of the initialization sequence, while keeping the creation of the structures at the beginning to allow the usage of dev_*(). Sig

Re: [RESEND PATCH v7] dmaengine: fsl-edma: add i.mx7ulp edma2 version support

On 24-07-19, 15:20, Robin Gong wrote: > Add edma2 for i.mx7ulp by version v3, since v2 has already > been used by mcf-edma. > The big changes based on v1 are belows: > 1. only one dmamux. > 2. another clock dma_clk except dmamux clk. > 3. 16 independent interrupts instead of only one interrupt for

Re: [PATCH v2] regulator: core: Add of_node_put() before return

On Thu, Aug 08, 2019 at 12:35:53PM +0530, Nishka Dasgupta wrote: > In function of_get_child_regulator(), the loop for_each_child_of_node() > contains two mid-loop return statements. Ordinarily the loop gets the > node child at the beginning of every iteration and automatically puts Please do not s

Re: [PATCH v2 2/2] virtio_ring: packed ring: fix virtqueue_detach_unused_buf

> > This patch makes packed ring code compatible with split ring in function > > 'virtqueue_detach_unused_buf_*'. > > What does that mean? What does this "fix"? Patch 1 frees the buffers When a port is unplugged from the virtio console device. It does this with the help of 'virtqueue_detach_

[PATCH] habanalabs: Handle HW_IP_INFO if device disabled or in reset

The HW IP information is relevant even if the device is disabled or in reset, so always handle the corresponding INFO IOCTL opcode. Signed-off-by: Tomer Tayar --- drivers/misc/habanalabs/habanalabs_ioctl.c | 19 +-- 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/d

[PATCH v2 04/15] net: phy: adin: add support for interrupts

This change adds support for enabling PHY interrupts that can be used by the PHY framework to get signal for link/speed/auto-negotiation changes. Signed-off-by: Alexandru Ardelean --- drivers/net/phy/adin.c | 38 ++ 1 file changed, 38 insertions(+) diff --git

[PATCH v2 10/15] net: phy: adin: add EEE translation layer from Clause 45 to Clause 22

The ADIN1200 & ADIN1300 PHYs support EEE by using standard Clause 45 access to access MMD registers for EEE. The EEE register addresses (when using Clause 22) are available at different addresses (than Clause 45), and since accessing these regs (via Clause 22) needs a special mechanism, a translat

[PATCH v2 06/15] net: phy: adin: configure RGMII/RMII/MII modes on config

The ADIN1300 chip supports RGMII, RMII & MII modes. Default (if unconfigured) is RGMII. This change adds support for configuring these modes via the device registers. For RGMII with internal delays (modes RGMII_ID,RGMII_TXID, RGMII_RXID), the default delay is 2 ns. This can be configurable and wil

[PATCH v2 12/15] net: phy: adin: implement Energy Detect Powerdown mode

The ADIN PHYs support Energy Detect Powerdown mode, which puts the PHY into a low power mode when there is no signal on the wire (typically cable unplugged). This behavior is enabled by default, but can be disabled via device property. Signed-off-by: Alexandru Ardelean --- drivers/net/phy/adin.c

[PATCH v2 13/15] net: phy: adin: configure downshift on config_init

Down-speed auto-negotiation may not always be enabled, in which case the PHY won't down-shift to 100 or 10 during auto-negotiation. This change enables downshift and configures the number of retries to default 8 (maximum supported value). The change has been adapted from the Marvell PHY driver.

[PATCH v2 07/15] net: phy: adin: make RGMII internal delays configurable

The internal delays for the RGMII are configurable for both RX & TX. This change adds support for configuring them via device-tree (or ACPI). Signed-off-by: Alexandru Ardelean --- drivers/net/phy/adin.c | 82 ++ 1 file changed, 82 insertions(+) diff --git

[PATCH v2 02/15] net: phy: adin: hook genphy_read_abilities() to get_features

The ADIN PHYs can operate with Clause 45, however they are not typical for how phylib considers Clause 45 PHYs. If the `features` field & the `get_features` hook are unspecified, and the device wants to operate via Clause 45, it would also try to read features via the `genphy_c45_pma_read_abilitie

[PATCH v2 15/15] dt-bindings: net: add bindings for ADIN PHY driver

This change adds bindings for the Analog Devices ADIN PHY driver, detailing all the properties implemented by the driver. Signed-off-by: Alexandru Ardelean --- .../devicetree/bindings/net/adi,adin.yaml | 76 +++ MAINTAINERS | 1 + 2 files ch

[PATCH v2 11/15] net: phy: adin: implement PHY subsystem software reset

The ADIN PHYs supports 4 types of reset: 1. The standard PHY reset via BMCR_RESET bit in MII_BMCR reg 2. Reset via GPIO 3. Reset via reg GeSftRst (0xff0c) & reload previous pin configs 4. Reset via reg GeSftRst (0xff0c) & request new pin configs Resets 2 & 4 are almost identical, with the exceptio

[PATCH v2 14/15] net: phy: adin: add ethtool get_stats support

This change implements retrieving all the error counters from the PHY. The PHY supports several error counters/stats. The `Mean Square Errors` status values are only valie when a link is established, and shouldn't be accumulated. These values characterize the quality of a signal. The rest of the e

[PATCH v2 09/15] net: phy: adin: add support MDI/MDIX/Auto-MDI selection

The ADIN PHYs support automatic MDI/MDIX negotiation. By default this is disabled, so this is enabled at `config_init`. This is controlled via the PHY Control 1 register. The supported modes are: 1. Manual MDI 2. Manual MDIX 3. Auto MDIX - prefer MDIX 4. Auto MDIX - prefer MDI The phydev

[PATCH v2 08/15] net: phy: adin: make RMII fifo depth configurable

The FIFO depth can be configured for the RMII mode. This change adds support for doing this via device-tree (or ACPI). Signed-off-by: Alexandru Ardelean --- drivers/net/phy/adin.c | 29 + 1 file changed, 29 insertions(+) diff --git a/drivers/net/phy/adin.c b/drivers/

Re: [PATCH v2 3/9] soc: samsung: Add Exynos Adaptive Supply Voltage driver

On Thu, 8 Aug 2019 at 14:07, Sylwester Nawrocki wrote: > >> +static unsigned int exynos5422_asv_parse_table(struct exynos_asv *asv, > >> + unsigned int pkg_id) > >> +{ > >> + return (pkg_id >> EXYNOS5422_TABLE_OFFSET) & EXYNOS5422_TABLE_MASK; > >> +} > >>

[PATCH v2] selftests: kvm: Adding config fragments

selftests kvm all test cases need pre-required kernel configs for the tests to get pass. The KVM tests are skipped without these configs: dev_fd = open(KVM_DEV_PATH, O_RDONLY); if (dev_fd < 0) exit(KSFT_SKIP); Signed-off-by: Naresh Kamboju --- tools/testing/self

[PATCH v2 00/15] net: phy: adin: add support for Analog Devices PHYs

This changeset adds support for Analog Devices Industrial Ethernet PHYs. Particularly the PHYs this driver adds support for: * ADIN1200 - Robust, Industrial, Low Power 10/100 Ethernet PHY * ADIN1300 - Robust, Industrial, Low Latency 10/100/1000 Gigabit Ethernet PHY The 2 chips are pin & regis

[PATCH v2 03/15] net: phy: adin: hook genphy_{suspend,resume} into the driver

The chip supports standard suspend/resume via BMCR reg. Hook these functions into the `adin` driver. Signed-off-by: Alexandru Ardelean --- drivers/net/phy/adin.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/net/phy/adin.c b/drivers/net/phy/adin.c index 879797d076e0..45490fbe27

[PATCH v2 05/15] net: phy: adin: add {write,read}_mmd hooks

Both ADIN1200 & ADIN1300 support Clause 45 access. The Extended Management Interface (EMI) registers are accessible via both Clause 45 (at register MDIO_MMD_VEND1) and using Clause 22. However, the Clause 22 MMD access operations differ from the implementation in the kernel, in the sense that it u

[PATCH v2 01/15] net: phy: adin: add support for Analog Devices PHYs

This change adds support for Analog Devices Industrial Ethernet PHYs. Particularly the PHYs this driver adds support for: * ADIN1200 - Robust, Industrial, Low Power 10/100 Ethernet PHY * ADIN1300 - Robust, Industrial, Low Latency 10/100/1000 Gigabit Ethernet PHY The 2 chips are pin & register

[PATCH] ASoC: soc-core: remove error due to probe deferral

From: Stefan Agner Deferred probes shouldn't cause error messages in the boot log. Avoid printing with dev_err() in case EPROBE_DEFER is the return value. Signed-off-by: Stefan Agner --- sound/soc/soc-core.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/sound/soc/soc-c

[PATCH RESEND] fs: use UB-safe check for signed addition overflow in remap_verify_area

The following warning pops up with enabled UBSAN in tests fstests/generic/303: [23127.529395] UBSAN: Undefined behaviour in fs/read_write.c:1725:7 [23127.529400] signed integer overflow: [23127.529403] 4611686018427322368 + 9223372036854775807 cannot be represented in type 'long long int'

Re: [PATCH] [RFC] dmaengine: add fifo_size member

On 02-08-19, 09:51, Jon Hunter wrote: > > On 31/07/2019 16:16, Vinod Koul wrote: > > On 31-07-19, 10:48, Jon Hunter wrote: > >> > >> On 29/07/2019 07:10, Vinod Koul wrote: > >>> On 23-07-19, 11:24, Sameer Pujar wrote: > > On 7/19/2019 10:34 AM, Vinod Koul wrote: > > On 05-07-19, 11:4

Re: [PATCH v2 2/2] virtio_ring: packed ring: fix virtqueue_detach_unused_buf

On Thu, Aug 08, 2019 at 08:28:46AM -0400, Pankaj Gupta wrote: > > > > > This patch makes packed ring code compatible with split ring in function > > > 'virtqueue_detach_unused_buf_*'. > > > > What does that mean? What does this "fix"? > > Patch 1 frees the buffers When a port is unplugged from

Re: [PATCH 2/2] ARM: dts: at91: sama5d27_som1_ek: add mmc capabilities for SDMMC0

On Thu, Aug 08, 2019 at 10:35:43AM +0200, Eugen Hristev - M18282 wrote: > From: Eugen Hristev > > Add mmc capabilities for SDMMC0 for this board. > With this enabled, eMMC connected card is detected as: > > mmc0: new DDR MMC card at address 0001 > > Signed-off-by: Eugen Hristev Acked-by: Ludov

Re: [PATCH 1/2] mmc: sdhci-of-at91: add quirk for broken HS200

On Thu, Aug 08, 2019 at 10:35:40AM +0200, Eugen Hristev - M18282 wrote: > From: Eugen Hristev > > HS200 is not implemented in the driver, but the controller claims it > through caps. > Remove it via quirk. > Without this quirk, the mmc core will try to enable hs200, which will fail, > and the eMM

Re: [PATCH v2 2/2] virtio_ring: packed ring: fix virtqueue_detach_unused_buf

> On Thu, Aug 08, 2019 at 08:28:46AM -0400, Pankaj Gupta wrote: > > > > > > > > This patch makes packed ring code compatible with split ring in > > > > function > > > > 'virtqueue_detach_unused_buf_*'. > > > > > > What does that mean? What does this "fix"? > > > > Patch 1 frees the buffers W

Re: [PATCH] ASoC: soc-core: remove error due to probe deferral

On Thu, Aug 08, 2019 at 02:36:55PM +0200, Stefan Agner wrote: > From: Stefan Agner > > Deferred probes shouldn't cause error messages in the boot log. Avoid > printing with dev_err() in case EPROBE_DEFER is the return value. No, they absolutely should tell the user why they are deferring so the

Re: [PATCH] scripts/checkpatch.pl - fix *_NOTIFIER_HEAD handling

On Thu, 2019-08-08 at 02:08 -0400, Valdis Klētnieks wrote: > On Wed, 07 Aug 2019 22:50:47 -0700, Joe Perches said: > > On Wed, 2019-08-07 at 21:36 -0400, Valdis Kltnieks wrote: > > > ^.DEFINE_$Ident\(\Q$name\E\)| > > > ^.DECLARE_$Ident\(\Q$name\E\

[tip:ras/core 2/2] drivers/ras/debugfs.c:10:5: error: redefinition of 'ras_userspace_consumers'

tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/tip/tip.git ras/core head: 963c712947207cc6117b4bd68427a63591f18786 commit: 963c712947207cc6117b4bd68427a63591f18786 [2/2] RAS: Fix prototype warnings config: riscv-defconfig (attached as .config) compiler: riscv64-linux-gcc (GCC)

[PATCH] powerpc/64e: drop stale call to smp_processor_id() which hangs SMP startup

Santa commit ebb9d30a6a74 ("powerpc/mm: any thread in one core can be the first to setup TLB1") removed the need to know the cpu_id in early_init_this_mmu(), but the call to smp_processor_id() which was marked __maybe_used remained. Since commit ed1cd6deb013 ("powerpc: Activate CONFIG_THREAD_INFO_

Re: [PATCH v2 3/9] soc: samsung: Add Exynos Adaptive Supply Voltage driver

On 08/08/2019 13:31, Krzysztof Kozlowski wrote: On Thu, 8 Aug 2019 at 14:07, Sylwester Nawrocki wrote: +static unsigned int exynos5422_asv_parse_table(struct exynos_asv *asv, + unsigned int pkg_id) +{ + return (pkg_id >> EXYNOS5422_TABLE_OFFSET) & EXYNO

Re: [PATCH] usb: dwc3: remove generic PHYs forwarding for XHCI device

Hi, Marek Szyprowski writes: > Commit 08f871a3aca2 ("usb: dwc3: host: convey the PHYs to xhci") added > forwarding of the generic PHYs from DWC3 core to the instantiated XHCI-plat > device. However XHCI(-plat) driver never gained support for generic PHYs, > thus the lookup added by that commit

[PATCH v2 1/2] ARM: zynq: support smp in thumb mode

Add .arm directive to headsmp.S to ensure that the CPU starts in 32-bit ARM mode and the correct code size is copied on smp bring-up. This is related to the fix applied to SoCFPGA by commit 5616f36713ea ("ARM: SoCFPGA: Fix secondary CPU startup in thumb2 kernel") Additionally, start secondary CPUs

[PATCH v2 0/2] ARM: zynq: smp improvements

This series adds support for kernel compiled in Thumb mode and fixes a kernel panic on smp bring-up when FORTIFY_SOURCE is enabled. The series started with the second patch as an RFC, and the first patch were suggested on the review to complement the fix. The changes were run-tested on a Digilent

[PATCH v2 2/2] ARM: zynq: Use memcpy_toio instead of memcpy on smp bring-up

This fixes a kernel panic on memcpy when FORTIFY_SOURCE is enabled. The initial smp implementation on commit aa7eb2bb4e4a ("arm: zynq: Add smp support") used memcpy, which worked fine until commit ee333554fed5 ("ARM: 8749/1: Kconfig: Add ARCH_HAS_FORTIFY_SOURCE") enabled overflow checks at runtime

drivers/clk/bcm/clk-bcm2835.c:2144:1-13: WARNING: Use devm_platform_ioremap_resource for cprman -> regs (fwd)

-- Forwarded message -- Date: Thu, 8 Aug 2019 20:52:32 +0800 From: kbuild test robot To: kbu...@01.org Cc: Julia Lawall Subject: drivers/clk/bcm/clk-bcm2835.c:2144:1-13: WARNING: Use devm_platform_ioremap_resource for cprman -> regs CC: kbuild-...@01.org CC: linux-kernel@v

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