Re: [PATCH 4.14 105/136] usb/ehci-platform: Set PM runtime as active on resume

Hello everyone, Cc: linux-renesas-soc Cc: linux-pm On Tue, Jun 23, 2020 at 09:59:21PM +0200, Greg Kroah-Hartman wrote: > From: Qais Yousef > > [ Upstream commit 16bdc04cc98ab0c74392ceef2475ecc5e73fcf49 ] > > Follow suit of ohci-platform.c and perform pm_runtime_set_active() on > resume. > > o

Re: [PATCH 0/9] timer: Reduce timers softirq v2

Hi, On 07/07/20 03:32, Frederic Weisbecker wrote: > Hi, > > No huge change here, just addressed reviews and fixed warnings: > > * Reposted patch 1 separately with appropriate "Fixes:" tag and stable Cc'ed: > https://lore.kernel.org/lkml/20200703010657.2302-1-frede...@kernel.org/ > > * Fix mis

RE: [PATCH v2 0/2] Add support to get/set PHY attributes using PHY framework

Ping requesting review comments. https://lkml.org/lkml/2020/5/26/507 Thanks & regards, Swapnil > -Original Message- > From: Yuti Amonkar > Sent: Tuesday, May 26, 2020 8:05 PM > To: linux-kernel@vger.kernel.org; kis...@ti.com; robh...@kernel.org; > mark.rutl...@arm.com; max...@cerno.tech

Re: [PATCH v4 04/11] mm/hugetlb: make hugetlb migration callback CMA aware

2020년 7월 9일 (목) 오후 3:43, Michal Hocko 님이 작성: > > On Wed 08-07-20 09:41:06, Michal Hocko wrote: > > On Wed 08-07-20 16:16:02, Joonsoo Kim wrote: > > > On Tue, Jul 07, 2020 at 01:22:31PM +0200, Vlastimil Babka wrote: > > > > On 7/7/20 9:44 AM, js1...@gmail.com wrote: > > > > > From: Joonsoo Kim > >

Re: [PATCH v4 0/4] printk: replace ringbuffer

On 2020-07-08, Petr Mladek wrote: > OK, I think that we are ready to try this in linux-next. > I am going to push it there via printk/linux.git. > > [...] > > Of course, there are still many potential problems. The following comes > to my mind: > > [...] > >+ Debugging tools accessing the buf

Re: [V2 PATCH] usb: mtu3: fix NULL pointer dereference

On Thu, 2020-07-09 at 09:40 +0300, Felipe Balbi wrote: > Chunfeng Yun writes: > > > Some pointers are dereferenced before successful checks. > > > > Reported-by: Markus Elfring > > Signed-off-by: Chunfeng Yun > > do you need a Fixes tag here? Perhaps a Cc stable too? It will not cause somes is

Re: [PATCH v2 3/3] misc: cxl: flash: Remove unused variable 'drc_index'

On 9/7/20 4:56 pm, Lee Jones wrote: Keeping the pointer increment though. Fixes the following W=1 kernel build warning: drivers/misc/cxl/flash.c: In function ‘update_devicetree’: drivers/misc/cxl/flash.c:178:16: warning: variable ‘drc_index’ set but not used [-Wunused-but-set-variable] 1

[PATCH] EDAC-GHES: Replace HTTP links with HTTPS ones

Rationale: Reduces attack surface on kernel devs opening the links for MITM as HTTPS traffic is much harder to manipulate. Deterministic algorithm: For each file: If not .svg: For each line: If doesn't contain `\bxmlns\b`: For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:

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

On Thu, Jul 09, 2020 at 09:54:12AM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the scmi tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > drivers/firmware/arm_scmi/clock.c: In function 'rate_cmp_func': > drivers/firmware/arm_scmi/clock.c:128:12: warn

Re: [PATCH] drm/aspeed: Call drm_fbdev_generic_setup after drm_dev_register

Am 09.07.20 um 08:51 schrieb Joel Stanley: > On Wed, 1 Jul 2020 at 09:10, Sam Ravnborg wrote: >> >> Hi Guenter. >> >> On Tue, Jun 30, 2020 at 05:10:02PM -0700, Guenter Roeck wrote: >>> The following backtrace is seen when running aspeed G5 kernels. >>> >>> WARNING: CPU: 0 PID: 1 at drivers/gpu/d

[v3 PATCH] usb: mtu3: remove unnecessary NULL pointer checks

The class driver will ensure the parameters are not NULL pointers before call the hook function of usb_ep_ops, so no need check them again. Reported-by: Markus Elfring Signed-off-by: Chunfeng Yun --- v3: remove unnecessary NULL pointer checks but not add more checks. v2: nothing changed, but ab

[PATCH v3 1/4] iommu/vt-d: Refactor device_to_iommu() helper

It is refactored in two ways: - Make it global so that it could be used in other files. - Make bus/devfn optional so that callers could ignore these two returned values when they only want to get the coresponding iommu pointer. Signed-off-by: Lu Baolu Reviewed-by: Kevin Tian --- drivers/iommu

[PATCH v3 0/4] iommu/vt-d: Add prq report and response support

Hi, This series adds page request event reporting and response support to the Intel IOMMU driver. This is necessary when the page requests must be processed by any component other than the vendor IOMMU driver. For example, when a guest page table was bound to a PASID through the iommu_ops->sva_bin

[PATCH v3 2/4] iommu/vt-d: Add a helper to get svm and sdev for pasid

There are several places in the code that need to get the pointers of svm and sdev according to a pasid and device. Add a helper to achieve this for code consolidation and readability. Signed-off-by: Lu Baolu Reviewed-by: Kevin Tian --- drivers/iommu/intel/svm.c | 121 +-

[PATCH v3 4/4] iommu/vt-d: Add page response ops support

After page requests are handled, software must respond to the device which raised the page request with the result. This is done through the iommu ops.page_response if the request was reported to outside of vendor iommu driver through iommu_report_device_fault(). This adds the VT-d implementation o

[PATCH v3 3/4] iommu/vt-d: Report page request faults for guest SVA

A pasid might be bound to a page table from a VM guest via the iommu ops.sva_bind_gpasid. In this case, when a DMA page fault is detected on the physical IOMMU, we need to inject the page fault request into the guest. After the guest completes handling the page fault, a page response need to be sen

Re: [f2fs-dev] [PATCH] f2fs: don't skip writeback of quota data

On 2020/7/9 13:30, Jaegeuk Kim wrote: > It doesn't need to bypass flushing quota data in background. The condition is used to flush quota data in batch to avoid random small-sized udpate, did you hit any problem here? Thanks, > > Signed-off-by: Jaegeuk Kim > --- > fs/f2fs/data.c | 2 +- > 1 f

Re: [PATCH 5/6] phy: exynos5-usbdrd: use correct format for structure description

On 08.07.2020 15:28, Vinod Koul wrote: > We get warning with W=1 build: > drivers/phy/samsung/phy-exynos5-usbdrd.c:211: warning: Function > parameter or member 'phys' not described in 'exynos5_usbdrd_phy' > drivers/phy/samsung/phy-exynos5-usbdrd.c:211: warning: Function > parameter or member 'vbu

Re: [Proposal] DRM: AMD: Convert logging to drm_* functions.

Am 08.07.20 um 18:11 schrieb Suraj Upadhyay: Hii AMD Maintainers, I plan to convert logging of information, error and warnings inside the AMD driver(s) to drm_* functions and macros for loggin, as described by the TODO list in the DRM documentation[1]. I need your approval for the change

Re: [PATCH v4 06/11] mm/migrate: make a standard migration target allocation function

2020년 7월 8일 (수) 오전 4:00, Michal Hocko 님이 작성: > > On Tue 07-07-20 16:49:51, Vlastimil Babka wrote: > > On 7/7/20 9:44 AM, js1...@gmail.com wrote: > > > From: Joonsoo Kim > > > > > > There are some similar functions for migration target allocation. Since > > > there is no fundamental difference, it

RE: [PATCH v3 06/14] vfio/type1: Add VFIO_IOMMU_PASID_REQUEST (alloc/free)

Hi Alex, After more thinking, looks like adding a r-b tree is still not enough to solve the potential problem for free a range of PASID in one ioctl. If caller gives [0, MAX_UNIT] in the free request, kernel anyhow should loop all the PASIDs and search in the r-b tree. Even VFIO can track the smal

Re: [PATCH v4 05/11] mm/migrate: clear __GFP_RECLAIM for THP allocation for migration

2020년 7월 7일 (화) 오후 9:17, Vlastimil Babka 님이 작성: > > On 7/7/20 9:44 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > In mm/migrate.c, THP allocation for migration is called with the provided > > gfp_mask | GFP_TRANSHUGE. This gfp_mask contains __GFP_RECLAIM and it > > would be conflict wit

Re: [PATCH v4] mm/zswap: move to use crypto_acomp API for hardware acceleration

On 2020-07-08 21:45:47 [+], Song Bao Hua (Barry Song) wrote: > > On 2020-07-08 00:52:10 [+1200], Barry Song wrote: > > > @@ -127,9 +129,17 @@ > > > +struct crypto_acomp_ctx { > > > + struct crypto_acomp *acomp; > > > + struct acomp_req *req; > > > + struct crypto_wait wait; > > > + u8 *dstmem;

Re:[PATCH] arm64/module-plts: Consider the special case where plt_max_entries is 0

On Thu, 9 Jul 2020 at 09:50, 彭浩(Richard) wrote: >> >Apparently, you are hitting a R_AARCH64_JUMP26 or R_AARCH64_CALL26 >> >relocation that operates on a b or bl instruction that is more than >> >128 megabytes away from its target. >> > >> My understanding is that a module that calls functions that

Re: [PATCH] bfq: fix blkio cgroup leakage

> Il giorno 8 lug 2020, alle ore 19:48, Dmitry Monakhov > ha scritto: > > Paolo Valente writes: > >> Hi, >> sorry for the delay. The commit you propose to drop fix the issues >> reported in [1]. >> >> Such a commit does introduce the leak that you report (thank you for >> spotting it). Y

Re: [PATCH] Replace HTTP links with HTTPS ones: PWM SUBSYSTEM

On Wed, Jul 08, 2020 at 07:59:24PM +0200, Alexander A. Klimov wrote: > Rationale: > Reduces attack surface on kernel devs opening the links for MITM > as HTTPS traffic is much harder to manipulate. > > Deterministic algorithm: > For each file: > If not .svg: > For each line: > If doesn

Re: [PATCH] scsi: fcoe: add missed kfree() in an error path

>>> fcoe_fdmi_info() misses to call kfree() in an error path. >>> Add the missed function call to fix it. >> >> I suggest to use an additional jump target for the completion >> of the desired exception handling. >> >> >> … >>> +++ b/drivers/scsi/fcoe/fcoe.c >>> @@ -830,6 +830,7 @@ static void fcoe_

Re: [Ksummit-discuss] [PATCH v3] CodingStyle: Inclusive Terminology

On Wed, Jul 8, 2020 at 8:30 PM Dan Williams wrote: > > Linux maintains a coding-style and its own idiomatic set of terminology. > Update the style guidelines to recommend replacements for the terms > master/slave and blacklist/whitelist. > > Link: > http://lore.kernel.org/r/159389297140.2210796.1

Re: [PATCH v1] platform/chrome: cros_ec_debugfs: conditionally create uptime node

Hi Eizan, Thank you for your patch On 8/7/20 6:53, Eizan Miyamoto wrote: > Before creating an 'uptime' node in debugfs, this change adds a check to > see if a EC_CMD_GET_UPTIME_INFO command can be successfully run. > > If the uptime node is created, userspace programs may periodically poll > it

[PATCH] PCI: Replace kmalloc with kzalloc in the comment/message

From: Liao Pingfang Use kzalloc instead of kmalloc in the comment/message according to the previous kzalloc() call. Signed-off-by: Liao Pingfang Signed-off-by: Yi Wang --- drivers/pci/hotplug/ibmphp_pci.c | 2 +- drivers/pci/setup-bus.c | 2 +- 2 files changed, 2 insertions(+), 2 del

[PATCH v3 1/4] iomap: Constify ioreadX() iomem argument (as in generic implementation)

The ioreadX() and ioreadX_rep() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and

[PATCH] TI DAVINCI SERIES MEDIA DRIVER: Replace HTTP links with HTTPS ones

Rationale: Reduces attack surface on kernel devs opening the links for MITM as HTTPS traffic is much harder to manipulate. Deterministic algorithm: For each file: If not .svg: For each line: If doesn't contain `\bxmlns\b`: For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:

[PATCH v3 0/4] iomap: Constify ioreadX() iomem argument

Hi, Multiple architectures are affected in the first patch and all further patches depend on the first. Maybe this could go in through Andrew Morton's tree? Changes since v2 1. Drop all non-essential patches (cleanups), 2. Update also drivers/sh/clk/cpg.c . Changes since v1 =

[PATCH v3 2/4] rtl818x: Constify ioreadX() iomem argument (as in generic implementation)

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among

[PATCH v3 3/4] ntb: intel: Constify ioreadX() iomem argument (as in generic implementation)

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among

Re: [Intel-gfx] [PATCH 03/18] dma-fence: basic lockdep annotations

Hi, Jumping in after a couple of weeks where I've paged most everything out of my brain ... On Fri, 19 Jun 2020 at 10:43, Daniel Vetter wrote: > On Fri, Jun 19, 2020 at 10:13:35AM +0100, Chris Wilson wrote: > > > The proposed patches might very well encode the wrong contract, that's > > > all up

[PATCH v2 1/2] riscv: Add STACKPROTECTOR supported

From: Guo Ren The -fstack-protector & -fstack-protector-strong features are from gcc. The patch only add basic kernel support to stack-protector feature and some arch could have its own solution such as ARM64_PTR_AUTH. After enabling STACKPROTECTOR and STACKPROTECTOR_STRONG, the .text size is ex

[PATCH v3 4/4] virtio: pci: Constify ioreadX() iomem argument (as in generic implementation)

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among

[PATCH v2 2/2] riscv: Enable per-task stack canaries

From: Guo Ren This enables the use of per-task stack canary values if GCC has support for emitting the stack canary reference relative to the value of tp, which holds the task struct pointer in the riscv kernel. After compare arm64 and x86 implementations, seems arm64's is more flexible and read

Re: [PATCH] spi: spi-geni-qcom: Set the clock properly at runtime resume

Hi Doug, @@ -670,7 +674,13 @@ static int __maybe_unused spi_geni_runtime_resume(struct device *dev) if (ret) return ret; - return geni_se_resources_on(&mas->se); + ret = geni_se_resources_on(&mas->se); + if (ret) + return ret; + + de

Re: [PATCH] arm64/module-plts: Consider the special case where plt_max_entries is 0

On Thu, Jul 09, 2020 at 07:18:01AM +, 彭浩(Richard) wrote: > On Thu, 9 Jul 2020 at 09:50, 彭浩(Richard) wrote: > >> >Apparently, you are hitting a R_AARCH64_JUMP26 or R_AARCH64_CALL26 > >> >relocation that operates on a b or bl instruction that is more than > >> >128 megabytes away from its target

Re: [PATCH 4/5] iommu/arm-smmu-qcom: Consstently initialize stream mappings

On 08-07-20, 22:01, Bjorn Andersson wrote: > Firmware that traps writes to S2CR to translate BYPASS into FAULT also > ignores writes of type FAULT. As such booting with "disable_bypass" set > will result in all S2CR registers left as configured by the bootloader. > > This has been seen to result i

Re: [PATCH v3 1/4] iomap: Constify ioreadX() iomem argument (as in generic implementation)

On Thu, Jul 09, 2020 at 09:28:34AM +0200, Krzysztof Kozlowski wrote: > The ioreadX() and ioreadX_rep() helpers have inconsistent interface. On > some architectures void *__iomem address argument is a pointer to const, > on some not. > > Implementations of ioreadX() do not modify the memory under

Re: [PATCH 0/5] iommu/arm-smmu: Support maintaining bootloader mappings

On 08-07-20, 22:01, Bjorn Andersson wrote: > Based on previous attempts and discussions this is the latest attempt at > inheriting stream mappings set up by the bootloader, for e.g. boot splash or > efifb. > > The first patch is an implementation of Robin's suggestion that we should just > mark th

Re: [PATCH] drm/vc4: dsi: Only register our component once a DSI device is attached

Hi Eric, On Tue, Jul 07, 2020 at 09:48:45AM -0700, Eric Anholt wrote: > On Tue, Jul 7, 2020 at 3:26 AM Maxime Ripard wrote: > > > > If the DSI driver is the last to probe, component_add will try to run all > > the bind callbacks straight away and return the error code. > > > > However, since we d

Re: [PATCH v2 2/3] media: rockchip: Introduce driver for Rockhip's camera interface

Hi Ezequiel, Sorry for the late reply, some answers to your very useful comments below :) On Sun, 31 May 2020 10:40:14 -0300 Ezequiel Garcia wrote: >Hi Maxime, > >Thanks for posting this patch. I think you can still improve it, >but it's a neat first try! :-) > >On Fri, 29 May 2020 at 10:05, Ma

Re: [PATCH v4 11/18] nitro_enclaves: Add logic for enclave memory region set

On 06/07/2020 13:46, Alexander Graf wrote: On 22.06.20 22:03, Andra Paraschiv wrote: Another resource that is being set for an enclave is memory. User space memory regions, that need to be backed by contiguous memory regions, are associated with the enclave. One solution for allocating / r

Re: [PATCH v4] mm/zswap: move to use crypto_acomp API for hardware acceleration

On 2020-07-09 01:32:38 [+], Song Bao Hua (Barry Song) wrote: > > This looks using the same synchronous mechanism around an asynchronous > > interface. It works as a PoC. > > > > As far as I remember the crypto async interface, the incoming skbs were fed > > to > > the async interface and retu

Re: [PATCH v2 0/2] Add support to get/set PHY attributes using PHY framework

On 09-07-20, 07:02, Swapnil Kashinath Jakhade wrote: > Ping requesting review comments. > https://lkml.org/lkml/2020/5/26/507 I dont have this, can you repost? Thanks > > Thanks & regards, > Swapnil > > > -Original Message- > > From: Yuti Amonkar > > Sent: Tuesday, May 26, 2020 8:05 PM

Re: [PATCH 2/2] doc, mm: clarify /proc//oom_score value range

On Thu, Jul 9, 2020 at 2:26 PM Michal Hocko wrote: > > From: Michal Hocko > > The exported value includes oom_score_adj so the range is no [0, 1000] > as described in the previous section but rather [0, 2000]. Mention that > fact explicitly. > > Signed-off-by: Michal Hocko > --- > Documentation

RE: [PATCH v5 0/5] scsi: ufs: Add Host Performance Booster Support

> Hello, > > > > Just a gentle reminder that I'd like some feedback. > > Any suggestions here? > If no-one objects, I think you can submit your patches for review as non-RFC. > [PATCH v5 0/5] scsi: ufs: Add Host Performance Booster Support ~~ It is non-RFC version. Thanks, Daejun.

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

Hi, Browm, Stephen Firstly, feel sorry for the problem introduced by me. I think I must modify my bad,but should I send another patch to delete the label "out_free" or re-send patch of v2(which maybe need to go back)? Could you give me some advices? Sorry again. Thanks "Peng Fan"

RE: [PATCH v4 1/2] dt-bindings: dma: Add bindings for intel LGM SOC

> -Original Message- > From: devicetree-ow...@vger.kernel.org ow...@vger.kernel.org> On Behalf Of Amireddy Mallikarjuna reddy > Sent: Donnerstag, 9. Juli 2020 08:01 > To: dmaeng...@vger.kernel.org; vk...@kernel.org; > devicet...@vger.kernel.org; robh...@kernel.org > Cc: linux-kernel@vger

RE: [PATCH v4] mm/zswap: move to use crypto_acomp API for hardware acceleration

> -Original Message- > From: linux-crypto-ow...@vger.kernel.org > [mailto:linux-crypto-ow...@vger.kernel.org] On Behalf Of Sebastian Andrzej > Siewior > Sent: Thursday, July 9, 2020 7:39 PM > To: Song Bao Hua (Barry Song) > Cc: a...@linux-foundation.org; herb...@gondor.apana.org.au; > da

Re: [PATCH v2] drm/bridge: dw-mipi-dsi.c: Add VPG runtime config through debugfs

On 7/8/20 7:08 PM, Angelo Ribeiro wrote: > Hi, > > Is this patch good to go? > @dan...@ffwll.ch, @Philippe CORNU > > Was already tested by @Yannick FERTRE > and @Adrian Pop > on https://lkml.org/lkml/2020/4/6/691 . > > Thanks, > Angelo > > From: Yannick > FERTRE > Date: Wed, Jun 24, 2020 at 1

Re: [PATCH 0/6] crypto: hisilicon/hpre bugfix - misc fixes

On Thu, Jul 02, 2020 at 10:31:13AM +0800, Meng Yu wrote: > Bugfix: crypto: hisilicon/hpre - modify the macros, add a switch in > sriov_configure, unified debugfs interface, and disable > hardware FLR. > > Hui Tang (2): > crypto: hisilicon/hpre - HPRE_OVERTIME_THRHLD can be written by

linux-next: manual merge of the akpm-current tree with the userns tree

Hi all, Today's linux-next merge of the akpm-current tree got a conflict in: fs/exec.c between commit: 25cf336de51b ("exec: Remove do_execve_file") from the userns tree and commit: 538d50d50815 ("umh: fix refcount underflow in fork_usermode_blob().") from the akpm-current tree. I fixe

Re: [PATCH] riscv: Enable ELF-ASLR for riscv

On Thu, Jul 9, 2020 at 1:32 PM Alex Ghiti wrote: > > Hi Guo, > > Le 7/9/20 à 12:38 AM, guo...@kernel.org a écrit : > > From: Guo Ren > > > > Let riscv enable randomizes the stack, heap and binary images of > > ELF binaries. Seems it's ok at all after qemu & chip test and > > there is no founded s

Re: [Intel-gfx] [PATCH 03/18] dma-fence: basic lockdep annotations

On Thu, Jul 09, 2020 at 08:29:21AM +0100, Daniel Stone wrote: > Hi, > Jumping in after a couple of weeks where I've paged most everything > out of my brain ... > > On Fri, 19 Jun 2020 at 10:43, Daniel Vetter wrote: > > On Fri, Jun 19, 2020 at 10:13:35AM +0100, Chris Wilson wrote: > > > > The prop

[PATCH 4/4] MAINTAINERS: Add Silvaco I3C master

Add Conor and myself as maintainers. Signed-off-by: Miquel Raynal --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 496fd4eafb68..7e44a06fd5da 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -15587,6 +15587,14 @@ S: Maintained F: D

[PATCH v4] HID: i2c-hid: Enable wakeup capability from Suspend-to-Idle

Many laptops can be woken up from Suspend-to-Idle by touchpad. This is also the default behavior on other OSes. However, if touchpad and touchscreen contact to each other when lid is closed, wakeup events can be triggered inadventertly. So let's disable the wakeup by default, but enable the wakeu

[PATCH 2/4] dt-bindings: i3c: Describe Silvaco master binding

Silvaco provide a dual-role I3C master. Description is rather simple: it needs a register mapping, three clocks and an interrupt. Signed-off-by: Miquel Raynal --- .../bindings/i3c/svc,i3c-master.yaml | 59 +++ 1 file changed, 59 insertions(+) create mode 100644 Documen

[PATCH 1/4] dt-bindings: Add vendor prefix for Silvaco

Silvaco, Inc. is an EDA provider of software tools used for process and device development and for analog/mixed-signal, power IC and memory design [1]. [1] https://www.silvaco.com/company/profile/profile.html Signed-off-by: Miquel Raynal --- Documentation/devicetree/bindings/vendor-prefixes.yam

[PATCH 3/4] i3c: master: svc: Add Silvaco I3C master driver

Add support for Silvaco I3C dual-role IP. The master role is supported in SDR mode only. I2C transfers have not been tested but are shared because they are so close to the I3C transfers in terms of registers configuration. Signed-off-by: Miquel Raynal --- drivers/i3c/master/Kconfig |

[PATCH 1/4] perf-probe: Avoid setting probes on same address on same event

There is a case that the several same-name symbols points same address. In that case, perf probe returns an error. E.g. perf probe -x /lib64/libc-2.30.so -v -a "memcpy arg1=%di" probe-definition(0): memcpy arg1=%di symbol:memcpy file:(null) line:0 offset:0 return:0 lazy:(null) parsing arg

[PATCH 0/4] perf-probe: Fix GNU IFUNC probe issue etc.

Hi, Here are patches to fix some issues of probing on GNU IFUNC, duplicated symbols, and memory leak, which were reported by Andi. Andi reported that some issues on probing memcpy function in glibc, which was related to GNU IFUNC (indirect function). As I described in the patch [4/4], it is hard

[PATCH 2/4] perf-probe: Fix wrong variable warning when the probe point is not found

Fix a wrong "variable not found" warning when the probe point is not found in the debuginfo. Since the debuginfo__find_probes() can return 0 even if it does not find given probe point in the debuginfo, fill_empty_trace_arg() can be called with tf.ntevs == 0 and it can warn a wrong warning. To fix t

[PATCH 4/4] perf-probe: Warn if the target function is GNU Indirect function

Warn if the probe target function is GNU indirect function (GNU_IFUNC) because it may not what the user want to probe. The GNU indirect function ( https://sourceware.org/glibc/wiki/GNU_IFUNC ) is the dynamic solved symbol at runtime. IFUNC function is a selector which is invoked from the elf loade

[PATCH 3/4] perf-probe: Fix memory leakage when the probe point is not found

Fix the memory leakage in debuginfo__find_trace_events() when the probe point is not found in the debuginfo. If there is no probe point found in the debuginfo, debuginfo__find_probes() will NOT return -ENOENT, but 0. Thus the caller of debuginfo__find_probes() must check the tf.ntevs and release th

[PATCH] service_layers: osunixmap: Remove unnecessary brackets in acpi_os_map_memory()

Remove extra brackets. Signed-off-by: Xu Wang --- tools/power/acpi/os_specific/service_layers/osunixmap.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/power/acpi/os_specific/service_layers/osunixmap.c b/tools/power/acpi/os_specific/service_layers/osunixmap.c ind

[RFC PATCH] usb: dwc3: fix maximum_speed check for usb2.0-only core

The maximum_speed will be USB_SPEED_SUPER_PLUS, but the maximum_speed check for usb2.0-only core doesn't consider it, so fix it, and move the ckeck into dwc3_check_params(). Signed-off-by: Chunfeng Yun --- Note: When I look at the code, find that this may be a problem, but no platform to test it

Re: [PATCH] tty/sysrq: Add alternative SysRq key

Hi Dmitry, W dniu 09.07.2020 o 07:05, Dmitry Torokhov pisze: Hi Andrzej, On Fri, Jun 19, 2020 at 06:28:19PM +0200, Andrzej Pietrasiewicz wrote: There exist machines which don't have SysRq key at all, e.g. chromebooks. This patch allows configuring an alternative key to act as SysRq. Devices w

Re: [PATCH v5 1/4] riscv: Move kernel mapping to vmalloc zone

On Thu, Jul 9, 2020 at 1:05 PM Palmer Dabbelt wrote: > > On Sun, 07 Jun 2020 00:59:46 PDT (-0700), a...@ghiti.fr wrote: > > This is a preparatory patch for relocatable kernel. > > > > The kernel used to be linked at PAGE_OFFSET address and used to be loaded > > physically at the beginning of the m

[RESEND PATCH 2/2] fpga: dfl: fix bug in port reset handshake

From: Matthew Gerlach When putting the port in reset, driver must wait for the soft reset acknowledgment bit instead of the soft reset bit. Fixes: 47c1b19c160f (fpga: dfl: afu: add port ops support) Signed-off-by: Matthew Gerlach Signed-off-by: Xu Yilun Acked-by: Wu Hao --- drivers/fpga/dfl-

[RESEND PATCH 1/2] fpga: dfl: pci: reduce the scope of variable 'ret'

This is to fix lkp cppcheck warnings: drivers/fpga/dfl-pci.c:230:6: warning: The scope of the variable 'ret' can be reduced. [variableScope] int ret = 0; ^ drivers/fpga/dfl-pci.c:230:10: warning: Variable 'ret' is assigned a value that is never used. [unreadVariable] int ret =

[RESEND PATCH 0/2] Bug fixes for FPGA DFL

Resend these 2 fix patches since the to-be-fixed patches have been merged to mainline. Matthew Gerlach (1): fpga: dfl: fix bug in port reset handshake Xu Yilun (1): fpga: dfl: pci: reduce the scope of variable 'ret' drivers/fpga/dfl-afu-main.c | 3 ++- drivers/fpga/dfl-pci.c | 3 ++- 2

[PATCH v2 1/2] firmware: arm_scmi: Keep the discrete clock rates sorted

Instead of relying on the firmware to keep the clock rates sorted, let us sort the list. This is not essential for clock layer but it helps to find the min and max rates easily from the list. Link: https://lore.kernel.org/r/20200708110725.18017-1-sudeep.ho...@arm.com Fixes: 5f6c6430e904 ("firmware

[PATCH v2 2/2] clk: scmi: Fix min and max rate when registering clocks with discrete rates

Currently we are not initializing the scmi clock with discrete rates correctly. We fetch the min_rate and max_rate value only for clocks with ranges and ignore the ones with discrete rates. This will lead to wrong initialization of rate range when clock supports discrete rate. Fix this by using th

Re: [PATCH 1/1] MAINTAINERS: add Hridya and myself into Android driver maintainers list

On Wed, Jul 08, 2020 at 04:12:53PM -0700, Suren Baghdasaryan wrote: > Add new maintainers for ashmem driver to handle related issues. > > Signed-off-by: Suren Baghdasaryan Can I get an ack/reviewed-by/something by the existing maintainers to verify this? :) And I thought we were deleting ashme

Re: [PATCH 2/2] doc, mm: clarify /proc//oom_score value range

On Thu 09-07-20 15:41:11, Yafang Shao wrote: > On Thu, Jul 9, 2020 at 2:26 PM Michal Hocko wrote: > > > > From: Michal Hocko > > > > The exported value includes oom_score_adj so the range is no [0, 1000] > > as described in the previous section but rather [0, 2000]. Mention that > > fact explicit

Re: [PATCH] bfq: fix blkio cgroup leakage

Paolo Valente writes: >> Il giorno 8 lug 2020, alle ore 19:48, Dmitry Monakhov >> ha scritto: >> >> Paolo Valente writes: >> >>> Hi, >>> sorry for the delay. The commit you propose to drop fix the issues >>> reported in [1]. >>> >>> Such a commit does introduce the leak that you report (th

RE: [PATCH 1/2] firmware: arm_scmi: Keep the discrete clock rates sorted

Hi Sudeep, I share my build warning and some in-line comment below: CC drivers/firmware/arm_scmi/clock.o drivers/firmware/arm_scmi/clock.c: In function 'rate_cmp_func': drivers/firmware/arm_scmi/clock.c:127:12: warning: initialization discards 'const' qualifier from pointer target type [-

Re: [PATCH] bus: fsl-mc: fix invalid free in fsl_mc_device_add

On Wed, Jul 08, 2020 at 11:45:24AM -0700, t...@redhat.com wrote: > From: Tom Rix > > clang static analysis flags this error > > fsl-mc-bus.c:695:2: warning: Attempt to free released memory [unix.Malloc] > kfree(mc_dev); > ^ > > The problem block of code is > >

linux-next: build failure after merge of the akpm-current tree

Hi all, [Also reported by Randy Dunlap.] After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) failed like this: mm/migrate.c: In function 'migrate_pages': mm/migrate.c:1528:19: error: 'THP_MIGRATION_SUCCESS' undeclared (first use in this function); did you mean

Re: [PATCH v2] genpd: Fix up terminology with parent/child

On Wed, Jul 08, 2020 at 04:32:13PM -0700, Kees Cook wrote: > The genpd infrastructure uses the terms master/slave, but such uses have > no external exposures (not even in Documentation/driver-api/pm/*) and are > not mandated by nor associated with any external specifications. Change > the language

[PATCH] fpga: dfl: pci: add device id for Intel FPGA PAC N3000

Add PCIe Device ID for Intel FPGA PAC N3000. Signed-off-by: Wu Hao Signed-off-by: Xu Yilun Signed-off-by: Matthew Gerlach Signed-off-by: Russ Weight --- drivers/fpga/dfl-pci.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/fpga/dfl-pci.c b/drivers/fpga/dfl-pci.c index 73b5153..

Re: [PATCH 3/4] firmware: arm_scmi: Fix scmi_event_header fields typing

On Wed, Jul 08, 2020 at 10:38:08PM +0200, Arnd Bergmann wrote: > On Wed, Jul 8, 2020 at 2:24 PM Cristian Marussi > wrote: > > > > Drop size_t in favour of fixed size u32 for consistency and shuffle > > around fields definitions to minimize implicit padding. > > > > Signed-off-by: Cristian Marussi

[PATCH] arm64: kernel: Add module symbols _text, _etext.

From: Sanggil Kim We have a solution to protect kernel code section(autually from _text to _etext) by not MMU. In order to do this, we have to know the addresses of _text and _etext at runtime. Signed-off-by: Sanggil Kim --- arch/arm64/kernel/head.S | 3 +++ 1 file changed, 3 insertions(+) di

Re: WARNING: at mm/mremap.c:211 move_page_tables in i386

On Thu, Jul 9, 2020 at 7:28 AM Naresh Kamboju wrote: > > While running LTP mm test suite on i386 or qemu_i386 this kernel warning > has been noticed from stable 5.4 to stable 5.7 branches and mainline 5.8.0-rc4 > and linux next. Are you able to correlate this with any particular test case in LTP,

RE: [PATCH v2 2/2] clk: scmi: Fix min and max rate when registering clocks with discrete rates

Hi Sudeep, Thanks for your patch. >-Original Message- >From: Sudeep Holla >Sent: Thursday, July 9, 2020 3:17 PM >To: linux-arm-ker...@lists.infradead.org; linux-...@vger.kernel.org; Stephen >Boyd >Cc: Sudeep Holla ; linux-kernel@vger.kernel.org; Michael >Turquette ; Dien Pham >Subje

[PATCH] edac: nxp: Add L1 and L2 error detection for A53 and A72 cores

Add error detection for A53 and A72 cores. Hardware error injection is supported on A53. Software error injection is supported on both. For hardware error injection on A53 to work, proper access to L2ACTLR_EL1, CPUACTLR_EL1 needs to be granted by EL3 firmware. This is done by making an SMC call in

Re: [GIT PULL] EFI fixes

On Wed, Jul 08, 2020 at 11:00:19AM -0700, Linus Torvalds wrote: > On Wed, Jul 8, 2020 at 9:21 AM Peter Zijlstra wrote: > > > > > > It's perhaps yet another reason to just skip gcc-4.8 too, since > > > apparently 4.9 works. > > > > > > gcc-4.9 really has a lot of advantages. It's where (I think) gc

Re: [PATCH v5 4/9] remoteproc: Introducing function rproc_actuate()

Hi Mathieu, On 7/7/20 11:00 PM, Mathieu Poirier wrote: > Introduce function rproc_actuate() that provides the same > functionatlity as rproc_fw_boot(), but without the steps that > involve interaction with the firmware image. That way we can > deal with scenarios where the remoteproc core is att

Re: [PATCH 0/2] perf: Allow closing siblings' file descriptors

Hi Alex, On 08.07.2020 18:16, Alexander Shishkin wrote: > Hi guys, > > I've been looking at reducing the number of open file descriptors per perf > session. If we retain one descriptor per event, in a large group they add > up. At the same time, we're not actually using them for anything after th

RE: [PATCH v3] scsi: ufs: Cleanup completed request without interrupt notification

> > If somehow no interrupt notification is raised for a completed request > and its doorbell bit is cleared by host, UFS driver needs to cleanup > its outstanding bit in ufshcd_abort(). Theoretically, this case is already accounted for - See line 6407: a proper error is issued and eventually o

[PATCH v14 0/2] Add initial support for slimport anx7625

Hi all, The following series add support for the Slimport ANX7625 transmitter, a ultra-low power Full-HD 4K MIPI to DP transmitter designed for portable device. This is the v14 version, any mistakes, please let me know, I will fix it in the next series. Change history: v14: Fix comments from Sa

Re: [PATCH v3 0/6] powerpc: queued spinlocks and rwlocks

On Wed, Jul 08, 2020 at 07:54:34PM -0400, Waiman Long wrote: > On 7/8/20 4:41 AM, Peter Zijlstra wrote: > > On Tue, Jul 07, 2020 at 03:57:06PM +1000, Nicholas Piggin wrote: > > > Yes, powerpc could certainly get more performance out of the slow > > > paths, and then there are a few parameters to tu

[PATCH v14 1/2] dt-bindings: drm/bridge: anx7625: MIPI to DP transmitter DT schema

anx7625: MIPI to DP transmitter DT schema Signed-off-by: Xin Ji Reviewed-by: Rob Herring --- .../bindings/display/bridge/analogix,anx7625.yaml | 95 ++ 1 file changed, 95 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/bridge/analogix,anx7625.ya

Re: [PATCH v5 5/9] remoteproc: Introducing function rproc_validate()

On 7/7/20 11:00 PM, Mathieu Poirier wrote: > Add a new function to assert the general health of the remote > processor before handing it to the remoteproc core. > > Signed-off-by: Mathieu Poirier Reviewed-by: Arnaud Pouliquen Thanks, Arnaud > --- > drivers/remoteproc/remoteproc_core.c | 4

Re: [printk] 18a2dc6982: ltp.kmsg01.fail

On (20/07/09 15:14), kernel test robot wrote: [..] Took me a while to find the FAIL-ed test: > kmsg01.c:393: INFO: TEST: read returns EPIPE when messages get overwritten > kmsg01.c:398: INFO: first seqno: 0 > kmsg01.c:411: INFO: first seqno now: 881 > kmsg01.c:425: FAIL: read returned: 77: SUCCES

  1   2   3   4   5   6   7   8   9   10   >