[PATCH] usb/gadget: f_midi: Replace tasklet with work

Currently a tasklet is used to transmit input substream buffer data. However, tasklets have long been deprecated as being too heavy on the system by running in irq context - and this is not a performance critical path. If a higher priority process wants to run, it must wait for the tasklet to

Re: [Freedreno] [PATCH] drm/msm: Only enable A6xx LLCC code on A6xx

Hi Rob, On 2021-01-08 22:16, Rob Clark wrote: On Fri, Jan 8, 2021 at 6:05 AM Sai Prakash Ranjan wrote: On 2021-01-08 19:09, Konrad Dybcio wrote: >> Konrad, can you please test this below change without your change? > > This brings no difference, a BUG still happens. We're still calling >

Re: [PATCH 1/1] arm64: make section size configurable for memory hotplug

On 1/8/21 9:00 PM, David Hildenbrand wrote: >> To summarize, the section size bits for each base page size config >> should always >> >> a. Avoid (MAX_ORDER - 1 + PAGE_SHIFT) > SECTION_SIZE_BITS > > Pageblocks must also always fall completely into a section. > >> >> b. Provide minimum

Re: [PATCH v18 3/3] scsi: ufs: Prepare HPB read for cached sub-region

On 2020-12-22 09:58, Daejun Park wrote: This patch changes the read I/O to the HPB read I/O. If the logical address of the read I/O belongs to active sub-region, the HPB driver modifies the read I/O command to HPB read. It modifies the UPIU command of UFS instead of modifying the existing

Re: [PATCH 3/6] hugetlb: add free page reporting support

On Fri, Jan 8, 2021 at 6:04 AM Mike Kravetz wrote: > > On 1/5/21 7:49 PM, Liang Li wrote: > > hugetlb manages its page in hstate's free page list, not in buddy > > system, this patch try to make it works for hugetlbfs. It canbe > > used for memory overcommit in virtualization and hugetlb pre zero

Re: [PATCH 0/4] Assorted fixes for RV32

Hi Palmer, On Thu, Jan 7, 2021 at 2:57 PM Atish Patra wrote: > > This series fixes various issues observed in latest kernel on RV32. > The first two patches fixes an resource tree introduced in 5.11-rc1 > while the last two fixes the case where 2GB physical memory is used > on RV32. > > There

Re: [PATCH 4/4] RISC-V: Fix maximum allowed phsyical memory for RV32

On Thu, Jan 7, 2021 at 2:57 PM Atish Patra wrote: > > Linux kernel can only map 1GB of address space for RV32 as the page offset > is set to 0xC000. The current description in the Kconfig is confusing > as it indicates that RV32 can support 2GB of physical memory. That is > simply not true

Re: [PATCH v7 08/18] virt: acrn: Introduce EPT mapping management

On Fri 8.Jan'21 at 16:34:06 +0100, Greg Kroah-Hartman wrote: On Wed, Jan 06, 2021 at 03:50:45PM +0800, shuo.a@intel.com wrote: +/** + * struct acrn_vm_memmap - A EPT memory mapping info for a User VM. + * @type: Type of the memory mapping (ACRM_MEMMAP_*). + *

Re: [PATCH v7 07/18] virt: acrn: Introduce an ioctl to set vCPU registers state

On Fri 8.Jan'21 at 16:33:22 +0100, Greg Kroah-Hartman wrote: On Wed, Jan 06, 2021 at 03:50:44PM +0800, shuo.a@intel.com wrote: From: Shuo Liu A virtual CPU of User VM has different context due to the different registers state. ACRN userspace needs to set the virtual CPU registers state

Re: [PATCH 3/4] RISC-V: Fix L1_CACHE_BYTES for RV32

On Thu, Jan 7, 2021 at 2:57 PM Atish Patra wrote: > > SMP_CACHE_BYTES/L1_CACHE_BYTES should be defined as 32 instead of > 64 for RV32. Otherwise, there will be hole of 32 bytes with each memblock > allocation if it is requested to be aligned with SMP_CACHE_BYTES. > > Signed-off-by: Atish Patra

Re: [PATCH 2/4] RISC-V: Set current memblock limit

On Thu, Jan 7, 2021 at 2:57 PM Atish Patra wrote: > > Currently, linux kernel can not use last 4k bytes of addressable space because > IS_ERR_VALUE macro treats those as an error. This will be an issue for RV32 > as any memblock allocator potentially allocate chunk of memory from the end > of

Re: [PATCH 3/6] hugetlb: add free page reporting support

> >> On Tue 05-01-21 22:49:21, Liang Li wrote: > >>> hugetlb manages its page in hstate's free page list, not in buddy > >>> system, this patch try to make it works for hugetlbfs. It canbe > >>> used for memory overcommit in virtualization and hugetlb pre zero > >>> out. > >> > >> David has layed

Re: [PATCH v7 06/18] virt: acrn: Introduce VM management interfaces

On Fri 8.Jan'21 at 16:31:34 +0100, Greg Kroah-Hartman wrote: On Wed, Jan 06, 2021 at 03:50:43PM +0800, shuo.a@intel.com wrote: From: Shuo Liu The VM management interfaces expose several VM operations to ACRN userspace via ioctls. For example, creating VM, starting VM, destroying VM and

[PATCH] mm/vmstat.c: erase latency in vmstat_shepherd

From: Jiang Biao Many 100us+ latencies have been deteceted in vmstat_shepherd() on CPX platform which has 208 logic cpus. And vmstat_shepherd is queued every second, which could make the case worse. Add schedule point in vmstat_shepherd() to erase the latency. Signed-off-by: Jiang Biao

Re: [PATCH 1/4] RISC-V: Do not allocate memblock while iterating reserved memblocks

On Thu, Jan 7, 2021 at 2:57 PM Atish Patra wrote: > > Currently, resource tree allocates memory blocks while iterating on the > list. It leads to following kernel warning because memblock allocation > also invokes memory block reservation API. > > [0.00] [ cut here

Re: [PATCH v6 5/5] ARM: dts: add Kverneland TGO board

On Thu, Jan 07, 2021 at 11:08:31AM +0100, Oleksij Rempel wrote: > VICTGO is the Kverneland TGO IsoBus universal terminal for agricultural > applications on tractors > > Co-Developed-by: David Jander > Signed-off-by: David Jander > Signed-off-by: Oleksij Rempel > --- >

Re: [PATCH] arm64: dts: rockchip: rename pinctrl nodename to gmac2io for nanopi-r2s board

Hi Rob, On Mon, Jan 11, 2021 at 3:50 AM Johan Jonker wrote: > > A test with the command below gives this error: > /arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dt.yaml: > ethernet-phy: 'reg' is a required property > > The pinctrl nodename "ethernet-phy" conflicts with the rules > in the

Re: [PATCH v2] proc_sysctl: fix oops caused by incorrect command parameters.

On 2021/1/9 9:50, Andrew Morton wrote: On Fri, 8 Jan 2021 21:10:25 +0100 Michal Hocko wrote: Why would that matter? A missing value is clearly a error path and it should be reported. This test is in the correct place. I think it's just a question of the return values. I was probably not

Re: [PATCH v6 3/5] ARM: dts: add Kverneland UT1, UT1Q and UT1P

On Thu, Jan 07, 2021 at 11:08:29AM +0100, Oleksij Rempel wrote: > VICUT1(Q,P) is the Kverneland UT1(Q,P) IsoBus universal terminal for > agricultural > applications on tractors. > > Co-Developed-by: David Jander > Signed-off-by: David Jander > Signed-off-by: Oleksij Rempel > --- >

Re: [PATCH 3/3] arm64: dts: rockchip: rk3328: Add Radxa ROCK Pi E

On Mon, Jan 11, 2021 at 4:17 AM Johan Jonker wrote: > > Hi Chen-Yu, > > Most is already answered by Heiko. > > On 1/10/21 4:37 PM, Chen-Yu Tsai wrote: > > Hi, > > > > On Sun, Jan 10, 2021 at 10:45 PM Johan Jonker wrote: > >> > >> Hi Chen-Yu, > >> > >> Some comments, have a look if it is

linux-next: build warnings after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (htmldocs) produced these warnings: Documentation/fpga/dfl.rst:505: WARNING: Title underline too short. Location of DFLs on a PCI Device === Documentation/fpga/dfl.rst:505: WARNING: Title underline too

Re: [PATCH] mmc: sdhci-iproc: Add ACPI bindings for the rpi4

Hi, On 1/9/21 5:07 AM, Stefan Wahren wrote: Hi Jeremy, +add Nicolas Am 08.01.21 um 22:13 schrieb Jeremy Linton: The rpi4 has a Arasan controller it carries over from the rpi3, and a newer eMMC2 controller. Because of a couple "quirks" it seems wiser to bind these controllers to the same

linux-next: build warnings after merge of the amdgpu tree

Hi all, After merging the amdgpu tree, today's linux-next build (htmldocs) produced these warnings: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:340: warning: Incorrect use of kernel-doc format: * @active_vblank_irq_count drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:379:

Re: [PATCH v2 0/2] mainline Protonic PRTI6G board

On Thu, Jan 07, 2021 at 09:52:31AM +0100, Oleksij Rempel wrote: > changes v2: > - reorder pinctls > > Oleksij Rempel (2): > dt-bindings: arm: fsl: add Protonic PRTI6G board > ARM: dts: add Protonic PRTI6G board Applied both, thanks.

Re: [PATCH v3 0/2] mainline Protonic MVT board

On Wed, Jan 06, 2021 at 10:04:12AM +0100, Oleksij Rempel wrote: > changes v3: > - use defines linux,code > - sour out some spaces > - move compatible to the beginning of the gpio_pca node. > > changes v2: > - fix active level of SPI CS GPIOs > > Oleksij Rempel (2): > dt-bindings: arm: fsl:

[PATCH] drm/hisilicon: Use drm_crtc_mask()

Use drm_crtc_mask() where appropriate. Signed-off-by: Tian Tao --- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_vdac.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_vdac.c b/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_vdac.c index

Re: [PATCH v5 1/2] dt-bindings: arm: fsl: Add binding for Gateworks boards with IMX8MM

On Mon, Jan 04, 2021 at 09:36:46AM -0800, Tim Harvey wrote: > Add bindings for the Gateworks Venice Development kit boards with > IMX8MM System on Module. > > Signed-off-by: Tim Harvey Applied both, thanks.

Re: [PATCH 3/3] arm64: dts: rockchip: rk3328: Add Radxa ROCK Pi E

On Mon, Jan 11, 2021 at 4:06 AM Heiko Stübner wrote: > > Hi, > > Am Sonntag, 10. Januar 2021, 16:37:15 CET schrieb Chen-Yu Tsai: > > > > + vcc_sd: sdmmc-regulator { > > > > + compatible = "regulator-fixed"; > > > > + gpio = < RK_PD6 GPIO_ACTIVE_LOW>; > > > > +

imx-scu-soc.c:undefined reference to `soc_device_register'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 7c53f6b671f4aba70ff15e1b05148b10d58c2837 commit: d7071743db31b4f6898b1c742e4b451bb4bc4b02 RISC-V: Add EFI stub support. date: 3 months ago config: riscv-randconfig-r022-20210111 (attached as .config)

Re: [PATCH v2] proc_sysctl: fix oops caused by incorrect command parameters.

On 2021/1/9 17:10, Andy Shevchenko wrote: On Friday, January 8, 2021, Xiaoming Ni > wrote: The process_sysctl_arg() does not check whether val is empty before  invoking strlen(val). If the command line parameter () is incorrectly  configured and

Re: [PATCH v3 7/7] bio: don't copy bvec for direct IO

On Sat, Jan 09, 2021 at 04:03:03PM +, Pavel Begunkov wrote: > The block layer spends quite a while in blkdev_direct_IO() to copy and > initialise bio's bvec. However, if we've already got a bvec in the input > iterator it might be reused in some cases, i.e. when new > ITER_BVEC_FLAG_FIXED flag

Re: [PATCH v3 6/7] bio: add a helper calculating nr segments to alloc

On Sat, Jan 09, 2021 at 04:03:02PM +, Pavel Begunkov wrote: > Add a helper function calculating the number of bvec segments we need to > allocate to construct a bio. It doesn't change anything functionally, > but will be used to not duplicate special cases in the future. > > Reviewed-by:

Re: [PATCH v3 5/7] iov_iter: optimise bvec iov_iter_advance()

On Sat, Jan 09, 2021 at 04:03:01PM +, Pavel Begunkov wrote: > iov_iter_advance() is heavily used, but implemented through generic > means. For bvecs there is a specifically crafted function for that, so > use bvec_iter_advance() instead, it's faster and slimmer. > > Reviewed-by: Christoph

Re: [PATCH v3 4/7] target/file: allocate the bvec array as part of struct target_core_file_cmd

On Sat, Jan 09, 2021 at 04:03:00PM +, Pavel Begunkov wrote: > From: Christoph Hellwig > > This saves one memory allocation, and ensures the bvecs aren't freed > before the AIO completion. This will allow the lower level code to be > optimized so that it can avoid allocating another bvec

Re: [PATCH v3 3/7] block/psi: remove PSI annotations from direct IO

On Sat, Jan 09, 2021 at 04:02:59PM +, Pavel Begunkov wrote: > Direct IO does not operate on the current working set of pages managed > by the kernel, so it should not be accounted as memory stall to PSI > infrastructure. > > The block layer and iomap direct IO use bio_iov_iter_get_pages() >

Re: [PATCH V7 01/13] dt-bindings: soc: Add dvfsrc driver bindings

Hi Rob, On Fri, 2021-01-08 at 20:30 -0700, Rob Herring wrote: > On Fri, 08 Jan 2021 15:48:03 +0800, Henry Chen wrote: > > Document the binding for enabling dvfsrc on MediaTek SoC. > > > > Signed-off-by: Henry Chen > > --- > > .../devicetree/bindings/soc/mediatek/dvfsrc.yaml | 67 > >

Re: [PATCH v3 2/7] bvec/iter: disallow zero-length segment bvecs

On Sat, Jan 09, 2021 at 04:02:58PM +, Pavel Begunkov wrote: > zero-length bvec segments are allowed in general, but not handled by bio > and down the block layer so filtered out. This inconsistency may be > confusing and prevent from optimisations. As zero-length segments are > useless and

Re: [PATCH v3 1/7] splice: don't generate zero-len segement bvecs

On Sat, Jan 09, 2021 at 04:02:57PM +, Pavel Begunkov wrote: > iter_file_splice_write() may spawn bvec segments with zero-length. In > preparation for prohibiting them, filter out by hand at splice level. > > Reviewed-by: Christoph Hellwig > Signed-off-by: Pavel Begunkov > --- > fs/splice.c

Re: [PATCH] target/file: don't zero iter before iov_iter_bvec

On 1/9/21 7:53 AM, Pavel Begunkov wrote: > iov_iter_bvec() initialises iterators well, no need to pre-zero it > beforehand as done in fd_execute_rw_aio(). Compilers can't optimise it > out and generate extra code for that (confirmed with assembly). Reviewed-by: Bart Van Assche

Re: [PATCH 4.19 13/35] null_blk: Fix zone size initialization

On 2021/01/06 21:55, Pavel Machek wrote: > Hi! > >> commit 0ebcdd702f49aeb0ad2e2d894f8c124a0acc6e23 upstream. >> >> For a null_blk device with zoned mode enabled is currently initialized >> with a number of zones equal to the device capacity divided by the zone >> size, without considering if the

Re: [PATCH v10 1/4] dt-bindings: soc: imx8m: add DT Binding doc for soc unique ID

On Mon, Jan 04, 2021 at 05:15:41PM +0800, Alice Guo (OSS) wrote: > From: Alice Guo > > Add DT Binding doc for the Unique ID of i.MX 8M series. > > Reviewed-by: Krzysztof Kozlowski > Reviewed-by: Rob Herring > Signed-off-by: Alice Guo Applied all, thanks.

Re: [PATCH] target/file: don't zero iter before iov_iter_bvec

On 11/01/2021 02:06, Chaitanya Kulkarni wrote: > On 1/9/21 13:29, Pavel Begunkov wrote: >> On 09/01/2021 20:52, Chaitanya Kulkarni wrote: >>> On 1/9/21 12:40, Pavel Begunkov wrote: I expect you won't find any, but such little things can pile up into a not-easy-to-spot overhead over time.

RE: [PATCH v2 1/3] regulator: mt6360: Add OF match table

[ Internal Use - External ] Hi Matthias, I discussed OF match table with Mark in previous mail in our PATCH v3, MFD should just instantiate the platform device. > Mark Brown 於 2020年8月20日 週四 下午7:45寫道： > > This device only exists in the context of a single parent device, there > > should be no

Re: [PATCH 1/1] usb: gadget: aspeed: fix stop dma register setting.

On Fri, 8 Jan 2021 at 08:13, Ryan Chen wrote: > > The vhub engine has two dma mode, one is descriptor list, another > is single stage DMA. Each mode has different stop register setting. > Descriptor list operation (bit2) : 0 disable reset, 1: enable reset > Single mode operation (bit0) : 0 :

[PATCH v25 5/5] remoteproc: Add initial zynqmp R5 remoteproc driver

R5 is included in Xilinx Zynq UltraScale MPSoC so by adding this remotproc driver, we can boot the R5 sub-system in two different configurations - * Split * Lockstep The Xilinx R5 Remoteproc Driver boots the R5's via calls to the Xilinx Platform Management Unit that handles the R5

linux-next: manual merge of the char-misc tree with the drivers-x86 tree

Hi all, Today's linux-next merge of the char-misc tree got conflicts in: include/linux/mod_devicetable.h scripts/mod/devicetable-offsets.c scripts/mod/file2alias.c between commit: eb0e90a82098 ("platform/surface: aggregator: Add dedicated bus and device type") from the drivers-x86

Re: [PATCH] target/file: don't zero iter before iov_iter_bvec

On 1/9/21 13:29, Pavel Begunkov wrote: > On 09/01/2021 20:52, Chaitanya Kulkarni wrote: >> On 1/9/21 12:40, Pavel Begunkov wrote: >>> I expect you won't find any, but such little things can pile up >>> into a not-easy-to-spot overhead over time. >> That is what I suspected with the resulting

Re: [PATCH v5 mips-next 8/9] vmlinux.lds.h: catch UBSAN's "unnamed data" into data

On Sun, Jan 10, 2021 at 11:56:54AM +, Alexander Lobakin wrote: > When building kernel with both LD_DEAD_CODE_DATA_ELIMINATION and > UBSAN, LLVM stack generates lots of "unnamed data" sections: > > ld.lld: warning: net/built-in.a(netfilter/utils.o): (.data.$__unnamed_2) > is being placed in

[PATCH v25 3/5] firmware: xilinx: Add RPU configuration APIs

This patch adds APIs to access to configure RPU and its processor-specific memory. That is query the run-time mode of RPU as either split or lockstep as well as API to set this mode. In addition add APIs to access configuration of the RPUs' tightly coupled memory (TCM). Signed-off-by: Ben

[PATCH v25 2/5] firmware: xilinx: Add shutdown/wakeup APIs

Add shutdown/wakeup a resource eemi operations to shutdown or bringup a resource. Note alignment of args matches convention of other fn's in this file. The reason being that the long fn name results in aligned args that otherwise go over 80 chars so shift right to avoid this Signed-off-by: Ben

[PATCH v25 4/5] dt-bindings: remoteproc: Add documentation for ZynqMP R5 rproc bindings

Add binding for ZynqMP R5 OpenAMP. Represent the RPU domain resources in one device node. Each RPU processor is a subnode of the top RPU domain node. Signed-off-by: Jason Wu Signed-off-by: Wendy Liang Signed-off-by: Michal Simek Signed-off-by: Ben Levinsky --- v25: - grammar in device tree

[PATCH v25 0/5] Provide basic driver to control Arm R5 co-processor found on Xilinx ZynqMP

R5 is included in Xilinx Zynq UltraScale MPSoC so by adding this remotproc driver, we can boot the R5 sub-system in two different configurations - * Split * Lockstep The Xilinx R5 Remoteproc Driver boots the R5's via calls to the Xilinx Platform Management Unit that handles the R5

[PATCH v25 1/5] firmware: xilinx: Add ZynqMP firmware ioctl enums for RPU configuration.

Add ZynqMP firmware ioctl enums for RPU configuration and TCM Nodes for later use via request_node and release_node Signed-off-by: Ben Levinsky --- v25: - update include/linux/firmware/xlnx-zynqmp.h style to match for enum --- include/linux/firmware/xlnx-zynqmp.h | 23 +++ 1

RE: [RFC PATCH net] udp: check sk for UDP GRO fraglist

On 2021-01-08 22:35, Steffen Klassert wrote: > On Fri, Jan 08, 2021 at 09:52:28PM +0900, Dongseok Yi wrote: > > It is a workaround patch. > > > > UDP/IP header of UDP GROed frag_skbs are not updated even after NAT > > forwarding. Only the header of head_skb from ip_finish_output_gso -> > >

Re: [PATCH 2/2] scsi: ufs: Protect PM ops and err_handler from user access through sysfs

On 2021-01-11 00:13, Bean Huo wrote: On Sat, 2021-01-09 at 12:51 +0800, Can Guo wrote: On 2021-01-09 12:45, Can Guo wrote: > On 2021-01-08 19:29, Bean Huo wrote: > > On Wed, 2021-01-06 at 09:20 +0800, Can Guo wrote: > > > Hi Bean, > > > > > > On 2021-01-06 02:38, Bean Huo wrote: > > > > On Tue,

Re: [PATCH] clk: imx: fix Kconfig warning for i.MX SCU clk

On Wed, Dec 30, 2020 at 04:52:25PM +0100, Arnd Bergmann wrote: > From: Arnd Bergmann > > A previous patch introduced a harmless randconfig warning: > > WARNING: unmet direct dependencies detected for MXC_CLK_SCU > Depends on [n]: COMMON_CLK [=y] && ARCH_MXC [=n] && IMX_SCU [=y] && >

Re: Old platforms: bring out your dead

Hi Arnd, On Sat, 9 Jan 2021 at 07:56, Arnd Bergmann wrote: > * 68000/68328 (Dragonball): these are less capable than the > 68020+ or the Coldfire MCF5xxx line and similar to the 68360 > that was removed in 2016. I have some patches for the DragonBall series to enable SPI etc there, some

[PATCH v2] ext4: Change list_for_each* to list_for_each_entry*

In the fast_commit.c, list_for_each* + list_entry can be changed to list_for_each_entry*. It reduces number of variables and lines. Signed-off-by: Daejun Park --- fs/ext4/fast_commit.c | 29 +++-- 1 file changed, 11 insertions(+), 18 deletions(-) diff --git

Re: [PATCH] ARM: imx: fix imx8m dependencies

On Wed, Dec 30, 2020 at 04:17:51PM +0100, Arnd Bergmann wrote: > From: Arnd Bergmann > > Selecting ARM_GIC_V3 on non-CP15 processors leads to build failures > like > > arch/arm/include/asm/arch_gicv3.h: In function 'write_ICC_AP1R3_EL1': > arch/arm/include/asm/arch_gicv3.h:36:40: error: 'c12'

Re: [PATCH 2/2] arm64: dts: freescale: sl28: add variant 1

On Tue, Dec 29, 2020 at 01:03:21PM +0100, Michael Walle wrote: > There is a new variant 1 of this board available. It features up to four > SerDes lanes for customer use. Add a new device tree which features just > the basic peripherals. A customer will then have to modify or append to > this

Re: [PATCH 2/2] scsi: ufs: Protect PM ops and err_handler from user access through sysfs

On 2021-01-11 00:18, Bean Huo wrote: On Sat, 2021-01-02 at 05:59 -0800, Can Guo wrote: + * @shutting_down: flag to check if shutdown has been invoked + * @host_sem: semaphore used to serialize concurrent contexts * @eh_wq: Workqueue that eh_work works on * @eh_work: Worker to handle UFS

Re: [PATCH v5 mips-next 5/9] MIPS: vmlinux.lds.S: explicitly catch .rel.dyn symbols

On Sun, Jan 10, 2021 at 11:56:34AM +, Alexander Lobakin wrote: > According to linker warnings, both GCC and LLVM generate '.rel.dyn' > symbols: > > mips-alpine-linux-musl-ld: warning: orphan section `.rel.dyn' > from `init/main.o' being placed in section `.rel.dyn' > > Link-time assertion

Re: [PATCH 2/2] scsi: ufs: Protect PM ops and err_handler from user access through sysfs

On 2021-01-11 00:13, Bean Huo wrote: On Sat, 2021-01-09 at 12:51 +0800, Can Guo wrote: On 2021-01-09 12:45, Can Guo wrote: > On 2021-01-08 19:29, Bean Huo wrote: > > On Wed, 2021-01-06 at 09:20 +0800, Can Guo wrote: > > > Hi Bean, > > > > > > On 2021-01-06 02:38, Bean Huo wrote: > > > > On Tue,

Re: [PATCH 0/1] mm: restore full accuracy in COW page reuse

On Sun, Jan 10, 2021 at 11:30:57AM -0800, Linus Torvalds wrote: > Notice how this is all both conceptually fairly simple (ie I can > explain the rules in plain English without really making any complex > argument) and it is arguably internally fairly self-consistent (ie the > whole notion of "oh,

Re: [PATCH 0/7] arm64: dts: fsl: use the new clockgen constants

On Tue, Dec 29, 2020 at 12:47:33PM +0100, Michael Walle wrote: > Since commit 4cb15934ba05 ("clk: qoriq: provide constants for the type") > there are constants for better readabilty. This series will use them for > all arm64 device trees. > > This is just a mechanical change. The change was done

RE: Re: [PATCH] ext4: Change list_for_each to list_for_each_entry

Hi Harshad, > > > list_for_each + list_entry can be changed to list_for_each_entry > > > It reduces number of variables and lines. > > > > > > Signed-off-by: Daejun Park > > > --- > > > fs/ext4/fast_commit.c | 7 ++- > > > 1 file changed, 2 insertions(+), 5 deletions(-) > > > > > > diff

linux-next: build warning after merge of the spi tree

Hi all, After merging the spi tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/kernel.h:14, from include/linux/clk.h:13, from drivers/spi/spi-cadence-quadspi.c:9: drivers/spi/spi-cadence-quadspi.c:

[PATCH] rcu: remove surplus instrumentation_end in rcu_nmi_enter

In function rcu_nmi_enter, there is a surplus instrumentation_end in second branch of if statement, although objtool check -f vmlinux.o will not complain because of its inability to correctly cover all cases (objtool will visit the third branch first, which markes following trace_rcu_dyntick as

Re: [RFC PATCH 5/8] entry: Explicitly flush pending rcuog wakeup before last rescheduling points

On Sat, Jan 09, 2021 at 03:05:33AM +0100, Frederic Weisbecker wrote: > Following the idle loop model, cleanly check for pending rcuog wakeup > before the last rescheduling point on resuming to user mode. This > way we can avoid to do it from rcu_user_enter() with the last resort > self-IPI hack

Re: [v5 3/3] thermal: mediatek: add another get_temp ops for thermal sensors

On Tue, Oct 13, 2020 at 6:24 PM Michael Kao wrote: > > Provide thermal zone to read thermal sensor > in the SoC. We can read all the thermal sensors > value in the SoC by the node /sys/class/thermal/ > > In mtk_thermal_bank_temperature, return -EAGAIN instead of -EACCESS > on the first read of

Re: Old platforms: bring out your dead

On Sun, Jan 10, 2021 at 10:33:56PM +0100, Linus Walleij wrote: > On Sun, Jan 10, 2021 at 7:16 PM Fabian Vogt wrote: > > Am Samstag, 9. Januar 2021, 23:20:48 CET schrieb Arnd Bergmann: > > > On Sat, Jan 9, 2021 at 1:06 AM Daniel Tang wrote: > > > > > * nspire -- added in 2013, no notable changes

Re: [PATCH v2 2/4] arm64: dts: imx8mq-librem5: add pinctrl for the touchscreen description

On Tue, Dec 22, 2020 at 04:13:45PM +0100, Martin Kepplinger wrote: > In order for the touchscreen interrupt line to work, describe it properly. > Otherwise it can work if defaults are ok, but we cannot be sure. > > Fixes: 8f0216b006e5 ("arm64: dts: Add a device tree for the Librem 5 phone") >

Re: [PATCH v2] arm64: dts: imx8mq: Add clock parents for mipi dphy

On Sun, Jan 10, 2021 at 05:55:51PM +0100, Guido Günther wrote: > This makes sure the clock tree setup for the dphy is not dependent on > other components. > > Without this change bringing up the display can fail like > > kernel: phy phy-30a00300.dphy.2: Invalid CM/CN/CO values: 165/217/1 >

Re: [PATCH v3 1/4] arm64: defconfig: Enable Librem 5 devkit components

On Fri, Jan 08, 2021 at 01:57:07PM +0100, Guido Günther wrote: > The Librem 5 devkit is based on NXP's i.MX8MQ. Schematics are at > https://source.puri.sm/Librem5/dvk-mx8m-bsb. > > This enables drivers for the following hardware components that aren't > yet enabled in defconfig: > > - Goodix

Re: Expense of read_iter

On Sun, Jan 10, 2021 at 04:19:15PM -0500, Mikulas Patocka wrote: > I put counters into vfs_read and vfs_readv. > > After a fresh boot of the virtual machine, the counters show "13385 4". > After a kernel compilation they show "4475220 8". > > So, the readv path is almost unused. > > My

Re: [PATCH] mm: vmscan: support complete shrinker reclaim

On Wed, Jan 06, 2021 at 03:56:02PM -0800, Andrew Morton wrote: > (cc's added) > > On Tue, 5 Jan 2021 16:43:38 -0800 Sudarshan Rajagopalan > wrote: > > > Ensure that shrinkers are given the option to completely drop > > their caches even when their caches are smaller than the batch size. > >

Re: [PATCH v6 4/6] mmc: sdhci-of-aspeed: Add KUnit tests for phase calculations

On Wed, 6 Jan 2021, at 00:17, Adrian Hunter wrote: > On 18/12/20 5:53 am, Andrew Jeffery wrote: > > Converting degrees of phase to logic delays is irritating to test on > > hardware, so lets exercise the function using KUnit. > > > > Signed-off-by: Andrew Jeffery > > --- > >

Re: linux-next: build failure after merge of the drm tree

Hi all, On Fri, 8 Jan 2021 12:25:40 +1100 Stephen Rothwell wrote: > > On Fri, 8 Jan 2021 11:55:18 +1100 Stephen Rothwell > wrote: > > > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > error: the following would cause module name

Re: [PATCH v1] drm/panel: simple: add SGD GKTW70SDAD1SD

On Sun, Jan 10, 2021 at 5:09 PM Oliver Graute wrote: > here the schematics and my dts. The board is using a LVDS connector for > the display. The schematics shows the GKTW70SDAD1SD panel in the J4 connector, not the LVDS J7 connector. >

Re: [RFC v2] nvfs: a filesystem for persistent memory

On Sun, Jan 10, 2021 at 04:14:55PM -0500, Mikulas Patocka wrote: > That's a good point. I split nvfs_rw_iter to separate functions > nvfs_read_iter and nvfs_write_iter - and inlined nvfs_rw_iter_locked into > both of them. It improved performance by 1.3%. > > > Not that it had been more useful

Re: linux-next: build warning after merge of the f2fs tree

On Mon, 11 Jan 2021 07:33:54 +1100 Stephen Rothwell wrote: > On Thu, 7 Jan 2021 19:28:19 +0800 Chao Yu wrote: > > > > On 2021/1/7 11:11, Stephen Rothwell wrote: > > > > > > After merging the f2fs tree, today's linux-next build (htmldocs) produced > > > this warning: > > > > > >

WARNING in input_mt_init_slots

Hello, syzbot found the following issue on: HEAD commit:f5e6c330 Merge tag 'spi-fix-v5.11-rc2' of git://git.kernel.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=121ca75750 kernel config: https://syzkaller.appspot.com/x/.config?x=8aa30b9da402d224

[PATCH 1/3] dt-bindings: arm: imx: add imx8mm nitrogen support

The Nitrogen8M Mini is an ARM based single board computer (SBC). Signed-off-by: Adrien Grassein --- Documentation/devicetree/bindings/arm/fsl.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml

[PATCH 3/3] arm64: defconfig: Enable PF8x00 as builtin

This driver is mandatory for the nitrogen8m mini board when booting from the sdcard slot. Signed-off-by: Adrien Grassein --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index

[PATCH 2/3] arm64: dts: imx: Add i.mx8mm nitrogen8mm basic dts support

Tested with a basic Build Root configuration booting from sdcard. Signed-off-by: Adrien Grassein --- arch/arm64/boot/dts/freescale/Makefile| 1 + .../dts/freescale/imx8mm-nitrogen8mm_rev2.dts | 657 ++ 2 files changed, 658 insertions(+) create mode 100644

[PATCH 0/3] Add support for Boundary Nitrogen8M Mini SBC

Hello, This patch set aims is to add the support of the Nitrogen8M Mini SBC from Boundary Devices. Thanks, Adrien Grassein (3): dt-bindings: arm: imx: add imx8mm nitrogen support arm64: dts: imx: Add i.mx8mm nitrogen8mm basic dts support arm64: defconfig: Enable PF8x00 as builtin

[PATCH 01/17] rtc: introduce features bitfield

Introduce a bitfield to allow the drivers to announce the available features for an RTC. The main use case would be to better handle alarms, that could be present or not or have a minute resolution or may need a correct week day to be set. Use the newly introduced RTC_FEATURE_ALARM bit to then

[PATCH 12/17] rtc: opal: constify opal_rtc_ops

Use RTC_FEATURE_ALARM to signal to the core whether alarms are available instead of changing the global struct rtc_class_ops, allowing to make it const. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-opal.c | 13 +++-- 1 file changed, 7 insertions(+), 6 deletions(-) diff --git

[PATCH 14/17] rtc: rv3029: constify rv3029_rtc_ops

Use RTC_FEATURE_ALARM to signal to the core whether alarms are available instead of changing the global struct rtc_class_ops, allowing to make it const. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-rv3029c2.c | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git

[PATCH 17/17] rtc: tps65910: remove tps65910_rtc_ops_noirq

Clear RTC_FEATURE_ALARM to signal that alarms are not available instead of having a supplementary struct rtc_class_ops without alarm callbacks. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-tps65910.c | 15 --- 1 file changed, 4 insertions(+), 11 deletions(-) diff --git

[PATCH 15/17] rtc: rv3032: constify rv3032_rtc_ops

Use RTC_FEATURE_ALARM to signal to the core whether alarms are available instead of changing the global struct rtc_class_ops, allowing to make it const. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-rv3032.c | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git

[PATCH 16/17] rtc: rv8803: constify rv8803_rtc_ops

Use RTC_FEATURE_ALARM to signal to the core whether alarms are available instead of changing the global struct rtc_class_ops, allowing to make it const. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-rv8803.c | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git

[PATCH 11/17] rtc: m41t80: constify m41t80_rtc_ops

Use RTC_FEATURE_ALARM to signal to the core whether alarms are available instead of changing the global struct rtc_class_ops, allowing to make it const. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-m41t80.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git

[PATCH 09/17] rtc: rx8010: drop a struct rtc_class_ops

Merge both struct rtc_class_ops in a single one and use RTC_FEATURE_ALARM to signal to the core whether alarms are available. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-rx8010.c | 13 +++-- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/drivers/rtc/rtc-rx8010.c

[PATCH 08/17] rtc: pcf85063: remove pcf85063_rtc_ops_alarm

Move the alarm callbacks in pcf85063_rtc_ops and use RTC_FEATURE_ALARM to signal to the core whether alarms are available instead of having a supplementary struct rtc_class_ops without alarm callbacks. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-pcf85063.c | 11 ++- 1 file

[PATCH 10/17] rtc: pcf85363: drop a struct rtc_class_ops

Merge both struct rtc_class_ops in a single one and use RTC_FEATURE_ALARM to signal to the core whether alarms are available. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-pcf85363.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/rtc/rtc-pcf85363.c

[PATCH 13/17] rtc: rv3028: constify rv3028_rtc_ops

Use RTC_FEATURE_ALARM to signal to the core whether alarms are available instead of changing the global struct rtc_class_ops, allowing to make it const. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-rv3028.c | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git

[PATCH 06/17] rtc: m48t59: remove m48t02_rtc_ops

Clear RTC_FEATURE_ALARM to signal that alarms are not available instead of having a supplementary struct rtc_class_ops without alarm callbacks. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-m48t59.c | 22 -- 1 file changed, 8 insertions(+), 14 deletions(-) diff --git

[PATCH 07/17] rtc: pcf2127: remove pcf2127_rtc_alrm_ops

Move the alarm callbacks in pcf2127_rtc_ops and use RTC_FEATURE_ALARM to signal to the core whether alarms are available instead of having a supplementary struct rtc_class_ops without alarm callbacks. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-pcf2127.c | 11 +++ 1 file

[PATCH 02/17] rtc: pl031: use RTC_FEATURE_ALARM

Clear RTC_FEATURE_ALARM instead of setting set_alarm, read_alarm and alarm_irq_enable to NULL. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-pl031.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/rtc/rtc-pl031.c b/drivers/rtc/rtc-pl031.c index

<    1   2   3   4   5   6   >