On Wed, Aug 05, 2020 at 12:20:24PM +0800, Baoquan He wrote:
> On 08/02/20 at 07:35pm, Mike Rapoport wrote:
> > From: Mike Rapoport
> >
> > Currently, initrd image is reserved very early during setup and then it
> > might be relocated and re-reserved after the initial physical memory
> > mapping
This series adds support for the AMS AS73211 digital XYZ sensor.
Probably everything is fine now...
Changes in v6:
---
- [2/2] Fixed remaining open points reported by Andy Shevchenko.
Changes in v5:
---
- [1/2] Reviewed by Rob Herring
- [2/2] Added KHZ_PER_HR define
-
Quoting Wesley Cheng (2020-08-03 17:45:20)
> The QCOM SPMI typec driver handles the role and orientation detection, and
> notifies client drivers using the USB role switch framework. It registers
> as a typec port, so orientation can be communicated using the typec switch
> APIs. The driver
Thanks, Ricky.
On 05/08/2020 03:35, 吳昊澄 Ricky wrote:
>
>
>> -Original Message-
>> From: Chris Clayton [mailto:chris2...@googlemail.com]
>> Sent: Tuesday, August 04, 2020 7:52 PM
>> To: 吳昊澄 Ricky; gre...@linuxfoundation.org
>> Cc: LKML; rdun...@infradead.org; philqua...@gmail.com; Arnd
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, Andrii Nakryiko
> >>> wrote:
> >>>
> >>> On Sun, Aug 2, 2020 at 9:47 PM
> -Original Message-
> From: Anson Huang
> Sent: 2020年8月4日 13:38
> To: Richard Zhu ; l.st...@pengutronix.de;
> lorenzo.pieral...@arm.com; r...@kernel.org; bhelg...@google.com;
> shawn...@kernel.org; s.ha...@pengutronix.de; ker...@pengutronix.de;
> feste...@gmail.com;
Hi all,
On Mon, 20 Jul 2020 15:59:17 +1000 Stephen Rothwell
wrote:
>
> Hi all,
>
> Today's linux-next merge of the seccomp tree got a conflict in:
>
> tools/testing/selftests/seccomp/seccomp_bpf.c
>
> between commit:
>
> 4c6614dc86ad ("selftests/seccomp: Check ENOSYS under tracing")
>
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, Andrii Nakryiko
> >>> wrote:
> >>>
> >>> On Sat, Aug 1, 2020 at 1:50 AM Song
This is a patch for the HPB feature.
This patch adds HPB function calls to UFS core driver.
The mininum size of the memory pool used in the HPB is implemented as a
Kconfig parameter (SCSI_UFS_HPB_HOST_MEM), so that it can be configurable.
Reviewed-by: Can Guo
Tested-by: Bean Huo
Signed-off-by:
Enable support for audio-graph based sound card on Jetson-Nano and
Jetson-TX1. Depending on the platform, required I/O interfaces are
enabled.
* Jetson-Nano: Enable I2S3, I2S4, DMIC1 and DMIC2.
* Jetson-TX1: Enable all I2S and DMIC interfaces.
Signed-off-by: Sameer Pujar
---
For open platforms, which can support pluggable audio cards, Codec
endpoint is not fixed always. It actually depends on the compatible
HW module that is going to be connected. From SoC side the given I/O
interface is always available. Hence such links have fixed CPU endpoint
but no Codec endpoint.
The audio-graph driver supports both normal and DPCM DAI links. The
sound cards requiring DPCM DAI link support, use DPCM_SELECTABLE flag
and DAI links are treated as DPCM links depending on the number of
child nodes in a given DAI link.
There is another requirement where multiple ASoC components
Expose a header which describes DT bindings required to use audio-graph
based sound card. All Tegra210 based platforms can include this header
and add platform specific information. Currently, from SoC point of view,
all links are exposed for ADMAIF, AHUB, I2S and DMIC components.
Signed-off-by:
This series proposes following enhancements to audio-graph card driver.
* Support multiple instances of a component.
* Support open platforms with empty Codec endpoint.
* Identify no-pcm DPCM DAI links which can be used in BE<->BE connections.
* Add new compatible to support DPCM based DAI
PCM devices are created for FE dai links with 'no-pcm' flag as '0'.
Such DAI links have CPU component which implement either pcm_construct()
or pcm_new() at component or dai level respectively. Based on this,
current patch exposes a helper function to identify such components
and populate 'no_pcm'
The "prefix" can be defined in DAI link node or it can be specified as
part of the component node itself. Currently "sound-name-prefix" defined
in a component is not taking effect. Actually the property is not getting
parsed. It can be fixed by parsing "sound-name-prefix" property whenever
New compatible "audio-graph-cc-card" is exposed for audio-graph card
driver which allows usage of DAI link chaining and thus connects multiple
components together in a system.
Signed-off-by: Sameer Pujar
---
Documentation/devicetree/bindings/sound/audio-graph-card.txt | 1 +
1 file changed, 1
For multiple instances of components, using DAI name alone for DAI links
is causing conflicts. Components can define multiple DAIs and hence using
just a device name won't help either. Thus DT device node reference and
DAI names are used to uniquely represent DAI link names.
Signed-off-by: Sameer
dpcm_end_walk_at_be() stops the graph walk when first BE is found for
the given FE component. In a component model we may want to connect
multiple DAIs from different components. A new flag is introduced in
'snd_soc_card', which when set allows DAI/component chaining. Later
PCM operations can be
On 2020-08-04 21:20, Xie He wrote:
On Tue, Aug 4, 2020 at 5:43 AM Martin Schiller wrote:
I'm not an expert in the field, but after reading the commit message
and
the previous comments, I'd say that makes sense.
Thanks!
Shouldn't this kernel panic be intercepted by a skb_cow() before the
This is a patch for parameters to be used for UFS features layer and HPB
module.
Reviewed-by: Can Guo
Tested-by: Bean Huo
Signed-off-by: Daejun Park
---
drivers/scsi/ufs/ufs.h | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/scsi/ufs/ufs.h b/drivers/scsi/ufs/ufs.h
On Tue, Aug 04, 2020 at 07:42:34PM +0200, Bartosz Golaszewski wrote:
> On Sat, Jul 25, 2020 at 6:20 AM Kent Gibson wrote:
> >
> > Add a new version of the uAPI to address existing 32/64-bit alignment
> > issues, add support for debounce and event sequence numbers, and provide
> > some future
On Wed, Aug 05, 2020 at 01:03:37PM +0800, Shengjiu Wang wrote:
> > Btw, the new fsl_sai_dir_is_synced() can be probably applied to
> > other places with a followup patch.
> Do you mean move it to the beginning of this file?
There are other existing places testing "sync[tx] && !sync[!tx]"
so you
On August 4, 2020 10:08:08 PM PDT, Borislav Petkov wrote:
>On Tue, Aug 04, 2020 at 09:58:25PM -0700, h...@zytor.com wrote:
>> Because why use an alternative to jump over one instruction?
>>
>> I personally would prefer to have the IRET put out of line
>
>Can't yet - SERIALIZE CPUs are a minority
On Tue, Aug 04, 2020 at 09:58:25PM -0700, h...@zytor.com wrote:
> Because why use an alternative to jump over one instruction?
>
> I personally would prefer to have the IRET put out of line
Can't yet - SERIALIZE CPUs are a minority at the moment.
> and have the call/jmp replaced by SERIALIZE
The pull request you sent on Tue, 04 Aug 2020 08:21:53 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> core-entry-2020-08-04
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d25c8be67481060782d7e8b84bc0d0355922
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Tue, 04 Aug 2020 08:21:58 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86-fsgsbase-2020-08-04
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4da9f3302615f4191814f826054846bf843e24fa
Thank you!
--
Deet-doot-dot,
The pull request you sent on Tue, 04 Aug 2020 08:21:57 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-entry-2020-08-04
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/125cfa0d4d143416ae217c26a72003baae93233d
Thank you!
--
Deet-doot-dot, I am
On Wed, Aug 5, 2020 at 12:13 PM Nicolin Chen wrote:
>
> On Wed, Aug 05, 2020 at 10:23:53AM +0800, Shengjiu Wang wrote:
> > Tx synchronous with Rx:
> > The TCSR.TE is no need to enabled when only Rx is going to be enabled.
> > Check if need to disable RSCR.RE before disabling TCSR.TE.
> >
> > Rx
On Tue, Aug 04, 2020 at 05:29:09PM -0400, Michael S. Tsirkin wrote:
> On Tue, Aug 04, 2020 at 07:20:36PM +0300, Eli Cohen wrote:
> > Hi Michael,
> > please note that this series depends on mlx5 core device driver patches
> > in mlx5-next branch in
> >
On Tue, Aug 04, 2020 at 06:18:47PM +0200, Luca Stefani wrote:
> * late_initcall expects a function to return an integer
Please write a proper sentence for a commit message.
> Signed-off-by: Luca Stefani
> ---
> drivers/ras/cec.c | 9 +
> 1 file changed, 5 insertions(+), 4 deletions(-)
On August 4, 2020 9:48:40 PM PDT, Borislav Petkov wrote:
>On Tue, Aug 04, 2020 at 07:10:59PM -0700, Ricardo Neri wrote:
>> The SERIALIZE instruction gives software a way to force the processor
>to
>> complete all modifications to flags, registers and memory from
>previous
>> instructions and
Convert the NXP lpuart binding to DT schema format using json-schema.
Signed-off-by: Anson Huang
---
.../devicetree/bindings/serial/fsl-lpuart.txt | 43
.../devicetree/bindings/serial/fsl-lpuart.yaml | 79 ++
2 files changed, 79 insertions(+), 43
Convert the i.MX uart binding to DT schema format using json-schema.
Signed-off-by: Anson Huang
---
.../devicetree/bindings/serial/fsl-imx-uart.txt| 40 --
.../devicetree/bindings/serial/fsl-imx-uart.yaml | 92 ++
2 files changed, 92 insertions(+), 40
Convert the MXS auart binding to DT schema format using json-schema.
Signed-off-by: Anson Huang
---
.../devicetree/bindings/serial/fsl-mxs-auart.txt | 53
.../devicetree/bindings/serial/fsl-mxs-auart.yaml | 93 ++
2 files changed, 93 insertions(+), 53
Hi,
On Tue, Aug 4, 2020 at 12:08 AM Stephen Boyd wrote:
>
> I see it takes about 5us per regulator to grab the lock, check that this
> regulator isn't going to do anything for suspend, and then release the
> lock. When that is combined with PMICs that have dozens of regulators we
> get into a
On Aug 4, 2020, at 7:02 PM, brookxu wrote:
>
> Add the needed value to ext4_mb_discard_preallocations trace, so
> we can more easily observe the requested number of trim.
>
> Signed-off-by: Chunguang Xu
IMHO, this should be part of the previous patch that is changing the
API for
On Tue, Aug 4, 2020 at 9:08 PM Eric Biggers wrote:
>
> On Wed, Aug 05, 2020 at 01:47:58PM +1000, Aleksa Sarai wrote:
> > On 2020-08-04, Lokesh Gidra wrote:
> > > when get_unused_fd_flags returns error, ctx will be freed by
> > > userfaultfd's release function, which is indirectly called by
On Wed, Aug 5, 2020 at 12:21 PM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the ftrace tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> kernel/kprobes.c: In function 'kill_kprobe':
> kernel/kprobes.c:1116:33: warning: statement with no effect
On Aug 4, 2020, at 7:02 PM, brookxu wrote:
>
> In the scenario of writing sparse files, the Per-inode prealloc list may
> be very long, resulting in high overhead for ext4_mb_use_preallocated().
> To circumvent this problem, we limit the maximum length of per-inode
> prealloc list to 512 and
On Tue, Aug 04, 2020 at 07:10:59PM -0700, Ricardo Neri wrote:
> The SERIALIZE instruction gives software a way to force the processor to
> complete all modifications to flags, registers and memory from previous
> instructions and drain all buffered writes to memory before the next
> instruction is
> 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, Andrii Nakryiko
>>> wrote:
>>>
>>> On Sun, Aug 2, 2020 at 9:47 PM Song Liu wrote:
> On Aug 2, 2020, at 6:51 PM, Andrii
On Aug 4, 2020, at 7:01 PM, brookxu wrote:
>
> Reorganize the if statement of ext4_mb_release_context(), make it
> easier to read.
>
> Signed-off-by: Chunguang Xu
Reviewed-by: Andreas Dilger
> ---
> fs/ext4/mballoc.c | 27 +--
> 1 file changed, 13 insertions(+), 14
From: Patricia Alfonso
In order to integrate debugging tools like KASAN into the KUnit
framework, add KUnit struct to the current task to keep track of the
current KUnit test.
Signed-off-by: Patricia Alfonso
Reviewed-by: Brendan Higgins
Signed-off-by: David Gow
---
include/linux/sched.h | 4
From: Patricia Alfonso
Include documentation on how to test KASAN using CONFIG_TEST_KASAN_KUNIT
and CONFIG_TEST_KASAN_MODULE.
Signed-off-by: Patricia Alfonso
Signed-off-by: David Gow
Reviewed-by: Andrey Konovalov
Reviewed-by: Dmitry Vyukov
Acked-by: Brendan Higgins
---
From: Patricia Alfonso
Integrate KASAN into KUnit testing framework.
- Fail tests when KASAN reports an error that is not expected
- Use KUNIT_EXPECT_KASAN_FAIL to expect a KASAN error in KASAN
tests
- Expected KASAN reports pass tests and are still printed when
KASAN errors will currently trigger a panic when panic_on_warn is set.
This renders kasan_multishot useless, as further KASAN errors won't be
reported if the kernel has already paniced. By making kasan_multishot
disable this behaviour for KASAN errors, we can still have the benefits
of
This patchset contains everything needed to integrate KASAN and KUnit.
KUnit will be able to:
(1) Fail tests when an unexpected KASAN error occurs
(2) Pass tests when an expected KASAN error occurs
Convert KASAN tests to KUnit with the exception of copy_user_test
because KUnit is unable to test
From: Patricia Alfonso
Transfer all previous tests for KASAN to KUnit so they can be run
more easily. Using kunit_tool, developers can run these tests with their
other KUnit tests and see "pass" or "fail" with the appropriate KASAN
report instead of needing to parse each KASAN report to test
The proposed KUnit test naming guidelines[1] suggest naming KUnit test
modules [suite]_kunit (and hence test source files [suite]_kunit.c).
Rename test_kunit.c to kasan_kunit.c to comply with this, and be
consistent with other KUnit tests.
[1]:
Hello Stephen,
On 8/5/20 12:26 AM, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 95d0c04e0cf9 ("watchdog: f71808e_wdt: remove use of wrong watchdog_info
> option")
>
> Fixes tag
>
> Fixes: 96cb4eb019ce ("watchdog: f71808e_wdt: new watchdog driver for
>
> has these problem(s):
>
>
Christoph's "getting rid of ksys_...() uses under KERNEL_DS" stuff.
One trivial conflict (drivers/md/md.c).
The following changes since commit f8456690ba8eb18ea4714e68554e242a04f65cff:
Merge tag 'clk-fixes-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux into
Hi all,
After merging the ftrace tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
kernel/kprobes.c: In function 'kill_kprobe':
kernel/kprobes.c:1116:33: warning: statement with no effect [-Wunused-value]
1116 | #define disarm_kprobe_ftrace(p) (-ENODEV)
|
On 08/02/20 at 07:35pm, Mike Rapoport wrote:
> From: Mike Rapoport
>
> Currently, initrd image is reserved very early during setup and then it
> might be relocated and re-reserved after the initial physical memory
> mapping is created. The "late" reservation of memblock verifies that mapped
>
On Wed, Aug 05, 2020 at 10:23:53AM +0800, Shengjiu Wang wrote:
> Tx synchronous with Rx:
> The TCSR.TE is no need to enabled when only Rx is going to be enabled.
> Check if need to disable RSCR.RE before disabling TCSR.TE.
>
> Rx synchronous with Tx:
> The RCSR.RE is no need to enabled when only
Hi all,
On Fri, 3 Jul 2020 14:35:50 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the kspp tree got a conflict in:
>
> drivers/gpu/drm/drm_edid.c
>
> between commit:
>
> 948de84233d3 ("drm : Insert blank lines after declarations.")
>
> from the drm-misc tree and commit:
On Wed, Aug 05, 2020 at 01:47:58PM +1000, Aleksa Sarai wrote:
> On 2020-08-04, Lokesh Gidra wrote:
> > when get_unused_fd_flags returns error, ctx will be freed by
> > userfaultfd's release function, which is indirectly called by fput().
> > Also, if anon_inode_getfile_secure() returns an error,
Hi all,
On Tue, 28 Jul 2020 18:45:20 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the kspp tree got a conflict in:
>
> drivers/infiniband/core/uverbs_cmd.c
>
> between commit:
>
> 29f3fe1d6854 ("RDMA/uverbs: Remove redundant assignments")
>
> from the rdma tree and
Hi all,
On Mon, 27 Jul 2020 19:27:21 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the kspp tree got a conflict in:
>
> net/ipv6/ip6_flowlabel.c
>
> between commit:
>
> ff6a4cf214ef ("net/ipv6: split up ipv6_flowlabel_opt")
>
> from the net-next tree and commit:
>
>
Changelog:
v6 -> v7
1. Remove UFS feature layer.
2. Cleanup for sparse error.
v5 -> v6
Change base commit to b53293fa662e28ae0cdd40828dc641c09f133405
v4 -> v5
Delete unused macro define.
v3 -> v4
1. Cleanup.
v2 -> v3
1. Add checking input module parameter value.
2. Change base commit from
> 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, Andrii Nakryiko
>>> wrote:
>>>
>>> On Sat, Aug 1, 2020 at 1:50 AM Song Liu wrote:
>>
>> [...]
>>
>>>
};
LIBBPF_API
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 scheduling is a feature that allows only trusted tasks to run
>>>
On 08/02/20 at 07:35pm, Mike Rapoport wrote:
> From: Mike Rapoport
>
> There are several occurrences of the following pattern:
>
> for_each_memblock(memory, reg) {
> start_pfn = memblock_region_memory_base_pfn(reg);
> end_pfn =
If j1939_xtp_rx_dat_one() receive last frame of multipacket broadcast
message, j1939_session_timers_cancel() should be called to cancel
rxtimer.
Fixes: 9d71dd0c7009 ("can: add support of SAE J1939 protocol")
Signed-off-by: Zhang Changzhong
---
net/can/j1939/transport.c | 1 +
1 file changed, 1
According to SAE J1939/21 (Chapter 5.12.3 and APPENDIX C), for transmit
side the required time interval between packets of a multipacket
broadcast message is 50 to 200 ms, the responder shall use a timeout of
250ms (provides margin allowing for the maximumm spacing of 200ms). For
receive side a
If timeout occurs, j1939_tp_rxtimer() first calls hrtimer_start() to
restart rxtimer, and then calls __j1939_session_cancel() to set
session->state = J1939_SESSION_WAITING_ABORT. At next timeout
expiration, because of the J1939_SESSION_WAITING_ABORT session state
j1939_tp_rxtimer() will call
Zhang Changzhong (4):
can: j1939: fix support for multipacket broadcast message
can: j1939: cancel rxtimer on multipacket broadcast session complete
can: j1939: abort multipacket broadcast session when timeout occurs
can: j1939: add rxtimer for multipacket broadcast session
Currently j1939_tp_im_involved_anydir() in j1939_tp_recv() check the
previously set flags J1939_ECU_LOCAL_DST and J1939_ECU_LOCAL_SRC of
incoming skb, thus multipacket broadcast message was aborted by
receive side because it may come from remote ECUs and have no exact
dst address. Similarly,
On 08/02/20 at 07:35pm, Mike Rapoport wrote:
> From: Mike Rapoport
>
> The memory size calculation in cma_early_percent_memory() traverses
> memblock.memory rather than simply call memblock_phys_mem_size(). The
> comment in that function suggests that at some point there should have been
> call
On 2020-08-04, Lokesh Gidra wrote:
> when get_unused_fd_flags returns error, ctx will be freed by
> userfaultfd's release function, which is indirectly called by fput().
> Also, if anon_inode_getfile_secure() returns an error, then
> userfaultfd_ctx_put() is called, which calls mmdrop() and frees
On Wed, Aug 05, 2020 at 10:23:52AM +0800, Shengjiu Wang wrote:
> 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
Hi Palmer,
On Tue, 04 Aug 2020 18:17:35 -0700 (PDT) Palmer Dabbelt
wrote:
>
> >> diff --cc arch/riscv/Kconfig
> >> index 76a0cfad3367,f6a3a2bea3d8..
> >> --- a/arch/riscv/Kconfig
> >> +++ b/arch/riscv/Kconfig
> >> @@@ -57,9 -52,6 +57,8 @@@ config RISC
> >>select
when ctx->sqo_mm is zero, io_sq_wq_submit_work() frees 'req'
without deleting it from 'task_list'. After that, 'req' is
accessed in io_ring_ctx_wait_and_kill() which lead to
a use-after-free.
Signed-off-by: Guoyu Huang
---
fs/io_uring.c | 1 +
1 file changed, 1 insertion(+)
diff --git
On Wed, Aug 05, 2020 at 10:57:23AM +0800, 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
>
On 8/3/2020 11:52 PM, Rob Herring wrote:
On Mon, Aug 3, 2020 at 2:28 AM Rohit Kumar wrote:
Thanks Rob for reviewing
On 7/23/2020 10:46 PM, Rob Herring wrote:
On Wed, Jul 22, 2020 at 04:01:55PM +0530, Rohit kumar wrote:
Update lpass-cpu binding with yaml formats.
Signed-off-by: Rohit
Hi Lakshmi,
There's still a number of other patch sets needing to be reviewed
before my getting to this one. The comment below is from a high level.
On Tue, 2020-08-04 at 17:43 -0700, Lakshmi Ramasubramanian wrote:
> Critical data structures of security modules need to be measured to
> enable
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 442489c219235991de86d0277b5d859ede6d8792
commit: a94e4f24ec836c8984f839594bad7454184975b1 MIPS: init: Drop boot_mem_map
date: 12 months ago
config: mips-randconfig-m031-20200805 (attached as .config)
On 05/08/2020 13:04, Leonardo Bras wrote:
> On LoPAR "DMA Window Manipulation Calls", it's recommended to remove the
> default DMA window for the device, before attempting to configure a DDW,
> in order to make the maximum resources available for the next DDW to be
> created.
>
> This is a
On 05/08/2020 13:04, Leonardo Bras wrote:
> Move the window-removing part of remove_ddw into a new function
> (remove_dma_window), so it can be used to remove other DMA windows.
>
> It's useful for removing DMA windows that don't create DIRECT64_PROPNAME
> property, like the default DMA window
On 05/08/2020 13:04, Leonardo Bras wrote:
> From LoPAR level 2.8, "ibm,ddw-extensions" index 3 can make the number of
> outputs from "ibm,query-pe-dma-windows" go from 5 to 6.
>
> This change of output size is meant to expand the address size of
> largest_available_block PE TCE from 32-bit to
On 05/08/2020 13:04, Leonardo Bras wrote:
> Create defines to help handling ibm,ddw-applicable values, avoiding
> confusion about the index of given operations.
>
> Signed-off-by: Leonardo Bras
> Tested-by: David Dai
Reviewed-by: Alexey Kardashevskiy
> ---
>
On Tue, 04 Aug 2020 19:48:07 PDT (-0700), v...@zeniv.linux.org.uk wrote:
On Tue, Aug 04, 2020 at 07:20:05PM -0700, Palmer Dabbelt wrote:
On Tue, 04 Aug 2020 19:07:45 PDT (-0700), v...@zeniv.linux.org.uk wrote:
> On Tue, Aug 04, 2020 at 07:01:01PM -0700, Palmer Dabbelt wrote:
>
> > > We
On Mon, 2020-08-03 at 14:15 +0800, Crystal Guo wrote:
> Introduce force-update method for assert and deassert interface,
> which force the write operation in case the read already happens
> to return the correct value.
>
> Signed-off-by: Crystal Guo
> ---
> drivers/reset/reset-ti-syscon.c | 15
On Tue, 2020-08-04 at 10:15 +0200, Philipp Zabel wrote:
> On Mon, 2020-08-03 at 14:15 +0800, Crystal Guo wrote:
> > The TI syscon reset controller provides a common reset management,
> > and should be suitable for other SOCs. Add compatible "generic-reset",
> > which denotes to use a common
On Tue, Aug 04, 2020 at 07:47:43PM +0200, Bartosz Golaszewski wrote:
> On Tue, Aug 4, 2020 at 1:01 AM Kent Gibson wrote:
> >
>
> [snip]
>
> >
> > > Also: I just started going through the patches - nice idea with the
> > > GPIO attributes, I really like it. Although I need to give it a longer
>
>From LoPAR level 2.8, "ibm,ddw-extensions" index 3 can make the number of
outputs from "ibm,query-pe-dma-windows" go from 5 to 6.
This change of output size is meant to expand the address size of
largest_available_block PE TCE from 32-bit to 64-bit, which ends up
shifting page_size and
Move the window-removing part of remove_ddw into a new function
(remove_dma_window), so it can be used to remove other DMA windows.
It's useful for removing DMA windows that don't create DIRECT64_PROPNAME
property, like the default DMA window from the device, which uses
"ibm,dma-window".
Create defines to help handling ibm,ddw-applicable values, avoiding
confusion about the index of given operations.
Signed-off-by: Leonardo Bras
Tested-by: David Dai
---
arch/powerpc/platforms/pseries/iommu.c | 43 --
1 file changed, 26 insertions(+), 17 deletions(-)
On LoPAR "DMA Window Manipulation Calls", it's recommended to remove the
default DMA window for the device, before attempting to configure a DDW,
in order to make the maximum resources available for the next DDW to be
created.
This is a requirement for using DDW on devices in which hypervisor
There are some devices in which a hypervisor may only allow 1 DMA window
to exist at a time, and in those cases, a DDW is never created to them,
since the default DMA window keeps using this resource.
LoPAR recommends this procedure:
1. Remove the default DMA window,
2. Query for which configs
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 4f30a60aa78410496e5ffe632a371c00f0d83a8d
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 7 weeks ago
config: s390-randconfig-s031-20200805 (attached
On Tue, Aug 04, 2020 at 12:40:44PM -0700, Sean V Kelley wrote:
> From: Qiuxu Zhuo
>
> A PCIe Root Complex Event Collector(RCEC) has the base class 0x08,
> sub-class 0x07, and programming interface 0x00. Add the class code
> 0x0807 to identify RCEC devices and add the defines for the RCEC
>
Hi,
On 8/4/20 11:11 AM, FelixCui-oc wrote:
Hi baolu ,
When creating a identity mapping for a namespace device in RMRR,
you need to add the namespace device to the rmrr->device[] , right?
Yes. You are right.
The dmar_acpi_bus_add_dev() in patch adds the enumeration of the
On 2020/8/5 10:50, 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
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
Convert the i.MX7ULP PM binding to DT schema format using json-schema.
Signed-off-by: Anson Huang
---
.../bindings/arm/freescale/fsl,imx7ulp-pm.txt | 23 -
.../bindings/arm/freescale/fsl,imx7ulp-pm.yaml | 40 ++
2 files changed, 40 insertions(+), 23
Convert the i.MX7ULP SIM binding to DT schema format using json-schema.
Signed-off-by: Anson Huang
---
.../bindings/arm/freescale/fsl,imx7ulp-sim.txt | 16 --
.../bindings/arm/freescale/fsl,imx7ulp-sim.yaml| 36 ++
2 files changed, 36 insertions(+), 16
On 2020/8/5 10:46, Ming Lei wrote:
> On Wed, Aug 05, 2020 at 09:54:00AM +0800, Coly Li wrote:
>> On 2020/8/5 07:58, Ming Lei wrote:
>>> On Tue, Aug 04, 2020 at 10:23:32PM +0800, Coly Li wrote:
When some buggy driver doesn't set its queue->limits.discard_granularity
(e.g. current loop
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
+--
2 files changed, 3 insertions(+), 3 deletions(-)
--- linux-next-20200804.orig/fs/proc/base.c
+++ linux-next-20200804/fs/proc/base.c
@@ -2016,7 +2016,7 @@ const struct dentry_operations pid_dentr
* file type from dcache entry.
*
* Since all of the proc inode numbers are dynamically
1 - 100 of 1144 matches
Mail list logo
