Re: scheduling while atomic in z3fold

On Mon, 2020-12-07 at 02:05 +0100, Vitaly Wool wrote: > > Could you please try the following patch in your setup: crash> gdb list *z3fold_zpool_free+0x527 0xc0e14487 is in z3fold_zpool_free (mm/z3fold.c:341). 336 if (slots->slot[i]) { 337 is_

RE: [PATCH 04/15] usb: misc: ehset: update to use the usb_control_msg_{send|recv}() API

> > The newer usb_control_msg_{send|recv}() API are an improvement on the > existing usb_control_msg() as it ensures that a short read/write is treated as > an error, data can be used off the stack, and raw usb pipes need not be > created > in the calling functions. > For this reason, instances

Re: [PATCH] docs/zh_CN: Improve Cinese transolation quality.

在 2020/12/5 下午6:36, Ran Wang 写道: > Signed-off-by: Ran Wang > --- > .../translations/zh_CN/process/1.Intro.rst| 61 ++- > 1 file changed, 32 insertions(+), 29 deletions(-) > > diff --git a/Documentation/translations/zh_CN/process/1.Intro.rst > b/Documentation/translations/

Re: [PATCH 16/22] xlink-ipc: Add xlink ipc driver

On Tue, 2020-12-01 at 14:35 -0800, mgr...@linux.intel.com wrote: > From: Seamus Kelly > > Add xLink driver, which interfaces the xLink Core driver with the Keem > Bay VPU IPC driver, thus enabling xLink to control and communicate with > the VPU IP present on the Intel Keem Bay SoC. Trivial style

Re: [PATCH 3/7] mm,madvise: call soft_offline_page() without MF_COUNT_INCREASED

On Sat, Dec 05, 2020 at 04:34:23PM +0100, Oscar Salvador wrote: > On Fri, Dec 04, 2020 at 06:25:31PM +0100, Vlastimil Babka wrote: > > OK, so that means we don't introduce this race for MADV_SOFT_OFFLINE, but > > it's > > already (and still) there for MADV_HWPOISON since Dan's 23e7b5c2e271 ("mm, >

linux-next: manual merge of the block tree with the btrfs tree

Hi all, Today's linux-next merge of the block tree got a conflict in: fs/btrfs/check-integrity.c between commit: 068afafa2589 ("btrfs: drop casts of bio bi_sector") from the btrfs tree and commit: 051707baf43b ("block: store a block_device pointer in struct bio") from the block tree.

[PATCH] mtd: spi-nor: macronix: enable 4-bit BP support for MX25L6405D

Enable 4-bit Block Protect support for MX256405D and its variants using the same ID. Tested on Innacom W3400V6 router with MX25L6406E chip. https://github.com/openwrt/openwrt/pull/3501 Signed-off-by: Sieng Piaw Liew --- drivers/mtd/spi-nor/macronix.c | 3 ++- 1 file changed, 2 insertions(+), 1

Re: [PATCH] vdpa/mlx5: Use write memory barrier after updating CQ index

On 2020/12/6 下午6:57, Eli Cohen wrote: Make sure to put write memory barrier after updating CQ consumer index so the hardware knows that there are available CQE slots in the queue. Failure to do this can cause the update of the RX doorbell record to get updated before the CQ consumer index resu

Re: [PATCH 21/22] xlink-core: add async channel and events

On Tue, 2020-12-01 at 14:35 -0800, mgr...@linux.intel.com wrote: > Enable asynchronous channel and event communication. [] > diff --git a/drivers/misc/xlink-core/xlink-core.c > b/drivers/misc/xlink-core/xlink-core.c [] > + > +// sysfs attribute functions > + > +static ssize_t event0_show(struct de

Re: [PATCH 22/22] xlink-core: factorize xlink_ioctl function by creating sub-functions for each ioctl command

On Tue, 2020-12-01 at 14:35 -0800, mgr...@linux.intel.com wrote: > From: Seamus Kelly > > Refactor the too large IOCTL function to call helper functions. This should not be sent as a known poor patch as patch 21 of 22 and then updated in patch 22 of 22 with a better style. This should be sent i

Re: [PATCH] iommu/amd: Increase interrupt remapping table limit to 512 entries

Jerry, On 12/2/20 6:53 AM, Jerry Snitselaar wrote: Suravee Suthikulpanit @ 2020-10-14 19:50 MST: Certain device drivers allocate IO queues on a per-cpu basis. On AMD EPYC platform, which can support up-to 256 cpu threads, this can exceed the current MAX_IRQ_PER_TABLE limit of 256, and result

linux-next: build failure after merge of the block tree

Hi all, After merging the block tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: fs/io_uring.c: In function 'io_shutdown': fs/io_uring.c:3782:9: error: too many arguments to function 'sock_from_file' 3782 | sock = sock_from_file(req->file, &ret); | ^~

Re: [PATCH v2 2/2] drivers: gpio: add virtio-gpio guest driver

On 2020/12/6 上午3:32, Michael S. Tsirkin wrote: On Sat, Dec 05, 2020 at 08:59:55AM +0100, Enrico Weigelt, metux IT consult wrote: On 04.12.20 04:35, Jason Wang wrote: --- a/drivers/gpio/Kconfig +++ b/drivers/gpio/Kconfig @@ -1615,6 +1615,15 @@ config GPIO_MOCKUP         tools/testing/

[PATCH 1/1] dt-bindings: mediatek: mt8192: eliminate yamllint warnings

Eliminate the following yamllint warnings: ./Documentation/devicetree/bindings/sound/mt8192-mt6359-rt1015-rt5682.yaml :10:4: [warning] wrong indentation: expected 2 but found 3 (indentation) Signed-off-by: Zhen Lei --- .../devicetree/bindings/sound/mt8192-mt6359-rt1015-rt5682.yaml| 4 ++-

Re: [PATCH v2 2/2] drivers: gpio: add virtio-gpio guest driver

On 2020/12/6 上午4:05, Enrico Weigelt, metux IT consult wrote: On 05.12.20 20:32, Michael S. Tsirkin wrote: Hi, It seems a bit of a mess, at this point I'm not entirely sure when should drivers select VIRTIO and when depend on it. if VIRTIO just enables something that could be seen as library

Re: [PATCH 0/5] crypto: hisilicon - add some new algorithms

On 2020/12/7 9:33, Herbert Xu wrote: > On Mon, Dec 07, 2020 at 09:20:05AM +0800, liulongfang wrote: >> >> Did any test case tests fail? > > You tell me :) > > If it passed all of the tests in your testing, please state that > in the cover letter or in one of the patches. > > Thanks, > OK, I wil

[PATCH 0/1] dt-bindings: mmc: eliminate yamllint warnings

This patch is based on the latest linux-next code. Zhen Lei (1): dt-bindings: mmc: eliminate yamllint warnings Documentation/devicetree/bindings/mmc/mtk-sd.yaml | 26 +++ 1 file changed, 13 insertions(+), 13 deletions(-) -- 1.8.3

[PATCH 1/1] dt-bindings: mmc: eliminate yamllint warnings

Eliminate the following yamllint warnings: ./Documentation/devicetree/bindings/mmc/mtk-sd.yaml :20:9: [warning] wrong indentation: expected 10 but found 8 (indentation) :30:9: [warning] wrong indentation: expected 10 but found 8 (indentation) :33:9: [warning] wrong indentation: expected 10 but foun

[PATCH v3 0/6] drm/imx: Introduce i.MX8qm/qxp DPU DRM

Hi, This patch set introduces i.MX8qm/qxp Display Processing Unit(DPU) DRM support. DPU is comprised of a blit engine for 2D graphics, a display controller and a command sequencer. Outside of DPU, optional prefetch engines can fetch data from memory prior to some DPU fetchunits of blit engine a

[PATCH v3 4/6] drm/atomic: Avoid unused-but-set-variable warning on for_each_old_plane_in_state

Artifically use 'plane' and 'old_plane_state' to avoid 'not used' warning. The precedent has already been set by other macros in the same file. Signed-off-by: Liu Ying --- v2->v3: * Add a missing blank line. v1->v2: * No change. include/drm/drm_atomic.h | 5 - 1 file changed, 4 insertions(

[PATCH v3 2/6] dt-bindings: display: imx: Add i.MX8qxp/qm PRG binding

This patch adds bindings for i.MX8qxp/qm Display Prefetch Resolve Gasket. Signed-off-by: Liu Ying --- Note that this depends on the 'two cell binding' clock patch set which has already landed in Shawn's i.MX clk/imx git branch. Otherwise, imx8-lpcg.h won't be found. v2->v3: * No change. v1->v2

[PATCH v3 1/6] dt-bindings: display: imx: Add i.MX8qxp/qm DPU binding

This patch adds bindings for i.MX8qxp/qm Display Processing Unit. Signed-off-by: Liu Ying --- Note that this depends on the 'two cell binding' clock patch set which has already landed in Shawn's i.MX clk/imx git branch. Otherwise, imx8-lpcg.h won't be found. v2->v3: * No change. v1->v2: * Fix

[PATCH v3 6/6] MAINTAINERS: add maintainer for i.MX8qxp DPU DRM driver

Add myself as the maintainer of the i.MX8qxp DPU DRM driver. Signed-off-by: Liu Ying --- v2->v3: * No change. v1->v2: * No change. MAINTAINERS | 9 + 1 file changed, 9 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 970d9ce..dee4586 100644 --- a/MAINTAINERS +++ b/MAINTAINER

[PATCH v3 3/6] dt-bindings: display: imx: Add i.MX8qxp/qm DPR channel binding

This patch adds bindings for i.MX8qxp/qm Display Prefetch Resolve Channel. Signed-off-by: Liu Ying --- Note that this depends on the 'two cell binding' clock patch set which has already landed in Shawn's i.MX clk/imx git branch. Otherwise, imx8-lpcg.h won't be found. v2->v3: * No change. v1->v

Re: [PATCH V2 19/19] vdpa: introduce virtio pci driver

On 2020/12/5 上午1:12, Randy Dunlap wrote: On 12/4/20 7:20 AM, Stefano Garzarella wrote: On Fri, Dec 04, 2020 at 12:03:53PM +0800, Jason Wang wrote: This patch introduce a vDPA driver for virtio-pci device. It bridges the virtio-pci control command to the vDPA bus. This will be used for feature

Re: [PATCH v2 1/4] PCI: rockchip: Make 'ep-gpios' DT property optional

Ping On Wed, Nov 18, 2020 at 4:49 PM Heiko Stübner wrote: > > Am Mittwoch, 18. November 2020, 08:17:21 CET schrieb Chen-Yu Tsai: > > From: Chen-Yu Tsai > > > > The Rockchip PCIe controller DT binding clearly states that 'ep-gpios' is > > an optional property. And indeed there are boards that don

Re: [PATCHSET] saner elf compat

On December 5, 2020 7:23:05 PM PST, Al Viro wrote: >On Thu, Dec 03, 2020 at 11:03:36PM +, Al Viro wrote: >> > > The answer (for mainline) is that mips compat does *NOT* want >> > > COMPAT_BINFMT_ELF. Not a problem with that series, though, so >I'd >> > > retested it (seems to work, both for

Re: [PATCH v2 bpf-next 0/3] bpf: support module BTF in BTF display helpers

On 12/5/20 4:43 PM, Alan Maguire wrote: On Sat, 5 Dec 2020, Yonghong Song wrote: __builtin_btf_type_id() is really only supported in llvm12 and 64bit return value support is pushed to llvm12 trunk a while back. The builtin is introduced in llvm11 but has a corner bug, so llvm12 is recomme

Re: [PATCH 1/1] ionic: fix array overflow on receiving too many fragments for a packet

On 12/6/20 5:51 PM, Jesse Brandeburg wrote: Xiaohui Zhang wrote: From: Zhang Xiaohui If the hardware receives an oversized packet with too many rx fragments, skb_shinfo(skb)->frags can overflow and corrupt memory of adjacent pages. This becomes especially visible if it corrupts the freelist p

Re: [PATCH 2/5] crypto: hisilicon/sec - add new type of sqe for Kunpeng930

On 2020/12/4 15:03, Herbert Xu Wrote: > On Thu, Nov 26, 2020 at 10:18:03AM +0800, Longfang Liu wrote: >> >> diff --git a/drivers/crypto/hisilicon/sec2/sec_crypto.h >> b/drivers/crypto/hisilicon/sec2/sec_crypto.h >> index 0e933e7..712176b 100644 >> --- a/drivers/crypto/hisilicon/sec2/sec_crypto.h

Re: [PATCH 2/5] crypto: hisilicon/sec - add new type of sqe for Kunpeng930

On Mon, Dec 07, 2020 at 11:43:38AM +0800, liulongfang wrote: > > Can I use __attribute__((aligned(n))) instead of #pragma pack(n)? We normally just use __aligned(n) in the kernel. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~h

Re: [PATCH v2 2/2] drivers: gpio: add virtio-gpio guest driver

On 2020/12/4 下午5:36, Enrico Weigelt, metux IT consult wrote: On 04.12.20 04:35, Jason Wang wrote: Hi, Is the plan to keep this doc synced with the one in the virtio specification? Yes, of course. I'm still in progress of doing the beaurocratic stuff w/ virtio-tc folks (ID registration, ...)

Re: [RFC] fpga: dfl: a prototype uio driver

On Sun, Dec 06, 2020 at 01:55:54PM -0800, t...@redhat.com wrote: > From: Tom Rix > > >From [PATCH 0/2] UIO support for dfl devices > https://lore.kernel.org/linux-fpga/1602828151-24784-1-git-send-email-yilun...@intel.com/ > > Here is an idea to have uio support with no driver override. > > This

Re: [PATCH v3 04/19] vhost/iotlb: add VHOST_IOTLB_UNLIMITED macro

On 2020/12/4 上午1:04, Stefano Garzarella wrote: It's possible to allocate an unlimited IOTLB calling vhost_iotlb_alloc() with 'limit' = 0. Add a new macro (VHOST_IOTLB_UNLIMITED) for this case and document it in the vhost_iotlb_alloc() documentation block. Suggested-by: Jason Wang Signed-off-

Re: [PATCH v3 05/19] vdpa_sim: remove the limit of IOTLB entries

On 2020/12/4 上午1:04, Stefano Garzarella wrote: The simulated devices can support multiple queues, so this limit should be defined according to the number of queues supported by the device. Since we are in a simulator, let's simply remove that limit. Suggested-by: Jason Wang Acked-by: Jason W

[PATCH] EDAC/mv64x60: Remove orphan mv64x60 driver

The mv64x60 EDAC driver depends on CONFIG_MV64X60. But that symbol is not user-selectable, and the last code that selected it was removed with the C2K board support in 2018, see: 92c8c16f3457 ("powerpc/embedded6xx: Remove C2K board support") That means the driver is now dead code, so remove it.

[PATCH 1/4] dt-bindings: media: adv7604: eliminate yamllint warnings

Eliminate the following yamllint warnings: ./Documentation/devicetree/bindings/media/i2c/adv7604.yaml :24:9: [warning] wrong indentation: expected 10 but found 8 (indentation) Signed-off-by: Zhen Lei --- Documentation/devicetree/bindings/media/i2c/adv7604.yaml | 4 ++-- 1 file changed, 2 inserti

[PATCH 4/4] dt-bindings: media: imx214: eliminate yamllint warnings

Eliminate the following yamllint warnings: ./Documentation/devicetree/bindings/media/i2c/sony,imx214.yaml :72:17: [warning] wrong indentation: expected 18 but found 16 (indentation) :75:17: [warning] wrong indentation: expected 18 but found 16 (indentation) Signed-off-by: Zhen Lei --- Documentat

[PATCH 3/4] dt-bindings: media: ov772x: eliminate yamllint warnings

Eliminate the following yamllint warnings: ./Documentation/devicetree/bindings/media/i2c/ovti,ov772x.yaml :79:17: [warning] wrong indentation: expected 14 but found 16 (indentation) :88:17: [warning] wrong indentation: expected 14 but found 16 (indentation) Signed-off-by: Zhen Lei --- Documentat

[PATCH 2/4] dt-bindings: media: nokia,smia: eliminate yamllint warnings

Eliminate the following yamllint warnings: ./Documentation/devicetree/bindings/media/i2c/mipi-ccs.yaml :4:1: [error] missing document start "---" (document-start) :29:9: [warning] wrong indentation: expected 10 but found 8 (indentation) :32:9: [warning] wrong indentation: expected 10 but found 8 (i

[PATCH 0/4] dt-bindings: media: eliminate yamllint warnings

These patches are based on the latest linux-next code. Zhen Lei (4): dt-bindings: media: adv7604: eliminate yamllint warnings dt-bindings: media: nokia,smia: eliminate yamllint warnings dt-bindings: media: ov772x: eliminate yamllint warnings dt-bindings: media: imx214: eliminate yamllint w

Re: [PATCH] userfaultfd: prevent non-cooperative events vs mcopy_atomic races

Thanks for the detailed answer, Mike. Things are clearer in regard to your intention. > On Dec 6, 2020, at 1:37 AM, Mike Rapoport wrote: > > The uffd monotor should *know* what is the state of child's memory and > without this patch it could only guess. I see - so mmap_changing is not just abou

RE: [PATCH v2] exfat: Avoid allocating upcase table using kcalloc()

> The table for Unicode upcase conversion requires an order-5 allocation, which > may fail on a highly- > fragmented system: > > pool-udisksd: page allocation failure: order:5, > mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), > nodemask=(null),cpuset=/,mems_allowed=0 > CPU: 4 PID: 3756880 Com

Re: BUG: Invalid wait context with KMEMLEAK and KASAN enabled

Hi Richard, On Sun, Dec 06, 2020 at 11:59:16PM +0100, Richard Weinberger wrote: > Hi! > > With both KMEMLEAK and KASAN enabled, I'm facing the following lockdep > splat at random times on Linus' tree as of today. > Sometimes it happens at bootup, sometimes much later when userspace has > started

Re: [RFC V2 3/3] s390/mm: Define arch_get_mappable_range()

On 12/3/20 5:31 PM, David Hildenbrand wrote: > On 03.12.20 12:51, Heiko Carstens wrote: >> On Thu, Dec 03, 2020 at 06:03:00AM +0530, Anshuman Khandual wrote: > diff --git a/arch/s390/mm/extmem.c b/arch/s390/mm/extmem.c > index 5060956b8e7d..cc055a78f7b6 100644 > --- a/arch/s390/mm/ex

Re: [RFC PATCH 0/9] CXL 2.0 Support

Hi Ben, >On Dec 4, 2020, at 1:12 PM, Ben Widawsky wrote: > >Hi Chris. > >On 20-12-04 12:40:03, Chris Browy wrote: > >Hi Ben, > >Trying to bring up the environment using the latest developments as follows: > >1. Linux kernel baseline version is cloned using > gi

Re: [PATCH 1/7] soundwire: bus: use sdw_update_no_pm when initializing a device

On 05-12-20, 08:59, Pierre-Louis Bossart wrote: > Thanks for the review Vinod. > > On 12/5/20 1:45 AM, Vinod Koul wrote: > > On 03-12-20, 04:46, Bard Liao wrote: > > > From: Pierre-Louis Bossart > > > > > > When a Slave device is resumed, it may resume the bus and restart the > > > enumeration.

[Regression] Can only do S3 once after "tpm: take TPM chip power gating out of tpm_transmit()"

Hi Jarkko, A user report that the system can only do S3 once. Subsequent S3 fails after commit a3fbfae82b4c ("tpm: take TPM chip power gating out of tpm_transmit()"). Dmesg with the issue, collected under 5.10-rc2: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891502/comments/14 Dmesg w

undefined reference to `cpu_sa110_suspend_size'

Hi Stephan, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 0477e92881850d44910a7e94fc2c46f96faa131f commit: a871be6b8eee13a35a3e8e56c62770ef17ee9220 cpuidle: Convert Qualcomm SPM driver to a generic CPUidle driver

Re: [PATCH 5/7] regmap: sdw: use no_pm routines for SoundWire 1.2 MBQ

On 05-12-20, 17:31, Greg KH wrote: > On Sat, Dec 05, 2020 at 08:52:50AM -0600, Pierre-Louis Bossart wrote: > > > > > > MODULE_DESCRIPTION("Regmap SoundWire MBQ Module"); > > > > -MODULE_LICENSE("GPL v2"); > > > > +MODULE_LICENSE("GPL"); > > > > > > Why do you want to change this ? > > > > We o

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

On Mon, Dec 07, 2020 at 08:39:20AM +1100, Stephen Rothwell wrote: > Hi Paul, > > On Fri, 4 Dec 2020 11:20:32 -0800 "Paul E. McKenney" > wrote: > > > > Does the following patch fix things? (Sigh. It won't apply on the > > rcu/next that you used. Or even on this moment's dev branch. I will > >

[PATCH v2 0/1] dt-bindings: display: eliminate yamllint warnings

This patch is based on the latest linux-next code. v1 --> v2: Extract the modification of the Documentation/devicetree/bindings/display/ parts and send the patch separately. https://www.spinics.net/lists/arm-kernel/msg860713.html v1: There're too many people, I just send to the maintainer, revi

[PATCH v2 1/1] dt-bindings: display: eliminate yamllint warnings

Eliminate the following yamllint warnings: ./Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml :52:9: [warning] wrong indentation: expected 6 but found 8 (indentation) ./Documentation/devicetree/bindings/display/bridge/intel,keembay-dsi.yaml :42:8: [warning] wrong indentation:

Re: [PATCH v6 0/6] Tegra210 audio graph card

Hi Mark, This series adds audio graph based sound card support for Tegra210 platforms like Jetson-TX1 an Jetson-Nano. The following preparatory audio graph enhancement series is already merged. * https://patchwork.kernel.org/project/alsa-devel/list/?series=375629&state=* Following are the sum

[PATCH 1/1] dt-bindings: clock: imx8qxp-lpcg: eliminate yamllint warnings

Eliminate the following yamllint warnings: ./Documentation/devicetree/bindings/clock/imx8qxp-lpcg.yaml :32:13:[warning] wrong indentation: expected 14 but found 12 (indentation) :35:9: [warning] wrong indentation: expected 10 but found 8 (indentation) Signed-off-by: Zhen Lei --- .../devicetree/b

[PATCH 0/1] dt-bindings: clock: imx8qxp-lpcg: eliminate yamllint warnings

This patch is based on the latest linux-next code. Zhen Lei (1): dt-bindings: clock: imx8qxp-lpcg: eliminate yamllint warnings .../devicetree/bindings/clock/imx8qxp-lpcg.yaml | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) -- 1.8.3

[GIT PULL]: soundwire updates for v5.11-rc1

Hello Greg, Please pull to receive updates for v5.11 as detailed below: The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec: Linux 5.10-rc1 (2020-10-25 15:14:11 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundw

Re: [PATCH] vhost scsi: fix error return code in vhost_scsi_set_endpoint()

On 2020/12/4 下午4:43, Zhang Changzhong wrote: Fix to return a negative error code from the error handling case instead of 0, as done elsewhere in this function. Fixes: 25b98b64e284 ("vhost scsi: alloc cmds per vq instead of session") Reported-by: Hulk Robot Signed-off-by: Zhang Changzhong ---

Re: [PATCH v2 3/3] scsi: ufs: Changes comment in the function ufshcd_wb_probe()

On Sun, 2020-12-06 at 11:13 +0100, Bean Huo wrote: > From: Bean Huo > > USFHCD supports WriteBooster "LU dedicated buffer” mode and > “shared buffer” mode both, so changes the comment in the > function ufshcd_wb_probe(). > > Signed-off-by: Bean Huo > Reviewed-by: Can Guo Reviewed-by: Stanley

Re: [PATCH] Fixes kernel crash generating from bam_dma_irq()

Hi Parth, On 06-12-20, 15:51, Parth Y Shah wrote: > While performing suspend/resume, we were getting below kernel crash. > > [ 54.541672] [FTS][Info]gesture suspend... > [ 54.605256] [FTS][Error][GESTURE]Enter into gesture(suspend) failed! > [ 54.605256] > [ 58.345850] irq event 10: bogus

Re: [PATCH v3 12/19] vdpa_sim: make 'config' generic and usable for any device type

On 2020/12/4 上午1:05, Stefano Garzarella wrote: Add new 'config_size' attribute in 'vdpasim_dev_attr' and allocates 'config' dynamically to support any device types. Signed-off-by: Stefano Garzarella --- drivers/vdpa/vdpa_sim/vdpa_sim.c | 17 + 1 file changed, 13 insertions(

Re: [PATCH] clk: imx: Fix reparenting of UARTs not associated with sdout

Hi Adam, On Fri, Dec 04, 2020 at 12:31:54PM -0600, Adam Ford wrote: > The default clock source on i.MX8M Mini and Nano boards use a 24MHz clock, > but users who need to re-parent the clock source run into issues because > all the UART clocks are enabled whether or not they're needed by sdout. > >

Re: [PATCH v3 13/19] vdpa_sim: add get_config callback in vdpasim_dev_attr

On 2020/12/4 上午1:05, Stefano Garzarella wrote: The get_config callback can be used by the device to fill the config structure. The callback will be invoked in vdpasim_get_config() before copying bytes into caller buffer. Move vDPA-net config updates from vdpasim_set_features() in the new vdpas

Re: [PATCH v3 14/19] vdpa_sim: add set_config callback in vdpasim_dev_attr

On 2020/12/4 上午1:05, Stefano Garzarella wrote: The set_config callback can be used by the device to parse the config structure modified by the driver. The callback will be invoked, if set, in vdpasim_set_config() after copying bytes from caller buffer into vdpasim->config buffer. Signed-off-b

Re: [PATCH v3 15/19] vdpa_sim: set vringh notify callback

On 2020/12/4 上午1:05, Stefano Garzarella wrote: Instead of calling the vq callback directly, we can leverage the vringh_notify() function, adding vdpasim_vq_notify() and setting it in the vringh notify callback. Suggested-by: Jason Wang Signed-off-by: Stefano Garzarella Acked-by: Jason Wan

Re: [PATCH v3 19/19] vdpa: split vdpasim to core and net modules

On 2020/12/4 上午1:05, Stefano Garzarella wrote: From: Max Gurtovoy Introduce new vdpa_sim_net and vdpa_sim (core) drivers. This is a preparation for adding a vdpa simulator module for block devices. Signed-off-by: Max Gurtovoy [sgarzare: various cleanups/fixes] Signed-off-by: Stefano Garzarell

Re: [PATCH] Revert "xen: add helpers to allocate unpopulated memory"

On 06.12.20 18:22, Marek Marczykowski-Górecki wrote: This reverts commit 9e2369c06c8a181478039258a4598c1ddd2cadfa. On a Xen PV dom0, with NVME disk, this makes the dom0 crash when starting a domain. This looks like some bad interaction between xen-blkback and xen-scsiback has the same use patt

Re: [PATCH v2 2/3] scsi: ufs: Keep device active mode only fWriteBoosterBufferFlushDuringHibernate == 1

On Sun, 2020-12-06 at 11:13 +0100, Bean Huo wrote: > From: Bean Huo > > According to the JEDEC UFS 3.1 Spec, If > fWriteBoosterBufferFlushDuringHibernate > is set to one, the device flushes the WriteBooster Buffer data automatically > whenever the link enters the hibernate (HIBERN8) state. While

Re: [PATCH 1/3] thermal: core: Add indication for userspace usage

> On Dec 1, 2020, at 02:39, Srinivas Pandruvada > wrote: > > On Tue, 2020-12-01 at 02:22 +0800, Kai-Heng Feng wrote: >>> On Dec 1, 2020, at 02:13, Srinivas Pandruvada < >>> srinivas.pandruv...@linux.intel.com> wrote: >> >> [snipped] >> > What about creating an new callback > >

sched: core.c:7270 Illegal context switch in RCU-bh read-side critical section! __alloc_pages_nodemask

While booting arm64 hikey board with stable-rc 5.9.13-rc1 the following warning noticed. This is hard to reproduce. Step to reproduce: # Boot arm64 hikey device with stable-rc 5.9.13-rc1 # Since it is hard to reproduce you may notice this warning Crash log : -

linux-next: build failure after merge of the staging tree

Hi all, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/iio/trigger/iio-trig-sysfs.c: In function 'iio_sysfs_trigger_probe': drivers/iio/trigger/iio-trig-sysfs.c:164:21: error: 'struct irq_work' has no member named 'flags' 164 | atomic_

WARNING: bad unlock balance detected! - mkfs.ext4/426 is trying to release lock (rcu_read_lock)

While running "mkfs -t ext4" on arm64 juno-r2 device connected with SSD drive the following kernel warning reported on stable rc 5.9.13-rc1 kernel. Steps to reproduce: -- # boot arm64 Juno-r2 device with stable-rc 5.9.13-rc1. # Connect SSD drive # Format the file system ext4 type

[PATCH v1 0/2] scsi: ufs: Allow regulators being always on

Hi, This series allow vendors to keep the regulator always-on, and provide an implementation on MediaTek UFS platforms. Stanley Chu (2): scsi: ufs: Allow regulators being always-on scsi: ufs-mediatek: Keep VCC always-on for specific devices drivers/scsi/ufs/ufs-mediatek.c | 21 +

[PATCH v1 1/2] scsi: ufs: Allow regulators being always-on

Introduce a flag "always_on" in struct ufs_vreg to allow vendors to keep the regulator always-on. Reviewed-by: Andy Teng Signed-off-by: Stanley Chu --- drivers/scsi/ufs/ufs.h| 1 + drivers/scsi/ufs/ufshcd.c | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/scsi/u

[PATCH v1 2/2] scsi: ufs-mediatek: Keep VCC always-on for specific devices

For some devices which needs extra delay after VCC power down, VCC shall be kept always-on in some MediaTek UFS platforms to ensure the stability of such devices because the extra delay may not be enough in those platforms. Reviewed-by: Andy Teng Signed-off-by: Stanley Chu --- drivers/scsi/ufs/

[PATCH] scsi: ufs: Enable WB flush during suspend only if WB is enabled

WriteBootser flush during suspend is not necessary to be enabled if WriteBooster feature is disabled. Simply adding a check to prevent unexpected power drain. Signed-off-by: Stanley Chu --- drivers/scsi/ufs/ufshcd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/scsi

Re: sched: core.c:7270 Illegal context switch in RCU-bh read-side critical section! __alloc_pages_nodemask

On Mon, Dec 07, 2020 at 11:06:10AM +0530, Naresh Kamboju wrote: > While booting arm64 hikey board with stable-rc 5.9.13-rc1 the following > warning > noticed. This is hard to reproduce. Ugh. You've got two warnings interleaved here. This is impossible to read. Do you have any examples where on

[PATCH] watchdog: qcom: Avoid context switch in restart handler

The use of msleep() in the restart handler will cause scheduler to induce a context switch which is not desirable. This generates below warning on SDX55 when WDT is the only available restart source: [ 39.800188] reboot: Restarting system [ 39.804115] [ cut here ] [ 3

Re: [V9fs-developer] [RFC PATCH] 9p: create writeback fid on shared mmap

在 星期一, 2020-12-07 04:53:18 Dominique Martinet 撰写 > Dominique Martinet wrote on Sun, Dec 06, 2020: > > Chengguang Xu wrote on Sat, Dec 05, 2020: > > > If vma is shared and the file was opened for writing, > > > we should also create writeback fid because vma may be > > > mprotected

[PATCH 1/1] ice: fix array overflow on receiving too many fragments for a packet

From: Zhang Xiaohui If the hardware receives an oversized packet with too many rx fragments, skb_shinfo(skb)->frags can overflow and corrupt memory of adjacent pages. This becomes especially visible if it corrupts the freelist pointer of a slab page. Signed-off-by: Zhang Xiaohui --- drivers/ne

Re: WARNING: bad unlock balance detected! - mkfs.ext4/426 is trying to release lock (rcu_read_lock)

On Mon, Dec 07, 2020 at 11:17:29AM +0530, Naresh Kamboju wrote: > While running "mkfs -t ext4" on arm64 juno-r2 device connected with SSD drive > the following kernel warning reported on stable rc 5.9.13-rc1 kernel. > > Steps to reproduce: > -- > # boot arm64 Juno-r2 device with st

Re: [RFC PATCH 5/9] cxl/mem: Find device capabilities

On 20-12-03 23:41:16, Dan Williams wrote: > On Tue, Nov 10, 2020 at 9:44 PM Ben Widawsky wrote: > > > > CXL devices contain an array of capabilities that describe the > > interactions software can interact with the device, or firmware running > > on the device. A CXL compliant device must implemen

[PATCH v3] venus: core: add support to dump FW region

From: Dikshita Agarwal Add support to dump video FW region during FW crash using devcoredump helpers. Signed-off-by: Dikshita Agarwal --- drivers/media/platform/qcom/venus/core.c | 31 drivers/media/platform/qcom/venus/core.h | 2 ++ drivers/media/platform

[PATCH] x86/mtrr: Correct the returned MTRR type of mtrr_type_lookup.

In mtrr_type_lookup, if the input memory address region is not in the MTRR, over 4GB, and not over the top of memory, write-back attribute is returned. These condition checks are for ensuring the input memory address region is mapped to the physical memory actually. However, if the end address is

[PATCH] media: usb: dvd-usb: fix uninit-value bug in dibusb_read_eeprom_byte()

In dibusb_read_eeprom_byte(), if dibusb_i2c_msg() fails, val gets assigned an value that's not properly initialized. Using kzalloc() in place of kmalloc() for the buffer fixes this issue, as the val can now be set to 0 in the event dibusb_i2c_msg() fails. Reported-by: syzbot+e27b4fd589762b0b9...@s

Re: [PATCH v2 0/9] Add support for Microsoft Surface System Aggregator Module

On Sun, Dec 06, 2020 at 04:58:52PM +0100, Maximilian Luz wrote: > On 12/6/20 8:07 AM, Leon Romanovsky wrote: > > On Thu, Dec 03, 2020 at 10:26:31PM +0100, Maximilian Luz wrote: > > > Hello, > > > > > > Here is version two of the Surface System Aggregator Module (SAM/SSAM) > > > driver series, addin

Re: [PATCH v2 07/22] drm/msm: Do rpm get sooner in the submit path

On 19-11-20, 11:35, Viresh Kumar wrote: > On 18-11-20, 08:53, Rob Clark wrote: > > On Tue, Nov 17, 2020 at 9:28 PM Viresh Kumar > > wrote: > > > > > > On 17-11-20, 09:02, Rob Clark wrote: > > > > With that on top of the previous patch, > > > > > > Don't you still have this ? Which fixed the lockd

Re: [PATCH v2] input: raydium_ts_i2c: Do not split tx transactions

On Fri, Dec 04, 2020 at 04:59:41PM -0800, Furquan Shaikh wrote: > Raydium device does not like splitting of tx transactions into > multiple messages - one for the register address and one for the > actual data. This results in incorrect behavior on the device side. > > This change updates raydium_

RE: [PATCH] exfat: Avoid allocating upcase table using kcalloc()

> > I have not yet received a report of the same issue. > > But I agree that this problem is likely to occur even if it is low > > probability. > > Perhaps I should clarify my setup a little bit more. > The issue can be reliably reproduced on my laptop. It has 8 GBs of RAM > (pretty common amount

RE: [RFC] fpga: dfl: a prototype uio driver

> Subject: Re: [RFC] fpga: dfl: a prototype uio driver > > On Sun, Dec 06, 2020 at 01:55:54PM -0800, t...@redhat.com wrote: > > From: Tom Rix > > > > >From [PATCH 0/2] UIO support for dfl devices > > https://lore.kernel.org/linux-fpga/1602828151-24784-1-git-send-email- > yilun...@intel.com/ > > >

[PATCH 0/3] Add LVTS architecture thermal controller

This patch move thermal files related to Mediatek to the mediatek folder. And introduce the new architecture LVTS (low pressure thermal sensor) driver to report the highest temperature in the SoC and record the highest temperature sensor, each sensor as a hot zone. The LVTS body is divided into tw

[PATCH 1/3] thermal: mediatek: Relocate driver to mediatek folder

Add Mediatek proprietary folder to upstream more thermal zone and cooler drivers. Relocate the original thermal controller driver to it and rename as soc_temp.c to show its purpose more clearly. Signed-off-by: Michael Kao --- drivers/thermal/Kconfig | 14 --- driver

[PATCH 3/3] dt-bindings: thermal: Add binding document for mt6873 thermal controller

This patch adds binding document for mt6873 thermal controller. Signed-off-by: Michael Kao --- .../thermal/mediatek-thermal-lvts.yaml| 80 +++ 1 file changed, 80 insertions(+) create mode 100644 Documentation/devicetree/bindings/thermal/mediatek-thermal-lvts.yaml diff

Re: [PATCH] cpufreq: imx: fix NVMEM_IMX_OCOTP dependency

On 03-12-20, 23:53, Arnd Bergmann wrote: > From: Arnd Bergmann > > A driver should not 'select' drivers from another subsystem. > If NVMEM is disabled, this one results in a warning: > > WARNING: unmet direct dependencies detected for NVMEM_IMX_OCOTP > Depends on [n]: NVMEM [=n] && (ARCH_MXC [

[PATCH 2/3] thermal: mediatek: Add LVTS drivers for SoC theraml zones

Add a LVTS (Low voltage thermal sensor) driver to report junction temperatures in Mediatek SoC and register the maximum temperature of sensors and each sensor as a thermal zone. Signed-off-by: Yu-Chia Chang Signed-off-by: Michael Kao --- drivers/thermal/mediatek/Kconfig | 10 + driver

[PATCH v2 1/2] dt-bindings: pinctrl: qcom: Add SM8350 pinctrl bindings

Add device tree binding Documentation details for Qualcomm SM8350 pinctrl driver. Signed-off-by: Vinod Koul --- .../bindings/pinctrl/qcom,sm8350-pinctrl.yaml | 151 ++ 1 file changed, 151 insertions(+) create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sm8350-pin

Re: [PATCH] cpufreq: scmi: add COMMON_CLK dependency

On 03-12-20, 23:55, Arnd Bergmann wrote: > From: Arnd Bergmann > > Wtihout CONFIG_COMMON_CLK, the scmi driver fails to link: > > arm-linux-gnueabi-ld: drivers/cpufreq/scmi-cpufreq.o: in function > `scmi_cpufreq_probe': > scmi-cpufreq.c:(.text+0x20c): undefined reference to > `devm_of_clk_add_h

[PATCH v2 2/2] pinctrl: qcom: Add SM8350 pinctrl driver

From: Raghavendra Rao Ananta This adds pincontrol driver for tlmm block found in SM8350 SoC Signed-off-by: Raghavendra Rao Ananta Signed-off-by: Jeevan Shriram [vkoul: rebase and tidy up for upstream] Signed-off-by: Vinod Koul --- drivers/pinctrl/qcom/Kconfig |8 + drivers/pinct

[PATCH] dmaengine: bam_dma: fix return of bam_dma_irq()

While performing suspend/resume, we were getting below kernel crash. [ 54.541672] [FTS][Info]gesture suspend... [ 54.605256] [FTS][Error][GESTURE]Enter into gesture(suspend) failed! [ 54.605256] [ 58.345850] irq event 10: bogus return value fff3 .. [ 58.345966] [] el1_irq+0xb0/0

Re: [PATCH v2 1/2] Input: i8042 - Prevent intermixing i8042 commands

Hi Raul, On Thu, Aug 27, 2020 at 02:41:53PM -0600, Raul E Rangel wrote: > The i8042_mutex must be held by writers of the AUX and KBD ports, as > well as users of i8042_command. There were a lot of users of > i8042_command that were not calling i8042_lock_chip/i8042_unlock_chip. > This resulted in

<    1   2   3   4   5   6   7   >