Add DT bindings for AMS AS73211 XYZ True Color Sensor.
Signed-off-by: Christian Eggers
Reviewed-by: Rob Herring
---
.../bindings/iio/light/ams,as73211.yaml | 54 +++
1 file changed, 54 insertions(+)
create mode 100644
Support for AMS AS73211 JENCOLOR(R) Digital XYZ Sensor.
This driver has no built-in trigger. In order for making triggered
measurements, an external (software) trigger driver like
iio-trig-hrtimer or iio-trig-sysfs is required.
The sensor supports single and continuous measurement modes. The
This is a patch for managing L2P map in HPB module.
The HPB divides logical addresses into several regions. A region consists
of several sub-regions. The sub-region is a basic unit where L2P mapping is
managed. The driver loads L2P mapping data of each sub-region. The loaded
sub-region is called
Quoting Brendan Higgins (2020-08-04 13:47:45)
> Add a brief blurb saying how and when the kunit_test_suite() macro
> works to the usage documentation.
>
> Signed-off-by: Brendan Higgins
> ---
> Documentation/dev-tools/kunit/usage.rst | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git
On Tue, Aug 4, 2020 at 2:56 PM Shuah Khan wrote:
>
> Please pull the following Kselftest update for Linux 5.9-rc1.
Shortlog? diffstat? And the actual git address to pull from?
I see the attached diff, and I'm sure I could guess what branch you
want me to pull from, but please do a proper pull
On 08/02/20 at 07:35pm, Mike Rapoport wrote:
> From: Mike Rapoport
>
> * Replace magic numbers with defines
> * Replace memblock_find_in_range() + memblock_reserve() with
> memblock_phys_alloc_range()
> * Stop checking for low memory size in reserve_crashkernel_low(). The
> allocation from
On Tue, 4 Aug 2020 at 14:24, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.7.13 release.
> There are 116 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
The pull request you sent on Tue, 4 Aug 2020 17:20:24 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
> parisc-5.9-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/95ffa676583b23baed40861d30b65fe31397da00
Thank you!
--
Deet-doot-dot,
The pull request you sent on Mon, 3 Aug 2020 12:26:57 -0600:
> git://git.lwn.net/linux.git tags/docs-5.9
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2324d50d051ec0f14a548e78554fb02513d6dcef
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Tue, 4 Aug 2020 19:12:09 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux tags/printk-for-5.9
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a754292348bf88ec6b55563eca4faba7dcfe2ae7
Thank you!
--
Deet-doot-dot, I am a
This patch changes the read I/O to the HPB read I/O.
If the logical address of the read I/O belongs to active sub-region, the
HPB driver modifies the read I/O command to HPB read. It modifies the UPIU
command of UFS instead of modifying the existing SCSI command.
In the HPB version 1.0, the
On 2020/8/4 上午5:00, Michael S. Tsirkin wrote:
Some legacy guests just assume features are 0 after reset.
We detect that config space is accessed before features are
set and set features to 0 automatically.
Note: some legacy guests might not even access config space, if this is
reported in the
Hello,
syzbot found the following issue on:
HEAD commit:ac3a0c84 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=1088779290
kernel config: https://syzkaller.appspot.com/x/.config?x=c0cfcf935bcc94d2
Hello,
syzbot found the following issue on:
HEAD commit:c0842fbc random32: move the pseudo-random 32-bit definitio..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=142980c290
kernel config: https://syzkaller.appspot.com/x/.config?x=76cacb0fe58c4a1e
Hi,
> On Aug 5, 2020, at 11:57 AM, Li, Aubrey wrote:
>
> On 2020/8/4 0:53, Joel Fernandes wrote:
>> Hi Aubrey,
>>
>> On Mon, Aug 3, 2020 at 4:23 AM Li, Aubrey wrote:
>>>
>>> On 2020/7/1 5:32, Vineeth Remanan Pillai wrote:
Sixth iteration of the Core-Scheduling feature.
Core
Hello,
[adding tglx for irq expertise to Cc]
On Tue, Aug 04, 2020 at 11:16:03AM +0200, Ahmad Fatoum wrote:
> Generic GPIO consumers like gpio-keys use request_any_context_irq()
> to request a threaded handler if irq_settings_is_nested_thread() ==
> true or a hardirq handler otherwise.
>
>
On 2020/8/4 上午5:00, Michael S. Tsirkin wrote:
VDPA sim accesses config space as native endian - this is
wrong since it's a modern device and actually uses LE.
It only supports modern guests so we could punt and
just force LE, but let's use the full virtio APIs since people
tend to copy/paste
the CryptoCell HW has support for ciphers and modes not supported
and used at this time by Linux. Remove the code supporting this
in the ccree ddriver until such time support is added in the kernel.
Gilad Ben-Yossef (2):
crypto: ccree: remove data unit size support
crypto: ccree: remove
Remove the bitlocker cipher which is not supported by
the kernel.
Signed-off-by: Gilad Ben-Yossef
---
drivers/crypto/ccree/cc_cipher.c | 49 ++--
drivers/crypto/ccree/cc_crypto_ctx.h | 1 -
2 files changed, 3 insertions(+), 47 deletions(-)
diff --git
Remove the implementaion of automatic advancement of sector size in IV for
storage ciphers as its use is not supproted by the kernel.
Signed-off-by: Gilad Ben-Yossef
---
drivers/crypto/ccree/cc_cipher.c | 233 +--
drivers/crypto/ccree/cc_driver.h | 1 -
2 files
Christophe Leroy writes:
> On 07/15/2020 01:04 AM, Michael Ellerman wrote:
>> Christophe Leroy writes:
>>> Prepare for switching VDSO to generic C implementation in following
>>> patch. Here, we:
>>> - Modify __get_datapage() to take an offset
>>> - Prepare the helpers to call the C VDSO
On Tue, 4 Aug 2020 18:01:47 -0400 Steven Rostedt wrote:
> On Tue, 4 Aug 2020 11:14:09 +0200
> SeongJae Park wrote:
>
> > From: SeongJae Park
> >
> > This commit adds a tracepoint for DAMON. It traces the monitoring
> > results of each region for each aggregation interval. Using this, DAMON
Support VBUS power control using regulator framework. Enables the regulator
while the port is in host mode.
The "vbus-supply" property can be provided using a usb-connector child node
and standard devicetree bindings.
Signed-off-by: Mike Looijmans
---
v2: Add missing devm_regulator_get call
> On Aug 4, 2020, at 10:32 PM, Andrii Nakryiko
> wrote:
>
> On Tue, Aug 4, 2020 at 8:59 PM Song Liu wrote:
>>
>>
>>
>>> On Aug 4, 2020, at 6:38 PM, Andrii Nakryiko
>>> wrote:
>>>
>>> On Mon, Aug 3, 2020 at 6:18 PM Song Liu wrote:
> On Aug 2, 2020, at 6:40 PM,
When kernel is compiled with CONFIG_HAVE_HW_BREAKPOINT=N, user can
still create watchpoint using PPC_PTRACE_SETHWDEBUG, with limited
functionalities. But, such watchpoints are never firing because of
the missing privilege settings. Fix that.
Reported-by: Pedro Miraglia Franco de Carvalho
On 2020/8/4 上午4:58, Michael S. Tsirkin wrote:
Currently all config space fields are of the type __uXX.
This confuses people and some drivers (notably vdpa)
access them using CPU endian-ness - which only
works well for legacy or LE platforms.
Update virtio_cread/virtio_cwrite macros to allow
Patch #1 fixes a bug when watchpoint is created with ptrace
PPC_PTRACE_SETHWDEBUG and CONFIG_HAVE_HW_BREAKPOINT=N.
patch #2 introduce new feature bit
PPC_DEBUG_FEATURE_DATA_BP_ARCH_31 which will be set when
running on ISA 3.1 compliant machine.
v2:
PPC_DEBUG_FEATURE_DATA_BP_ARCH_31 can be used to determine whether
we are running on an ISA 3.1 compliant machine. Which is needed to
determine DAR behaviour, 512 byte boundary limit etc. This was
requested by Pedro Miraglia Franco de Carvalho for extending
watchpoint features in gdb. Note that
On Tue, 4 Aug 2020 at 14:24, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.56 release.
> There are 86 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
> -Original Message-
> From: Sudeep Holla
> Sent: Tuesday, August 4, 2020 6:20 PM
> To: Jason Liu
> Cc: w...@kernel.org; catalin.mari...@arm.com; as...@kernel.org;
> m...@kernel.org; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 1/1] arm64:
> -Original Message-
> From: Sudeep Holla
> Sent: Tuesday, August 4, 2020 7:39 PM
> To: Marc Zyngier
> Cc: Jason Liu ; catalin.mari...@arm.com;
> w...@kernel.org; linux-kernel@vger.kernel.org; Sudeep Holla
> ; linux-arm-ker...@lists.infradead.org
> Subject: Re: [PATCH 1/1] arm64: kexec:
Hello Liam,
On 03-08-20, 20:08, Liam Beguin wrote:
> Hi Vinod,
>
> On Sat, Jul 18, 2020 at 4:18 PM Liam Beguin wrote:
> >
> >
> > Hi,
> >
> > I sent another patch[1] to try to address this.
> >
> > The issue seems to come from the fact that the parisc architecture
> > doesn't support cmpxchg on
On 8/4/2020 1:13 PM, Vasundhara Volam wrote:
On Mon, Aug 3, 2020 at 7:23 PM Moshe Shemesh wrote:
On 8/3/2020 3:47 PM, Vasundhara Volam wrote:
On Mon, Aug 3, 2020 at 5:47 PM Moshe Shemesh wrote:
On 8/3/2020 1:24 PM, Vasundhara Volam wrote:
On Tue, Jul 28, 2020 at 10:13 PM Jacob Keller
If create a loop device with a backing NVMe SSD, current loop device
driver doesn't correctly set its queue's limits.discard_granularity and
leaves it as 0. If a discard request at LBA 0 on this loop device, in
__blkdev_issue_discard() the calculated req_sects will be 0, and a zero
length discard
On Wed, 8 Jul 2020 at 19:48, Lad Prabhakar
wrote:
>
> Document SDHI controller for RZ/G2H (R8A774E1) SoC, which is compatible
> with R-Car Gen3 SoC family.
>
> Signed-off-by: Lad Prabhakar
> Reviewed-by: Marian-Cristian Rotariu
>
Sorry, but this doesn't apply as the DT doc has been converted
Convert the i.MX rng binding to DT schema format using json-schema.
Signed-off-by: Anson Huang
---
Documentation/devicetree/bindings/rng/imx-rng.txt | 23 --
Documentation/devicetree/bindings/rng/imx-rng.yaml | 50 ++
2 files changed, 50 insertions(+), 23
Hi all,
Today's linux-next merge of the fsinfo tree got a conflict in:
samples/vfs/Makefile
between commit:
2f95ada7fe22 ("kbuild: introduce hostprogs-always-y and userprogs-always-y")
from the kbuid tree and commits:
7e786dee0b78 ("fsinfo: Add fsinfo() syscall to query filesystem
Hi Thomas,
Thomas Gleixner writes:
> Sven Schnelle writes:
>> --- /dev/null
>> +++ b/arch/s390/include/asm/vdso/data.h
>> @@ -0,0 +1,13 @@
>> +/* SPDX-License-Identifier: GPL-2.0 */
>> +#ifndef __S390_ASM_VDSO_DATA_H
>> +#define __S390_ASM_VDSO_DATA_H
>> +
>> +#include
>> +#include
>
> I
On Fri, 17 Jul 2020 at 05:33, Ben Chuang wrote:
>
> From: Ben Chuang
>
> Set SDR104's clock to 205MHz and enable SSC for GL9750 and GL9755
>
> Signed-off-by: Ben Chuang
Applied for next (a while ago), thanks!
Kind regards
Uffe
> ---
> drivers/mmc/host/sdhci-pci-gli.c | 220
On 8/5/20 8:31 AM, Coly Li wrote:
If create a loop device with a backing NVMe SSD, current loop device
driver doesn't correctly set its queue's limits.discard_granularity and
leaves it as 0. If a discard request at LBA 0 on this loop device, in
__blkdev_issue_discard() the calculated req_sects
On Mon, 20 Jul 2020 at 08:12, Masahiro Yamada
wrote:
>
> As commit ef6b75671b5f ("mmc: sdhci-cadence: send tune request twice to
> work around errata") stated, this IP has an errata. This commit applies
> the second workaround for the SD mode.
>
> Due to the errata, it is not possible to use the
On Mon, 20 Jul 2020 at 16:28, Vaibhav Gupta wrote:
>
> Drivers using legacy PM have to manage PCI states and device's PM states
> themselves. They also need to take care of configuration registers.
>
> With improved and powerful support of generic PM, PCI Core takes care of
> above mentioned,
On Mon, 20 Jul 2020 at 02:42, Chun-Hung Wu wrote:
>
> This series provides MediaTek cqhci implementations as below:
> - Refine msdc timeout api to reduce redundant code
> - MediaTek command queue support
> - dt-bindings for mt6779
>
> v1 -> v2:
> - Add more patch details in commit message
On Tue, 21 Jul 2020 at 03:29, shirley her wrote:
>
> Add HW tuning support for SD host controller in SDR104 mode
>
> Signed-off-by: Shirley Her
Applied for next (a while ago), thanks!
Kind regards
Uffe
> ---
> Change in V1:
> 1. Add HW tuning for SDR104 mode instead of SW tuning
> 2. Change
On Tue, 21 Jul 2020 at 03:18, shirley her wrote:
>
> Add bug fix for O2 host controller Seabird1
>
> Signed-off-by: Shirley Her
Applied for next (a while ago), thanks!
> ---
> change in V1:
> 1. Add quriks2 and mmc->caps2 for Seabird1
> 2. Add get_cd support for Seabird1
Future wise, I
On Mon, 20 Jul 2020 at 13:19, Vaibhav Gupta wrote:
>
> Drivers using legacy PM have to manage PCI states and device's PM states
> themselves. They also need to take care of configuration registers.
>
> With improved and powerful support of generic PM, PCI Core takes care of
> above mentioned,
On Wed, 15 Jul 2020 at 09:34, Ben Chuang wrote:
>
> The format string of the task descriptor should be "%016llx".
>
> Signed-off-by: Ben Chuang
Applied for next (a while ago), thanks!
Kind regards
Uffe
> ---
> drivers/mmc/host/cqhci.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
On Tue, 14 Jul 2020 at 21:12, Manish Narani wrote:
>
> The initial code that was adding delays was doing a cast over undefined
> memory. This meant that the delays would be all gibberish.
>
> This change, allocates all delays on the stack, and assigns them from the
> ZynqMP & Versal
Hi Lianbo,
Added Andrew in cc.
On 08/04/20 at 12:49pm, Lianbo Jiang wrote:
> This series includes the following patches, it fixes some corners bugs
> and improves the crash_exclude_mem_range().
>
> [1] [PATCH 1/3] x86/crash: Correct the address boundary of function
> parameters
> [2] [PATCH
Current code enables TCSR.TE and RCSR.RE together, and disable
TCSR.TE and RCSR.RE together in trigger(), which only supports
one operation mode：
1. Rx synchronous with Tx: TE is last enabled and first disabled
Other operation mode need to be considered also:
2. Tx synchronous with Rx: RE is last
refine and clean code for synchronous mode
Shengjiu Wang (3):
ASoC: fsl_sai: Refine enable/disable TE/RE sequence in trigger()
ASoC: fsl_sai: Drop TMR/RMR settings for synchronous mode
ASoC: fsl_sai: Replace synchronous check with fsl_sai_dir_is_synced
changes in v3:
- Add reviewed-by
As new function fsl_sai_dir_is_synced is included for checking if
stream is synced by the opposite stream, then replace the existing
synchronous checking with this new function.
Signed-off-by: Shengjiu Wang
---
sound/soc/fsl/fsl_sai.c | 40
1 file
Tx synchronous with Rx: The RMR is the word mask register, it is used
to mask any word in the frame, it is not relating to clock generation,
So it is no need to be changed when Tx is going to be enabled.
Rx synchronous with Tx: The TMR is the word mask register, it is used
to mask any word in the
Quoting Rajendra Nayak (2020-08-04 04:46:54)
> While most devices within power-domains which support performance states,
> scale the performance state dynamically, some devices might want to
> set a static/default performance state while the device is active.
> These devices typically would also
Convert the i.MX DDR perf binding to DT schema format using json-schema.
Signed-off-by: Anson Huang
---
.../devicetree/bindings/perf/fsl-imx-ddr.txt | 22
.../devicetree/bindings/perf/fsl-imx-ddr.yaml | 39 ++
2 files changed, 39 insertions(+), 22
Quoting Rajendra Nayak (2020-08-04 04:46:56)
> qup-i2c devices on sc7180 are clocked with a fixed clock (19.2 Mhz)
s/Mhz/MHz/
> Though qup-i2c does not support DVFS, it still needs to vote for a
> performance state on 'cx' to satisfy the 19.2 Mhz clock frequency
Capitalize CX?
> requirement.
>
On Tue, Aug 04, 2020 at 10:20:47PM +, Eads, Gage wrote:
> > > +/* [7:0]: device revision, [15:8]: device version */
> > > +#define DLB2_SET_DEVICE_VERSION(ver, rev) (((ver) << 8) | (rev))
> > > +
> > > +static int dlb2_ioctl_get_device_version(struct dlb2_dev *dev,
> > > +
On Tue, 4 Aug 2020 at 14:23, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.137 release.
> There are 52 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
Quoting Guru Das Srinagesh (2020-07-29 09:52:51)
> From: Veera Vegivada
>
> Currently driver is suppressing the negative temperature
> readings from the vadc. Consumers of the thermal zones need
> to read the negative temperature too. Don't suppress the
> readings.
>
> Fixes: c610afaa21d3c6e
Quoting Guru Das Srinagesh (2020-07-29 09:52:52)
> From: David Collins
>
> Add support for TEMP_ALARM GEN2 PMIC peripherals with digital
> major revision 1. This revision utilizes a different temperature
> threshold mapping than earlier revisions.
>
> Signed-off-by: David Collins
>
Rationale:
50 already merged patches of mine.
Signed-off-by: Alexander A. Klimov
---
(Let's try once more - with 50 patches instead of just 2.)
See:
git log --oneline '--author=Alexander A. Klimov '
v5.7..master
CREDITS | 5 +
1 file changed, 5 insertions(+)
diff --git a/CREDITS
On 2020-08-04 22:32, Jiri Olsa wrote:
On Tue, Aug 04, 2020 at 10:57:35AM +0200, Remi Bernon wrote:
SNIP
+
+int dso__load_bfd_symbols(struct dso *dso, const char *debugfile)
+{
+ int err = -1;
+ long symbols_size, symbols_count;
+ asection *section;
+ asymbol **symbols,
On Tue, 4 Aug 2020 at 14:23, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.192 release.
> There are 47 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On Tue, Aug 4, 2020 at 11:26 PM Song Liu wrote:
>
>
>
> > On Aug 4, 2020, at 10:32 PM, Andrii Nakryiko
> > wrote:
> >
> > On Tue, Aug 4, 2020 at 8:59 PM Song Liu wrote:
> >>
> >>
> >>
> >>> On Aug 4, 2020, at 6:38 PM, Andrii Nakryiko
> >>> wrote:
> >>>
> >>> On Mon, Aug 3, 2020 at 6:18 PM
Convert the snvs lpgpr binding to DT schema format using json-schema.
Signed-off-by: Anson Huang
---
.../devicetree/bindings/nvmem/snvs-lpgpr.txt | 21 ---
.../devicetree/bindings/nvmem/snvs-lpgpr.yaml | 31 ++
2 files changed, 31 insertions(+), 21
On Wed, Aug 5, 2020 at 12:02 PM Moshe Shemesh wrote:
>
>
> On 8/4/2020 1:13 PM, Vasundhara Volam wrote:
> > On Mon, Aug 3, 2020 at 7:23 PM Moshe Shemesh wrote:
> >>
> >> On 8/3/2020 3:47 PM, Vasundhara Volam wrote:
> >>> On Mon, Aug 3, 2020 at 5:47 PM Moshe Shemesh wrote:
> On 8/3/2020
On Wed, Aug 05, 2020 at 02:34:13PM +0800, Shengjiu Wang wrote:
> As new function fsl_sai_dir_is_synced is included for checking if
> stream is synced by the opposite stream, then replace the existing
> synchronous checking with this new function.
>
> Signed-off-by: Shengjiu Wang
Acked-by:
From: SeongJae Park
This commit updates the damon user space tool to support the initial
monitoring target regions specification.
Signed-off-by: SeongJae Park
---
tools/damon/_damon.py | 39 +++
tools/damon/record.py | 12 +++-
From: SeongJae Park
Changes from Previous Version
=
- paddr: Support nested iomem sections (Du Fan)
- Rebase on v5.8
Introduction
DAMON[1] programming interface users can extend DAMON for any address space by
configuring the address-space specific low
> On Aug 4, 2020, at 10:47 PM, Andrii Nakryiko
> wrote:
>
> On Tue, Aug 4, 2020 at 9:47 PM Song Liu wrote:
>>
>>
>>
>>> On Aug 4, 2020, at 6:52 PM, Andrii Nakryiko
>>> wrote:
>>>
>>> On Tue, Aug 4, 2020 at 2:01 PM Song Liu wrote:
> On Aug 2, 2020, at 10:10 PM,
From: SeongJae Park
Some users would want to monitor only a part of the entire virtual
memory address space. The '->init_target_regions' callback is therefore
provided, but only programming interface can use it.
For the reason, this commit introduces a new debugfs file,
'init_region'. Users
From: SeongJae Park
This commit adds description of the 'init_regions' feature in the DAMON
usage document.
Signed-off-by: SeongJae Park
---
Documentation/admin-guide/mm/damon/usage.rst | 41 +++-
1 file changed, 39 insertions(+), 2 deletions(-)
diff --git
From: SeongJae Park
This commit adds more test cases for the new feature, 'init_regions'.
Signed-off-by: SeongJae Park
---
mm/damon-test.h | 53 +
1 file changed, 53 insertions(+)
diff --git a/mm/damon-test.h b/mm/damon-test.h
index
From: SeongJae Park
Now the regions can be explicitly set as users want. Therefore checking
the number of gaps doesn't make sense. Remove the condition.
Signed-off-by: SeongJae Park
---
tools/testing/selftests/damon/_chk_record.py | 6 --
1 file changed, 6 deletions(-)
diff --git
From: SeongJae Park
This commit makes the debugfs interface to support the physical memory
monitoring, in addition to the virtual memory monitoring.
Users can do the physical memory monitoring by writing a special
keyword, 'paddr\n' to the 'pids' debugfs file. Then, DAMON will check
the
From: SeongJae Park
This commit implements the four callbacks (->init_target_regions,
->update_target_regions, ->prepare_access_check, and ->check_accesses)
for the basic access monitoring of the physical memory address space.
By setting the callback pointers to point those, users can easily
From: Etienne Carriere
Remove reset controller device reference from the device private
structure since it is used only at probe time and can be discarded
once used to reset the SPI device.
Signed-off-by: Etienne Carriere
Signed-off-by: Alain Volmat
---
drivers/spi/spi-stm32.c | 11
From: SeongJae Park
This commit allows users to record the data accesses on physical memory
address space by passing 'paddr' as target to 'damo-record'. If the
init regions are given, the regions will be monitored. Else, it will
monitor biggest conitguous 'System RAM' region in '/proc/iomem'
Defer the probe operation when a reset controller device is expected
but have not yet been probed.
This change replaces use of devm_reset_control_get_exclusive() with
devm_reset_control_get_optional_exclusive() as reset controller is
optional which is now explicitly stated.
Signed-off-by: Alain
From: SeongJae Park
This commit updates the DAMON user space tool (damo-record) for NUMA
specific physical memory monitoring. With this change, users can
monitor accesses to physical memory of specific NUMA node.
Signed-off-by: SeongJae Park
---
tools/damon/_paddr_layout.py | 147
From: Amelie Delaunay
When transfer is shorter than half of the fifo, set the data packet size
up to transfer size instead of up to half of the fifo.
Check also that threshold is set at least to 1 data frame.
Signed-off-by: Amelie Delaunay
Signed-off-by: Alain Volmat
---
From: Amelie Delaunay
This patch adds pinctrl power management, and reconfigure spi controller
in case of resume.
Signed-off-by: Amelie Delaunay
Signed-off-by: Alain Volmat
---
drivers/spi/spi-stm32.c | 27 ---
1 file changed, 24 insertions(+), 3 deletions(-)
diff
SPI registers content may have been lost upon suspend/resume sequence.
So, always compute and apply the necessary configuration in
stm32_spi_transfer_one_setup routine.
Signed-off-by: Alain Volmat
---
drivers/spi/spi-stm32.c | 42 +-
1 file changed, 17
From: Antonio Borneo
The spi disable could potentially require some time to finish.
It has to be executed at the end of a transfer, but there is
no reason to call it in the irq handler.
Simplify the irq handler by moving out the spi disable. The
synchronization through xfer_completion is used
On Mon, 2020-07-13 at 18:57 -0700, Sean Christopherson wrote:
> Don't attempt to load PDPTRs if EFER.LME=1, i.e. if 64-bit mode is
> enabled. A recent change to reload the PDTPRs when CR0.CD or CR0.NW is
> toggled botched the EFER.LME handling and sends KVM down the PDTPR path
> when is_paging()
From: SeongJae Park
This commit updates the DAMON documents for the physical memory
monitoring support.
Signed-off-by: SeongJae Park
---
Documentation/admin-guide/mm/damon/usage.rst | 42
Documentation/vm/damon/design.rst| 29 +-
From: Amelie Delaunay
Remove flush parameter and check RXWNE or RXPLVL when end of transfer
flag is set.
Signed-off-by: Amelie Delaunay
Signed-off-by: Alain Volmat
---
drivers/spi/spi-stm32.c | 32 ++--
1 file changed, 14 insertions(+), 18 deletions(-)
diff --git
On 0 byte transfer request, return straight from the
xfer function after finalizing the transfer.
Signed-off-by: Alain Volmat
---
drivers/spi/spi-stm32.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/spi/spi-stm32.c b/drivers/spi/spi-stm32.c
index 177f82700de0..b909afd9e99b
Ensure that messages given to transfer_one handler can actually be
handled by it. For that purpose rely on the SPI framework
spi_split_transfers_maxsize function to split messages whenever necessary.
Signed-off-by: Alain Volmat
---
drivers/spi/spi-stm32.c | 14 ++
1 file changed, 14
From: Amelie Delaunay
In irq mode, when cpu is under heavy load and spi speed is set too
high, the irq handler is not fast enough to feed the spi FIFOs.
This does not compromises the data tranferred; the spi clock is
temporarily stopped, the transfer takes longer time and the real
speed is much
From: Amelie Delaunay
To avoid defining shift and mask separately and hand-coding the bit
manipulation, use the bitfield macros.
Signed-off-by: Amelie Delaunay
Signed-off-by: Alain Volmat
---
drivers/spi/spi-stm32.c | 55 -
1 file changed, 18
From: Amelie Delaunay
Replace SPI_1HZ_NS private constant with NSEC_PER_SEC, which is easier
to read and understand.
Signed-off-by: Amelie Delaunay
Signed-off-by: Alain Volmat
---
drivers/spi/spi-stm32.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
From: Amelie Delaunay
Check the expected flags in irq handler instead of all flags set in
status register and clear only flags that are not automatically cleared
by hardware.
In case of Full-Duplex mode, DXP flag is set when RXP and TXP flags are
set. But to avoid 2 different handlings, just add
From: Amelie Delaunay
Fix spi->clk_rate when it is odd to the nearest lowest even value because
minimum SPI divider is 2.
Signed-off-by: Amelie Delaunay
Signed-off-by: Alain Volmat
---
drivers/spi/spi-stm32.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
This serie provides spi-stm32 driver enhancements in various area such as:
- code simplification
- race condition fix
- fixes in case of usage of SPI with DMA
- suspend/resume fixes
- issues triggered by spi-loopback-test
Alain Volmat (4):
spi: stm32-spi: defer probe for reset
spi:
From: Amelie Delaunay
The rx dma is completed "after" the last data is received
from spi. Thus, to avoid loss of rx data, it's mandatory to
wait for the dma callback before tearing down the rx dma in
stm32_spi_disable().
The tx dma is of course already completed when last data is
sent from spi.
From: Antonio Borneo
Accordingly to STM32H7 document RM0433, "mode fault" MODF is
a special mode to handle a spi bus with multiple masters, in
which each master has to "detect" if another master enables
its CS to take control of the bus. Once this is detected,
all other masters has to
From: Amelie Delaunay
Make spurious interrupts visible. We do not expect to receive
them, so rise at least a warning if it happens.
Don't bother repeating the suspended RX messages; to avoid RX
overrun we have set SPI_CR1_MASRX that enables the automatic
suspended RX so, mainly in irq mode,
From: Antonio Borneo
The caller of stm32_spi_transfer_one(), spi_transfer_one_message(),
is waiting for us to call spi_finalize_current_transfer() and will
eventually schedule a new transfer, if available.
We should guarantee that the spi controller is really available
before calling
On PPC64, the TOC pointer needs to be saved and restored.
Suggested-by: Michael Ellerman
Signed-off-by: Christophe Leroy
---
v9: New.
I'm not sure this is really needed, I can't see the VDSO C code doing
anything with r2, at least on ppc64_defconfig.
So I let you decide whether you take it or
1 - 100 of 1106 matches
Mail list logo
