[RESEND PATCH V13 3/3] Input: new da7280 haptic driver

Adds support for the Dialog DA7280 LRA/ERM Haptic Driver with multiple mode and integrated waveform memory and wideband support. It communicates via an I2C bus to the device. Signed-off-by: Roy Im --- v13: - Updated some conditions in pwm function and alignments. v12: No changes. v11:

Re: [PATCH] fs: Do not check if there is a fsnotify watcher on pseudo inodes

On Fri, Jun 12, 2020 at 11:34:16PM +0300, Amir Goldstein wrote: > > > > So maybe it would be better to list all users of alloc_file_pseudo() > > > > and say that they all should be opted out of fsnotify, without > > > > mentioning > > > > "internal mount"? > > > > > > > > > > The users are DMA

[PATCH v6 2/6] spi: spi-geni-qcom: Use OPP API to set clk/perf state

geni spi needs to express a perforamnce state requirement on CX depending on the frequency of the clock rates. Use OPP table from DT to register with OPP framework and use dev_pm_opp_set_rate() to set the clk/perf state. Signed-off-by: Rajendra Nayak Reviewed-by: Matthias Kaehlcke Acked-by:

[PATCH v6 0/6] DVFS for IO devices on sdm845 and sc7180

Changes in v6: 1. rebased on 5.8-rc1, no functional change. Changes in v5: 1. Opp cleanup path fixed up across drivers Changes in v4: 1. Fixed all review feedback on v3 2. Dropped the dts patches, will post as a seperate series once driver changes are reviewed and merged. The driver changes

Re: [PATCH v4 2/3] venus: Make debug infrastructure more flexible

On Mon, Jun 15, 2020 at 12:55:29PM +0300, Stanimir Varbanov wrote: > Hi Greg, > > On 6/14/20 9:37 AM, Greg KH wrote: > > On Sun, Jun 14, 2020 at 01:39:18AM +0300, Stanimir Varbanov wrote: > >>if (slot == -1) { > >> - dev_dbg(inst->core->dev, "%s: no free slot\n", __func__); > >> +

[PATCH v6 5/6] media: venus: core: Add support for opp tables/perf voting

Add support to add OPP tables and perf voting on the OPP powerdomain. This is needed so venus votes on the corresponding performance state for the OPP powerdomain along with setting the core clock rate. Signed-off-by: Rajendra Nayak Reviewed-by: Matthias Kaehlcke Cc: Stanimir Varbanov Cc:

[PATCH v6 4/6] drm/msm: dsi: Use OPP API to set clk/perf state

On SDM845 DSI needs to express a perforamnce state requirement on a power domain depending on the clock rates. Use OPP table from DT to register with OPP framework and use dev_pm_opp_set_rate() to set the clk/perf state. Signed-off-by: Rajendra Nayak Cc: Rob Clark Cc: Sean Paul Cc:

[PATCH v6 3/6] drm/msm/dpu: Use OPP API to set clk/perf state

On some qualcomm platforms DPU needs to express a performance state requirement on a power domain depending on the clock rates. Use OPP table from DT to register with OPP framework and use dev_pm_opp_set_rate() to set the clk/perf state. Signed-off-by: Rajendra Nayak Reviewed-by: Rob Clark

[PATCH v6 1/6] tty: serial: qcom_geni_serial: Use OPP API to set clk/perf state

geni serial needs to express a perforamnce state requirement on CX powerdomain depending on the frequency of the clock rates. Use OPP table from DT to register with OPP framework and use dev_pm_opp_set_rate() to set the clk/perf state. Signed-off-by: Rajendra Nayak Reviewed-by: Matthias Kaehlcke

[PATCH v6 6/6] spi: spi-qcom-qspi: Use OPP API to set clk/perf state

QSPI needs to vote on a performance state of a power domain depending on the clock rate. Add support for it by specifying the perf state/clock rate as an OPP table in device tree. Signed-off-by: Rajendra Nayak Reviewed-by: Matthias Kaehlcke Acked-by: Mark Brown Cc: Alok Chauhan Cc: Akash

Re: [PATCH 2/2] bitmap: Add test for bitmap_cut()

On Mon, Jun 15, 2020 at 12:46:16PM +0300, Andy Shevchenko wrote: > On Mon, Jun 15, 2020 at 12:41:55PM +0300, Andy Shevchenko wrote: > > On Sun, Jun 14, 2020 at 07:40:54PM +0200, Stefano Brivio wrote: > > > Inspired by an original patch from Yury Norov: introduce a test for > > > bitmap_cut() that

Re: [PATCH] coccinelle: api: add kzfree script

On Sun, Jun 14, 2020 at 10:42:54PM +0300, Denis Efremov wrote: > On 6/4/20 7:27 PM, Joe Perches wrote: > > On Thu, 2020-06-04 at 17:08 +0300, Denis Efremov wrote: > >> Check for memset() with 0 followed by kfree(). > > > > Perhaps those uses should be memzero_explicit or kvfree_sensitive. > > >

Re: [PATCH v2 3/3] genirq: Do not test disabled IRQs with DEBUG_SHIRQ

On Mon, Jun 15, 2020 at 10:07:19AM +0200, Krzysztof Kozlowski wrote: > Testing events during freeing of disabled shared interrupts > (CONFIG_DEBUG_SHIRQ) leads to false positives. The driver disabled > interrupts on purpose to be sure that they will not fire during device > removal. Surely the

[PATCH] arch: sh: smc37c93x: fix spelling mistake

Fix typo: "triger" --> "trigger" Signed-off-by: Flavio Suligoi --- arch/sh/include/asm/smc37c93x.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/sh/include/asm/smc37c93x.h b/arch/sh/include/asm/smc37c93x.h index f054c30a171a..891f2f8f2fd0 100644 ---

[PATCH] drm/kselftest: fix spellint typo in test-drm_mm.c

This patch fix a spelling typo in test-drm_mm.c Signed-off-by: Masanari Iida --- drivers/gpu/drm/selftests/test-drm_mm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/selftests/test-drm_mm.c b/drivers/gpu/drm/selftests/test-drm_mm.c index

[PATCH 03/13] bpfilter: switch to kernel_write

While pipes don't really need sb_writers projection, __kernel_write is an interface better kept private, and the additional rw_verify_area does not hurt here. Signed-off-by: Christoph Hellwig --- net/bpfilter/bpfilter_kern.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

clean up kernel_{read,write} & friends v4

Hi Al, this series fixes a few issues and cleans up the helpers that read from or write to kernel space buffers, and ensures that we don't change the address limit if we are using the ->read_iter and ->write_iter methods that don't need the changed address limit. I did not add your suggested

[PATCH 04/13] fs: unexport __kernel_write

This is a very special interface that skips sb_writes protection, and not used by modules anymore. Signed-off-by: Christoph Hellwig --- fs/read_write.c | 1 - 1 file changed, 1 deletion(-) diff --git a/fs/read_write.c b/fs/read_write.c index bbfa9b12b15eb7..2c601d853ff3d8 100644 ---

[PATCH 05/13] fs: check FMODE_WRITE in __kernel_write

We still need to check if the fѕ is open write, even for the low-level helper. Signed-off-by: Christoph Hellwig --- fs/read_write.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/read_write.c b/fs/read_write.c index 2c601d853ff3d8..76be155ad98242 100644 --- a/fs/read_write.c +++

[PATCH 06/13] fs: implement kernel_write using __kernel_write

Consolidate the two in-kernel write helpers to make upcoming changes easier. The only difference are the missing call to rw_verify_area in kernel_write, and an access_ok check that doesn't make sense for kernel buffers to start with. Signed-off-by: Christoph Hellwig --- fs/read_write.c | 17

[PATCH] KVM: async_pf: change kvm_setup_async_pf()/kvm_arch_setup_async_pf() return type to bool

Unlike normal 'int' functions returning '0' on success, kvm_setup_async_pf()/ kvm_arch_setup_async_pf() return '1' when a job to handle page fault asynchronously was scheduled and '0' otherwise. To avoid the confusion change return type to 'bool'. No functional change intended. Suggested-by:

[PATCH 09/13] fs: add a __kernel_read helper

This is the counterpart to __kernel_write, and skip the rw_verify_area call compared to kernel_read. Signed-off-by: Christoph Hellwig --- fs/read_write.c| 21 + include/linux/fs.h | 1 + 2 files changed, 22 insertions(+) diff --git a/fs/read_write.c b/fs/read_write.c

[PATCH v2] fs: Do not check if there is a fsnotify watcher on pseudo inodes

Changelog since v1 o Updated changelog The kernel uses internal mounts created by kern_mount() and populated with files with no lookup path by alloc_file_pseudo for a variety of reasons. An example of such a mount is for anonymous pipes. For pipes, every vfs_write regardless of filesystem,

[PATCH 10/13] integrity/ima: switch to using __kernel_read

__kernel_read has a bunch of additional sanity checks, and this moves the set_fs out of non-core code. Signed-off-by: Christoph Hellwig --- security/integrity/iint.c | 14 +- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/security/integrity/iint.c

[PATCH 07/13] fs: remove __vfs_write

Fold it into the two callers. Signed-off-by: Christoph Hellwig --- fs/read_write.c | 46 ++ 1 file changed, 22 insertions(+), 24 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c index 9d50d3cec017d8..f81e15c95f576c 100644 ---

[PATCH 13/13] fs: don't change the address limit for ->read_iter in __kernel_read

If we read to a file that implements ->read_iter there is no need to change the address limit if we send a kvec down. Implement that case, and prefer it over using plain ->read with a changed address limit if available. Signed-off-by: Christoph Hellwig --- fs/read_write.c | 24

[PATCH 11/13] fs: implement kernel_read using __kernel_read

Consolidate the two in-kernel read helpers to make upcoming changes easier. The only difference are the missing call to rw_verify_area in kernel_read, and an access_ok check that doesn't make sense for kernel buffers to start with. Signed-off-by: Christoph Hellwig --- fs/read_write.c | 13

[PATCH 12/13] fs: remove __vfs_read

Fold it into the two callers. Signed-off-by: Christoph Hellwig --- fs/read_write.c| 43 +-- include/linux/fs.h | 1 - 2 files changed, 21 insertions(+), 23 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c index

[PATCH 08/13] fs: don't change the address limit for ->write_iter in __kernel_write

If we write to a file that implements ->write_iter there is no need to change the address limit if we send a kvec down. Implement that case, and prefer it over using plain ->write with a changed address limit if available. Signed-off-by: Christoph Hellwig --- fs/read_write.c | 31

[PATCH 02/13] autofs: switch to kernel_write

While pipes don't really need sb_writers projection, __kernel_write is an interface better kept private, and the additional rw_verify_area does not hurt here. Signed-off-by: Christoph Hellwig Acked-by: Ian Kent --- fs/autofs/waitq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH 01/13] cachefiles: switch to kernel_write

__kernel_write doesn't take a sb_writers references, which we need here. Signed-off-by: Christoph Hellwig Reviewed-by: David Howells --- fs/cachefiles/rdwr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/cachefiles/rdwr.c b/fs/cachefiles/rdwr.c index

Re: [PATCH 4/5] LSM: Define SELinux function to measure security state

On Mon, Jun 15, 2020 at 7:57 AM Stephen Smalley wrote: > I think I mentioned this on a previous version of these patches, but I > would recommend including more than just the enabled and enforcing > states in your measurement. Other low-hanging fruit would be the > other selinux_state booleans

Re: [PATCH] x86/cpu: Reinitialize IA32_FEAT_CTL MSR on BSP during wakeup

On Mon, Jun 08, 2020 at 10:29:21AM -0700, Sean Christopherson wrote: > On Mon, Jun 08, 2020 at 11:12:35AM +0100, Liam Merwick wrote: > > On 05/06/2020 21:07, Sean Christopherson wrote: > > >Reinitialize IA32_FEAT_CTL on the BSP during wakeup to handle the case > > >where firmware doesn't

Re: [PATCH 2/2] iommu/amd: Move Kconfig and Makefile bits down into amd directory

Reviewed-by: Suravee Suthikulpanit Thanks, Suravee On 6/13/20 6:11 AM, Jerry Snitselaar wrote: Move AMD Kconfig and Makefile bits down into the amd directory with the rest of the AMD specific files. Cc: Joerg Roedel Cc: Suravee Suthikulpanit Signed-off-by: Jerry Snitselaar ---

Re: [PATCH v32 00/21] Intel SGX foundations

Looks like we missed the boat for 5.8. Can we get this ready for 5.9? -- Jethro Beekman | Fortanix On 2020-06-01 09:51, Jarkko Sakkinen wrote: > Intel(R) SGX is a set of CPU instructions that can be used by applications > to set aside private regions of code and data. The code outside the

Re: [PATCH] coccinelle: misc: add array_size_dup script to detect missed overflow checks

I suggest to avoid a typo in the previous patch subject. … > +virtual context > +virtual report > +virtual org +virtual context, report, org Is such a SmPL code variant more succinct? … > +@as_next@ > +expression subE1 <= as.E1; > +expression as.E1; … I propose to reduce the repetition of

[PATCH v12 0/6] powerpc/papr_scm: Add support for reporting nvdimm health

Changes since v11 [1]: * Minor update to 'papr_pdsm.h' fixing a misleading comment about 'possible' padding being added by GCC which doesn't apply in case structs are marked as __packed. * Fix the order of initialization of 'struct nd_papr_pdsm_health' in papr_pdsm_health(). * Added acks

[PATCH v12 3/6] powerpc/papr_scm: Fetch nvdimm health information from PHYP

Implement support for fetching nvdimm health information via H_SCM_HEALTH hcall as documented in Ref[1]. The hcall returns a pair of 64-bit bitmap, bitwise-and of which is then stored in 'struct papr_scm_priv' and subsequently partially exposed to user-space via newly introduced dimm specific

[PATCH v12 2/6] seq_buf: Export seq_buf_printf

'seq_buf' provides a very useful abstraction for writing to a string buffer without needing to worry about it over-flowing. However even though the API has been stable for couple of years now its still not exported to kernel loadable modules limiting its usage. Hence this patch proposes update to

[PATCH v12 5/6] ndctl/papr_scm,uapi: Add support for PAPR nvdimm specific methods

Introduce support for PAPR NVDIMM Specific Methods (PDSM) in papr_scm module and add the command family NVDIMM_FAMILY_PAPR to the white list of NVDIMM command sets. Also advertise support for ND_CMD_CALL for the nvdimm command mask and implement necessary scaffolding in the module to handle

[PATCH v12 4/6] powerpc/papr_scm: Improve error logging and handling papr_scm_ndctl()

Since papr_scm_ndctl() can be called from outside papr_scm, its exposed to the possibility of receiving NULL as value of 'cmd_rc' argument. This patch updates papr_scm_ndctl() to protect against such possibility by assigning it pointer to a local variable in case cmd_rc == NULL. Finally the patch

[PATCH v12 6/6] powerpc/papr_scm: Implement support for PAPR_PDSM_HEALTH

This patch implements support for PDSM request 'PAPR_PDSM_HEALTH' that returns a newly introduced 'struct nd_papr_pdsm_health' instance containing dimm health information back to user space in response to ND_CMD_CALL. This functionality is implemented in newly introduced papr_pdsm_health() that

[PATCH v12 1/6] powerpc: Document details on H_SCM_HEALTH hcall

Add documentation to 'papr_hcalls.rst' describing the bitmap flags that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM specification. Cc: "Aneesh Kumar K . V" Cc: Dan Williams Cc: Michael Ellerman Cc: Ira Weiny Acked-by: Ira Weiny Signed-off-by: Vaibhav Jain --- Changelog:

Re: [PATCH RFC v8 02/11] vhost: use batched get_vq_desc version

On Thu, Jun 11, 2020 at 5:22 PM Konrad Rzeszutek Wilk wrote: > > On Thu, Jun 11, 2020 at 07:34:19AM -0400, Michael S. Tsirkin wrote: > > As testing shows no performance change, switch to that now. > > What kind of testing? 100GiB? Low latency? > Hi Konrad. I tested this version of the patch:

Re: KCSAN Support on ARM64 Kernel

On Mon, 14 Oct 2019 at 11:31, Marco Elver wrote: > My plan was to send patches upstream within the month. [...] > On Mon, 14 Oct 2019 at 11:30, wrote: [...] > > When can we expect upstream of KCSAN on kernel mainline. Any timeline? [...] > > > > Can you please tell me if KCSAN is supported on

Re: [PATCH v2 1/3] spi: spi-fsl-dspi: Fix external abort on interrupt in exit paths

On Mon, Jun 15, 2020 at 10:17:07AM +0200, Marc Kleine-Budde wrote: > On 6/15/20 10:07 AM, Krzysztof Kozlowski wrote: > > If interrupt comes late, during probe error path or device remove (could > > be triggered with CONFIG_DEBUG_SHIRQ), the interrupt handler > > dspi_interrupt() will access

Re: [PATCH v7 01/13] tools/libperf: introduce notion of static polled file descriptors

On Mon, Jun 15, 2020 at 08:20:38AM +0300, Alexey Budankov wrote: > > On 08.06.2020 19:07, Jiri Olsa wrote: > > On Mon, Jun 08, 2020 at 12:54:31PM +0300, Alexey Budankov wrote: > >> > >> On 08.06.2020 11:43, Jiri Olsa wrote: > >>> On Mon, Jun 08, 2020 at 11:08:56AM +0300, Alexey Budankov wrote: >

RE: [PATCH v3 0/2] Resolve revision handling and add support for DA silicon

On 17 April 2020 11:56, Adam Thomson wrote: > This patch set fixes the currently broken revision handling in the driver's > i2c_probe() function and then adds DA support to existing permitted revisions. Do I need to resend this patch, or will you still pick up the original mail submission from

Re: [PATCH v2] SUNRPC: Add missing definition of ARCH_IMPLEMENTS_FLUSH_DCACHE_PAGE

> On Jun 15, 2020, at 2:25 AM, Christophe Leroy > wrote: > > Even if that's only a warning, not including asm/cacheflush.h > leads to svc_flush_bvec() being empty allthough powerpc defines > ARCH_IMPLEMENTS_FLUSH_DCACHE_PAGE. > > CC net/sunrpc/svcsock.o > net/sunrpc/svcsock.c:227:5:

Re: [PATCH 05/13] fs: check FMODE_WRITE in __kernel_write

On Mon, Jun 15, 2020 at 02:12:49PM +0200, Christoph Hellwig wrote: > We still need to check if the fѕ is open write, even for the low-level > helper. Do we need the analogous check for FMODE_READ in the __kernel_read() patch? > @@ -505,6 +505,8 @@ ssize_t __kernel_write(struct file *file, const

Re: [PATCH] Staging: rtl8712: Addressed checkpatch.pl issues related to macro parameter wrapping in parentheses.

On Mon, Jun 15, 2020 at 10:28:51AM +0100, Ricardo Ferreira wrote: > On Sun, 14 Jun 2020 at 15:05, Greg Kroah-Hartman > wrote: > > > > On Sun, Jun 14, 2020 at 02:51:25PM +0100, Ricardo Ferreira wrote: > > > #define init_h2fwcmd_w_parm_no_rsp(pcmd, pparm, code) \ > > > do {\ > > > -

Re: [PATCH v1 RFC 1/2] spi: introduce fallback to pio

On Sun, Jun 14, 2020 at 01:04:57PM +, Robin Gong wrote: > On 2020/06/12 22:16 Mark Brown wrote: > > On Fri, Jun 12, 2020 at 01:48:41PM +, Robin Gong wrote: > > > On 2020/06/12 18:14 Mark Brown wrote: Please delete unneeded context from mails when replying. Doing this makes it much

Re: [PATCH v2] Staging: rtl8712: Addressed checkpatch.pl issues related to macro parameter wrapping in parentheses.

On Sun, Jun 14, 2020 at 06:31:46PM +0100, Ricardo Ferreira wrote: > Attempting to wet my feet in kernel patch submission by submitting a > checkstyle > fix for the rtl8712 driver. > > Signed-off-by: Ricardo Ferreira > --- What changed from v1? Always put that below the --- line, so please fix

[PATCH v2 1/1] s390: virtio: let arch accept devices without IOMMU feature

An architecture protecting the guest memory against unauthorized host access may want to enforce VIRTIO I/O device protection through the use of VIRTIO_F_IOMMU_PLATFORM. Let's give a chance to the architecture to accept or not devices without VIRTIO_F_IOMMU_PLATFORM. Signed-off-by: Pierre Morel

RE: [PATCH v2 00/15] vfio: expose virtual Shared Virtual Addressing to VMs

> From: Stefan Hajnoczi > Sent: Monday, June 15, 2020 6:02 PM > > On Thu, Jun 11, 2020 at 05:15:19AM -0700, Liu Yi L wrote: > > Shared Virtual Addressing (SVA), a.k.a, Shared Virtual Memory (SVM) on > > Intel platforms allows address space sharing between device DMA and > > applications. SVA can

[PATCH v2 0/1] s390: virtio: let's arch choose to accept devices without IOMMU feature

An architecture protecting the guest memory against unauthorized host access may want to enforce VIRTIO I/O device protection through the use of VIRTIO_F_IOMMU_PLATFORM. Let's give a chance to the architecture to accept or not devices without VIRTIO_F_IOMMU_PLATFORM. Pierre Morel (1): s390:

Re: [PATCH 1/3] dt-bindings: sound: Document wm8994 endpoints

On Sun, Jun 14, 2020 at 01:24:09PM -0700, Jonathan Bakker wrote: > The wm8994 exposes several inputs and outputs that can be used by > machine drivers in their routing. Add them to the documention so > they don't have been duplicated in any machine drivers bindings. Please submit patches using

[PATCH] pinctrl: qcom: sc7180: Make gpio28 non wakeup capable

The PDC irqchip driver currently does not handle dual-edge interrupts, and we have atleast one board with sc7180 designed to configure gpio28 as a dual-edge interrupt. This interrupt is however not expected to be wakeup capable, so an easy way to fix this, seems to be to make this gpio non wakeup

[RFC PATCH] serial: samsung: Re-factors UART IRQ resource for various Samsung SoC

In few older Samsung SoCs like s3c2410, s3c2412 and s3c2440, UART IP is having 2 interrupt lines. However, in other SoCs like s3c6400, s5pv210, exynos5433, and exynos4210 UART is having only 1 interrupt line. Due to this, "platform_get_irq(platdev, 1)" call in the driver gives the following

[PATCH v13 1/6] powerpc: Document details on H_SCM_HEALTH hcall

Add documentation to 'papr_hcalls.rst' describing the bitmap flags that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM specification. Cc: "Aneesh Kumar K . V" Cc: Dan Williams Cc: Michael Ellerman Cc: Ira Weiny Acked-by: Ira Weiny Signed-off-by: Vaibhav Jain --- Changelog:

[PATCH] pinctrl: stm32: use the hwspin_lock_timeout_in_atomic() API

From: Fabien Dessenne Use the hwspin_lock_timeout_in_atomic() API which is the most appropriated here. Indeed: - hwspin_lock_() is called after spin_lock_irqsave() - the hwspin_lock_timeout() API relies on jiffies count which won't work if IRQs are disabled which is the case here.

[PATCH v13 0/6] powerpc/papr_scm: Add support for reporting nvdimm health

Changes since v12 [1]: * Fixed the clang warning regarding variable length object' being not at the end of the 'struct nd_pdsm_cmd_pkg' by introducing a new layout. * Removed instance of 'struct nd_cmd_pkg hdr' from 'struct nd_pdsm_cmd_pkg' and renamed the struct to 'struct nd_pkg_pdsm' to

Re: [PATCH] ARM: dts: am5729: beaglebone-ai: fix rgmii phy-mode

On Mon, Jun 15, 2020 at 12:34:57PM +0300, Grygorii Strashko wrote: > > > On 12/06/2020 01:09, Drew Fustini wrote: > > Since commit cd28d1d6e52e ("net: phy: at803x: Disable phy delay for > > RGMII mode") the networking is broken on the BeagleBone AI which has > > the AR8035 PHY for Gigabit

[PATCH v13 3/6] powerpc/papr_scm: Fetch nvdimm health information from PHYP

Implement support for fetching nvdimm health information via H_SCM_HEALTH hcall as documented in Ref[1]. The hcall returns a pair of 64-bit bitmap, bitwise-and of which is then stored in 'struct papr_scm_priv' and subsequently partially exposed to user-space via newly introduced dimm specific

[PATCH v13 2/6] seq_buf: Export seq_buf_printf

'seq_buf' provides a very useful abstraction for writing to a string buffer without needing to worry about it over-flowing. However even though the API has been stable for couple of years now its still not exported to kernel loadable modules limiting its usage. Hence this patch proposes update to

[PATCH v13 5/6] ndctl/papr_scm,uapi: Add support for PAPR nvdimm specific methods

Introduce support for PAPR NVDIMM Specific Methods (PDSM) in papr_scm module and add the command family NVDIMM_FAMILY_PAPR to the white list of NVDIMM command sets. Also advertise support for ND_CMD_CALL for the nvdimm command mask and implement necessary scaffolding in the module to handle

[PATCH v13 4/6] powerpc/papr_scm: Improve error logging and handling papr_scm_ndctl()

Since papr_scm_ndctl() can be called from outside papr_scm, its exposed to the possibility of receiving NULL as value of 'cmd_rc' argument. This patch updates papr_scm_ndctl() to protect against such possibility by assigning it pointer to a local variable in case cmd_rc == NULL. Finally the patch

[PATCH v13 6/6] powerpc/papr_scm: Implement support for PAPR_PDSM_HEALTH

This patch implements support for PDSM request 'PAPR_PDSM_HEALTH' that returns a newly introduced 'struct nd_papr_pdsm_health' instance containing dimm health information back to user space in response to ND_CMD_CALL. This functionality is implemented in newly introduced papr_pdsm_health() that

Re: [PATCH] i2c: mediatek: Add i2c support for continuous mode

On Mon, Jun 15, 2020 at 06:40:29PM +0800, qiangming.xia wrote: > Hi, Wolfram > Do you have time to take a look at this? Thanks. Please resend and CC Qii Wang who is now the maintainer of this driver. signature.asc Description: PGP signature

Re: [PATCH v7 0/4] Introduce the for_each_set_clump macro

On Mon, May 25, 2020 at 3:06 PM Bartosz Golaszewski wrote: > > niedz., 24 maj 2020 o 07:00 Syed Nayyar Waris > napisał(a): > > > > Hello Linus, > > > > Since this patchset primarily affects GPIO drivers, would you like > > to pick it up through your GPIO tree? > > > > This patchset introduces a

Re: [PATCH v12 1/6] powerpc: Document details on H_SCM_HEALTH hcall

This accidently got reposted. Please ignore. Vaibhav Jain writes: > Add documentation to 'papr_hcalls.rst' describing the bitmap flags > that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM > specification. > > Cc: "Aneesh Kumar K . V" > Cc: Dan Williams > Cc: Michael Ellerman >

Re: [PATCH v12 0/6] powerpc/papr_scm: Add support for reporting nvdimm health

This accidently got reposted. Please ignore. v13 version of the patch series located at https://lore.kernel.org/linux-nvdimm/20200615124407.32596-1-vaib...@linux.ibm.com Vaibhav Jain writes: > Changes since v11 [1]: > * Minor update to 'papr_pdsm.h' fixing a misleading comment about >

Re: [RFC PATCH] serial: samsung: Re-factors UART IRQ resource for various Samsung SoC

On Mon, Jun 15, 2020 at 05:56:09PM +0530, Tamseel Shams wrote: > In few older Samsung SoCs like s3c2410, s3c2412 > and s3c2440, UART IP is having 2 interrupt lines. > However, in other SoCs like s3c6400, s5pv210, > exynos5433, and exynos4210 UART is having only 1 > interrupt line. Due to this,

[PATCH v8 0/4] Introduce the for_each_set_clump macro

Hello Linus, Since this patchset primarily affects GPIO drivers, would you like to pick it up through your GPIO tree? This patchset introduces a new generic version of for_each_set_clump. The previous version of for_each_set_clump8 used a fixed size 8-bit clump, but the new generic version can

[PATCH v8 1/4] bitops: Introduce the for_each_set_clump macro

This macro iterates for each group of bits (clump) with set bits, within a bitmap memory region. For each iteration, "start" is set to the bit offset of the found clump, while the respective clump value is stored to the location pointed by "clump". Additionally, the bitmap_get_value and

[PATCH v8 2/4] lib/test_bitmap.c: Add for_each_set_clump test cases

The introduction of the generic for_each_set_clump macro need test cases to verify the implementation. This patch adds test cases for scenarios in which clump sizes are 8 bits, 24 bits, 30 bits and 6 bits. The cases contain situations where clump is getting split at the word boundary and also when

[PATCH 13/16] initramfs: simplify clean_rootfs

Just use d_genocide instead of iterating through the root directory with cumbersome userspace-like APIs. This also ensures we actually remove files that are not direct children of the root entry, which the old code failed to do. Fixes: df52092f3c97 ("fastboot: remove duplicate

[PATCH 03/16] md: replace the RAID_AUTORUN ioctl with a direct function call

Instead of using a spcial RAID_AUTORUN ioctl that only exists for non-modular builds and is only called from the early init code, just call the actual function directly. Signed-off-by: Christoph Hellwig --- drivers/md/md-autodetect.c | 10 ++ drivers/md/md.c| 14

[PATCH 08/16] initrd: remove support for multiple floppies

Remove the special handling for multiple floppies in the initrd code. No one should be using floppies for booting these days. (famous last words..) Signed-off-by: Christoph Hellwig --- arch/arm/kernel/atags_parse.c | 2 - arch/sh/kernel/setup.c| 2 - arch/sparc/kernel/setup_32.c | 2

[PATCH 15/16] init: open code setting up stdin/stdout/stderr

Don't rely on the implicit set_fs(KERNEL_DS) for ksys_open to work, but instead open a struct file for /dev/console and then install it as FD 0/1/2 manually. Signed-off-by: Christoph Hellwig --- fs/file.c| 7 +-- include/linux/syscalls.h | 1 - init/main.c |

[PATCH 01/16] init: remove the bstat helper

The only caller of the bstat function becomes cleaner and simpler when open coding the function. Signed-off-by: Christoph Hellwig --- init/do_mounts.h| 10 -- init/do_mounts_md.c | 8 2 files changed, 4 insertions(+), 14 deletions(-) diff --git a/init/do_mounts.h

[PATCH v8 3/4] gpio: thunderx: Utilize for_each_set_clump macro

This patch reimplements the thunderx_gpio_set_multiple function in drivers/gpio/gpio-thunderx.c to use the new for_each_set_clump macro. Instead of looping for each bank in thunderx_gpio_set_multiple function, now we can skip bank which is not set and save cycles. Cc: Robert Richter Cc: Bartosz

[PATCH 16/16] fs: remove ksys_open

Just open code it in the two callers. Signed-off-by: Christoph Hellwig --- fs/open.c| 11 --- include/linux/syscalls.h | 11 --- 2 files changed, 8 insertions(+), 14 deletions(-) diff --git a/fs/open.c b/fs/open.c index 6348173532e663..4375a5a8e726ea 100644 ---

[PATCH 10/16] initrd: switch initrd loading to struct file based APIs

There is no good reason to mess with file descriptors from in-kernel code, switch the initrd loading to struct file based read and writes instead. Signed-off-by: Christoph Hellwig --- fs/read_write.c | 2 +- include/linux/syscalls.h | 1 - init/do_mounts_rd.c | 82

[PATCH 12/16] initramfs: remove the populate_initrd_image and clean_rootfs stubs

If initrd support is not enable just print the warning directly instead of hiding the fact that we just failed behind two stub functions. Signed-off-by: Christoph Hellwig --- init/initramfs.c | 15 --- 1 file changed, 4 insertions(+), 11 deletions(-) diff --git a/init/initramfs.c

[PATCH 1/2] pinctrl: stm32: don't print an error on probe deferral during clock get

From: Etienne Carriere Change STM32 pinctrl driver to not print an error trace when probe is deferred due to clock resource. Probe defer issue (for clocks) could occur during bank registering when some banks have already been registered. In this case banks already registered should be released.

[PATCH 2/2] pinctrl: stm32: defer probe if reset resource is not yet ready

From: Etienne Carriere Defer probe when pin controller reset is defined in the system resources but not yet probed. Signed-off-by: Etienne Carriere Signed-off-by: Alexandre Torgue diff --git a/drivers/pinctrl/stm32/pinctrl-stm32.c b/drivers/pinctrl/stm32/pinctrl-stm32.c index

[PATCH 0/2] pinctrl: stm32: add changes to better manage

Hi, Clocks and resets for GPIO banks could be defined but not yet ready when stm32 pinctrl is probed. This series adds changes to manage probe defer when a clock or a reset is not yet registered in the system. regards alex Etienne Carriere (2): pinctrl: stm32: don't print an error on probe

[PATCH 14/16] initramfs: switch initramfs unpacking to struct file based APIs

There is no good reason to mess with file descriptors from in-kernel code, switch the initramfs unpacking to struct file based write instead. As we don't have nice helper for chmod or chown on a struct file or struct path use the pathname based ones instead there. This causes additional (cached)

[PATCH 09/16] initrd: remove the BLKFLSBUF call in handle_initrd

BLKFLSBUF used to be overloaded for the ramdisk driver to free the whole ramdisk, which was completely different behavior compared to all other drivers. But this magic overload got removed in commit ff26956875c2 ("brd: remove support for BLKFLSBUF"), so this call is entirely pointless now.

[PATCH 11/16] initrd: mark init_linuxrc as __init

Signed-off-by: Christoph Hellwig --- init/do_mounts_initrd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/init/do_mounts_initrd.c b/init/do_mounts_initrd.c index e4f88e9e1c0839..57ad5b2da8f5f5 100644 --- a/init/do_mounts_initrd.c +++ b/init/do_mounts_initrd.c @@ -56,7

[PATCH v8 4/4] gpio: xilinx: Utilize for_each_set_clump macro

This patch reimplements the xgpio_set_multiple function in drivers/gpio/gpio-xilinx.c to use the new for_each_set_clump macro. Instead of looping for each bit in xgpio_set_multiple function, now we can check each channel at a time and save cycles. Cc: Bartosz Golaszewski Cc: Michal Simek

decruft the early init / initrd / initramfs code

Hi all, this series starts to move the early init code away from requiring KERNEL_DS to be implicitly set during early startup. It does so by first removing legacy unused cruft, and the switches away the code from struct file based APIs to our more usual in-kernel APIs.

[PATCH 02/16] md: move the early init autodetect code to drivers/md/

Just like the NFS and CIFS root code this better lives with the driver it is tightly integrated with. Signed-off-by: Christoph Hellwig --- drivers/md/Makefile | 3 +++ init/do_mounts_md.c => drivers/md/md-autodetect.c | 15 +--

[PATCH 07/16] md: rewrite md_setup_drive to avoid ioctls

md_setup_drive knows it works with md devices, so it is rather pointless to open a file descriptor and issue ioctls. Just call directly into the relevant low-level md routines after getting a handle to the device using blkdev_get_by_dev instead. Signed-off-by: Christoph Hellwig ---

[PATCH 06/16] md: simplify md_setup_drive

Move the loop over the possible arrays into the caller to remove a level of indentation for the whole function. Signed-off-by: Christoph Hellwig --- drivers/md/md-autodetect.c | 203 ++--- 1 file changed, 101 insertions(+), 102 deletions(-) diff --git

[PATCH 04/16] md: remove the autoscan partition re-read

devfs is long gone, and autoscan works just fine without this these days. Signed-off-by: Christoph Hellwig --- drivers/md/md-autodetect.c | 10 -- 1 file changed, 10 deletions(-) diff --git a/drivers/md/md-autodetect.c b/drivers/md/md-autodetect.c index 0eb746211ed53c..6bc9b734eee6ff

[PATCH 05/16] md: remove the kernel version of md_u.h

mdp_major can just move to drivers/md/md.h. Signed-off-by: Christoph Hellwig --- drivers/md/md.h | 1 + include/linux/raid/md_u.h | 13 - 2 files changed, 1 insertion(+), 13 deletions(-) delete mode 100644 include/linux/raid/md_u.h diff --git a/drivers/md/md.h

Re: [PATCH v13 2/6] seq_buf: Export seq_buf_printf

On Mon, Jun 15, 2020 at 06:14:03PM +0530, Vaibhav Jain wrote: > 'seq_buf' provides a very useful abstraction for writing to a string > buffer without needing to worry about it over-flowing. However even > though the API has been stable for couple of years now its still not > exported to kernel

Re: [PATCH v2 1/3] spi: spi-fsl-dspi: Fix external abort on interrupt in exit paths

On Mon, 15 Jun 2020 at 15:35, Mark Brown wrote: > > > Indeed. The upshot of all this is that the interrupt needs to be freed > not disabled before the clocks are disabled, or some other mechanism > needs to be used to ensure that the interrupt handler won't attempt to > access the hardware when

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