From: SeongJae Park
This commit updates MAINTAINERS file for DAMON related files.
Signed-off-by: SeongJae Park
---
MAINTAINERS | 12
1 file changed, 12 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 867157311dc8..39fa966c02b9 100644
--- a/MAINTAINERS
+++
>> So, you'll keep retrying forever. Found while debugging that exact issue :)
>>
>
> If this is the case, my suggestion is to record it in the changelog.
> Otherwise, we may lose this corner case which is important to this change.
Yes, already added it - thanks!
--
Thanks,
David /
On Tue, Oct 20, 2020 at 02:13:13AM +, Z.q. Hou wrote:
[...]
> > > For NXP Layerscape platforms (the ls1028a and ls2088a are also NXP
> > Layerscape platform), as the error response to AXI/AHB was enabled, it will
> > get UR error and trigger SError on AXI bus when it accesses a non-existent
On 30/09/20 06:16, Sean Christopherson wrote:
> This series stems from Lai's RFC patches to intercept LA57 and let the
> guest own FSGSBASE[*]. Discussion and inspection revealed that KVM does
> not handle the case where LA57 is supported in hardware but not exposed to
> the guest. This is
On Mon, 19 Oct 2020 at 17:50, Marc Zyngier wrote:
>
> On 2020-10-14 12:12, Sumit Garg wrote:
> > Enable NMI backtrace support on arm64 using IPI turned as an NMI
> > leveraging pseudo NMIs support. It is now possible for users to get a
> > backtrace of a CPU stuck in hard-lockup using magic
On Mon, Oct 19, 2020 at 11:59:00PM +0100, Daniel Scally wrote:
> ipu3-cio2 driver needs extending with multiple files; rename the main
> source file and specify the renamed file in Makefile to accommodate that.
Suggested-by?
Reviewed-by: Andy Shevchenko
after addressing below comment.
>
Hey Angelo,
The VFE abstraction layers are something I've been looking at too, and
there's no neat solution that both eliminates code duplication,
separates revisions into individual files, and still avoids creating
even more abstraction layers. So while combining vfe47 and vfe48 looks
and feels
On Mon, Oct 19, 2020 at 11:58:59PM +0100, Daniel Scally wrote:
> Development for the ipu3-cio2 driver is taking place in media_tree, but
> there's no T: entry in MAINTAINERS to denote that - rectify that oversight
Reviewed-by: Andy Shevchenko
> Signed-off-by: Daniel Scally
> ---
> Changes in
On Mon, Oct 19, 2020 at 11:58:58PM +0100, Daniel Scally wrote:
> From: Heikki Krogerus
>
> This implements the remaining .graph_* callbacks in the
> fwnode operations vector for the software nodes. That makes
> the fwnode_graph*() functions available in the drivers also
> when software nodes are
On 9/30/2020 1:14 PM, vji...@codeaurora.org wrote:
> From: Vijayanand Jitta
>
> When ever a new iova alloc request comes iova is always searched
> from the cached node and the nodes which are previous to cached
> node. So, even if there is free iova space available in the nodes
> which are
On 9/30/2020 1:14 PM, vji...@codeaurora.org wrote:
> From: Vijayanand Jitta
>
> When ever an iova alloc request fails we free the iova
> ranges present in the percpu iova rcaches and then retry
> but the global iova rcache is not freed as a result we could
> still see iova alloc failure even
On Mon, Oct 19, 2020 at 11:59:01PM +0100, Daniel Scally wrote:
> fwnode_graph_get_endpoint_by_id() will optionally parse enabled devices
> only; that status being determined through the .device_is_available() op
> of the device's fwnode. As software_nodes don't have that operation and
> adding it
On Mon, Oct 19, 2020 at 11:58:56PM +0100, Daniel Scally wrote:
> Use the new software_node_unregister_nodes_reverse() function to
> unwind this array in a cleaner way.
Reviewed-by: Andy Shevchenko
> Suggested-by: Andriy Shevchenko
> Signed-off-by: Daniel Scally
> ---
> Changes in v3:
>
After removing blk-sq code, there is no user of nr_batch_requests
and last_waited in kernel.
Signed-off-by: Yufen Yu
---
include/linux/iocontext.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/include/linux/iocontext.h b/include/linux/iocontext.h
index 1dcd9198beb7..0a9dc40b7be8
C reproducer:
// autogenerated by syzkaller (https://github.com/google/syzkaller)
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
static long syz_open_dev(volatile long a0, volatile long a1, volatile
long a2)
{
if
On Tue, Oct 20, 2020 at 04:57:23PM +0800, Xu Yilun wrote:
> On Tue, Oct 20, 2020 at 09:32:59AM +0200, Greg KH wrote:
> > On Tue, Oct 20, 2020 at 03:11:58PM +0800, Xu Yilun wrote:
> > > I think it is normal case that a driver is successfully registered but
> > > doesn't match any device because it
On Mon, Oct 19, 2020 at 11:58:55PM +0100, Daniel Scally wrote:
> Software nodes that are children of another software node should be
> unregistered before their parent. To allow easy unregistering of an array
> of software_nodes ordered parent to child, add a helper function to loop
> over and
On Mon, Oct 19, 2020 at 11:58:54PM +0100, Daniel Scally wrote:
> Hello all
>
> This series adds support to the ipu3-cio2 driver for fwnode connections
> between cio2 and sensors to be defined via software_nodes. The final patch
> in the series deals wholly with those changes - the preceding
> Avoid using memory block ids. While at it, use uint64_t for
> address/size.
>
> Cc: "Michael S. Tsirkin"
> Cc: Jason Wang
> Cc: Pankaj Gupta
> Signed-off-by: David Hildenbrand
> ---
> drivers/virtio/virtio_mem.c | 10 +++---
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff
Note, your response is not threading well, just hit 'reply' in your
email client...
On Tue, Oct 20, 2020 at 09:01:05AM +, josephj...@google.com wrote:
> > On Tue, Oct 20, 2020 at 08:15:38AM +, josephj...@google.com wrote:
> > > > On Tue, Oct 20, 2020 at 02:22:26PM +0800, Joseph Jang
Hi Geert,
Thank you for the patch!
On 20/10/2020 09:38, Geert Uytterhoeven wrote:
MPTCP_IPV6 selects IPV6, thus enabling an optional feature the user may
not want to enable. Fix this by making MPTCP_IPV6 depend on IPV6, like
is done for all other IPv6 features.
Here again, the intension was
Hi Geert,
On 20/10/2020 09:40, Geert Uytterhoeven wrote:
On Mon, Oct 19, 2020 at 10:38 PM Geert Uytterhoeven
wrote:
On Mon, Oct 19, 2020 at 5:47 PM Matthieu Baerts
wrote:
On 19/10/2020 13:32, Geert Uytterhoeven wrote:
MPTCP_KUNIT_TESTS selects MPTCP, thus enabling an optional feature the
On 19/10/20 19:45, Graf (AWS), Alexander wrote:
>> +* In principle it would be possible to trap x2apic ranges
>> +* if !lapic_in_kernel. This however would be complicated
>> +* because KVM_X86_SET_MSR_FILTER can be called before
>> +* KVM_CREATE_IRQCHIP or
Jakub, Reji,
Andrea (CC'ed) and I have been working on a patch that could solve this issue.
The patch allows to provide optional parameters to when SRv6 behavior.
The OIF can be provided as an optional parameter when configuring SRv6 End.X,
End.DX6 or End.DX4 (we are submiting in the next
> ... which now matches virtio_mem_fake_online(). We'll reuse this
> functionality soon.
>
> Cc: "Michael S. Tsirkin"
> Cc: Jason Wang
> Cc: Pankaj Gupta
> Signed-off-by: David Hildenbrand
> ---
> drivers/virtio/virtio_mem.c | 34 --
> 1 file changed, 24
On 10/20/20 5:53 PM, Joakim Zhang wrote:
> Disable wakeup in flexcan_remove().
The patch looks good, please explain why this is needed.
Marc
>
> Fixes: de3578c198c6 ("can: flexcan: add self wakeup support")
> Fixes: 915f9666421c ("can: flexcan: add support for DT property
> 'wakeup-source'")
On Mon, Oct 19, 2020 at 09:08:03PM -0700, Dan Williams wrote:
> The COPY_MC_TEST facility has served its purpose for validating the
> early termination conditions of the copy_mc_fragile() implementation.
> Remove it and the EXPORT_SYMBOL_GPL of copy_mc_fragile().
>
> Reported-by: Borislav Petkov
On Tue, 20 Oct 2020 14:13:44 +0530
Mugilraj Dhavachelvan wrote:
> Replacing return value -1 to error code
>
> Signed-off-by: Mugilraj Dhavachelvan
> ---
> arch/x86/mm/kmmio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/mm/kmmio.c b/arch/x86/mm/kmmio.c
>
We are submitting the patch for End.DT4. End.DX4 is already there.
So the optional parameter and OIF applies directly to End.X/End.DX6/End.DX4.
On Tue, 20 Oct 2020 11:28:29 +0200
Ahmed Abdelsalam wrote:
> Jakub, Reji,
>
> Andrea (CC'ed) and I have been working on a patch that could solve
`hostname` may not be present on some systems as it's not mandated by
POSIX/SUSv4. This isn't just a theoretical problem: on Arch Linux,
`hostname` is provided by `inetutils`, which isn't part of the base
distribution.
./scripts/mkcompile_h: line 38: hostname: command not found
Use `uname
vImplement callbacks for enabling/disabling
POWER_CONTROL.AutoDischargeDisconnect.
Programs VBUS_SINK_DISCONNECT_THRESHOLD based on the
voltage requested as sink, mode of operation.
The programmed threshold is based on vSinkDisconnect and
vSinkDisconnectPD values.
Add auto_discharge_disconnect
During FRS hardware autonomously starts to source vbus. Provide
callback to perform chip specific operations.
Signed-off-by: Badhri Jagan Sridharan
Reviewed-by: Heikki Krogerus
---
v9 is the first version of this patch in the series. Added to fix
occasional bug of vbus turning back on when
Hi all,
Addressed comments from Rob Herring for dt-bindings patches:
- Added part number for the maxim chip to dt-binding and renamed the
file. Fixed it on the driver side as well with
usb: typec: tcpci_maxim: Fix the compatible string
- new-source-frs-typec-current now uses u32.
Added
On 17.10.20 20:09, Alexander Graf wrote:
> Hi Jason,
>
> On 17.10.20 15:24, Jason A. Donenfeld wrote:
>>
>> After discussing this offline with Jann a bit, I have a few general
>> comments on the design of this.
>>
>> First, the UUID communicated by the hypervisor should be consumed by
>> the
TCPCI spec allows TCPC hardware to autonomously discharge the vbus
capacitance upon disconnect. The expectation is that the TCPM enables
AutoDischargeDisconnect while entering SNK/SRC_ATTACHED states. Hardware
then automously discharges vbus when the vbus falls below a certain
threshold i.e.
This change adds frs-typec-current which allows setting the initial current
capability of the new source when vSafe5V is applied during PD3.0
sink Fast Role Swap.
Signed-off-by: Badhri Jagan Sridharan
---
Changes since v1:
- Changing patch version to v6 to fix version number confusion.
Changes
New source's current capability is now defined through
new-source-frs-typec-current. Refactor tcpm code to parse
new-source-frs-typec-current and infer local port's new source current
capability during frs.
Signed-off-by: Badhri Jagan Sridharan
---
v9 is the first version of this patch in this
Changing compatible string to include the part number.
Signed-off-by: Badhri Jagan Sridharan
---
V11 is the first version of the patch.
Introduced to add chip number to the compatible property to address
Rob Herring's comment on dt-binding patch.
---
drivers/usb/typec/tcpm/tcpci_maxim.c | 2 +-
Enable auto discharge disconnect for Maxim TCPC.
Signed-off-by: Badhri Jagan Sridharan
Reviewed-by: Heikki Krogerus
---
Changes since v1:
- Changing patch version to v6 to fix version number confusion.
Changes since v6:
- Rebase on usb-next.
Changes since v7:
- Heikki's suggestion:
Moved the
On Tue, Oct 20, 2020 at 11:24:32AM +0530, Viresh Kumar wrote:
> On 20-10-20, 10:35, Viresh Kumar wrote:
> > On 19-10-20, 15:10, Sudeep Holla wrote:
> > > On Mon, Oct 19, 2020 at 04:05:35PM +0530, Viresh Kumar wrote:
> > > > On 19-10-20, 11:12, Sudeep Holla wrote:
> > > > > Yes it has clocks
Occasionally, POWER_STATUS.sourcing_vbus takes a while to clear after
writing to MAX_BUCK_BOOST_OP register. This causes vbus to turn back
on while disconnecting the sink. Overcome this issue by writing into
MAX_BUCK_BOOST_OP during frs while sourcing vbu, instead of always
into the register
During FRS hardware autonomously starts to source vbus. Provide
callback to perform chip specific operations.
Signed-off-by: Badhri Jagan Sridharan
Reviewed-by: Heikki Krogerus
---
Introduced in v9.
Changes since v10:
Added Reviewed-by: Heikki Krogerus
---
drivers/usb/typec/tcpm/tcpm.c | 9
Add device tree binding document for Maxim 33359 Type-C chip driver
Signed-off-by: Badhri Jagan Sridharan
---
Changes since v1:
- Changing patch version to v6 to fix version number confusion.
Changes since v6:
- Migrated to yaml format.
Changes since v7:
- Rebase on usb-next
Changes since v8:
> > Let's add some documentation for the current mode - Sub Block Mode (SBM) -
> > to prepare for a new mode - Big Block Mode (BBM).
> >
> > Follow-up patches will properly factor out the existing Sub Block Mode
> > (SBM) and implement Device Block Mode (DBM).
>
> s/Device Block Mode (DBM)/Big
On Mon, Oct 19, 2020 at 11:59:03PM +0100, Daniel Scally wrote:
> Currently on platforms designed for Windows, connections between CIO2 and
> sensors are not properly defined in DSDT. This patch extends the ipu3-cio2
> driver to compensate by building software_node connections, parsing the
>
On Mon, Oct 19, 2020 at 05:22:47PM -0400, Arvind Sankar wrote:
> The boot cpu also enables CR4.PGE -- that code is shared between boot
> and secondary cpus. The boot cpu jumps to the first "1" label below,
> just before the call to sev_verify_cbit you're adding.
You are right, in the real kernel
On 20-10-20, 10:37, Sudeep Holla wrote:
> On Tue, Oct 20, 2020 at 11:24:32AM +0530, Viresh Kumar wrote:
> > On 20-10-20, 10:35, Viresh Kumar wrote:
> > > On 19-10-20, 15:10, Sudeep Holla wrote:
> > > > On Mon, Oct 19, 2020 at 04:05:35PM +0530, Viresh Kumar wrote:
> > > > > On 19-10-20, 11:12,
On Tue, Oct 13, 2020 at 7:16 AM Rob Herring wrote:
>
> On Wed, Oct 7, 2020 at 8:07 PM Badhri Jagan Sridharan
> wrote:
> >
> > On Tue, Oct 6, 2020 at 11:29 AM Rob Herring wrote:
> > >
> > > On Mon, Sep 28, 2020 at 07:39:54PM -0700, Badhri Jagan Sridharan wrote:
> > > > This change adds
On 10/20/20 5:53 PM, Joakim Zhang wrote:
> The first patch from Liu Ying aims to export SCU symbols for SoCs w/wo SCU,
> so that no need to check CONFIG_IMX_SCU in the specific driver.
>
> The following patches are flexcan fixes and add stop mode support for i.MX8QM.
I've applied 3,4,5 to
On Fri, Sep 18, 2020 at 09:27:40AM -0600, Rob Herring wrote:
[...]
> > > Maybe a link down just never happens once up, but if so, then we only need
> > > to check it once and fail probe.
> >
> > Many customers connect the FPGA Endpoint, which may establish PCIe link
> > after the PCIe
On 20.10.20 11:27, Paolo Bonzini wrote:
On 19/10/20 19:45, Graf (AWS), Alexander wrote:
+* In principle it would be possible to trap x2apic ranges
+* if !lapic_in_kernel. This however would be complicated
+* because KVM_X86_SET_MSR_FILTER can be called before
+
> let's use a new "sbm" sub-struct to hold SBM-specific state and rename +
> move applicable definitions, frunctions, and variables (related to
> memory block states).
>
> While at it:
> - Drop the "_STATE" part from memory block states
> - Rename "nb_mb_state" to "mb_count"
> - "set_mb_state" /
On Tue, Oct 20, 2020 at 03:11:34PM +0530, Viresh Kumar wrote:
> On 20-10-20, 10:37, Sudeep Holla wrote:
> > On Tue, Oct 20, 2020 at 11:24:32AM +0530, Viresh Kumar wrote:
> > > On 20-10-20, 10:35, Viresh Kumar wrote:
> > > > On 19-10-20, 15:10, Sudeep Holla wrote:
> > > > > On Mon, Oct 19, 2020 at
Add support of BT656 embedded synchronization busa
Add support of BT656 embedded synchronization bus.
This mode allows to save hardware synchro lines hsync & vsync by replacing
them with synchro codes embedded in data stream.
This bus type is only compatible with 8 bits
Add support of BT656 embedded synchronization bus.
This mode allows to save hardware synchro lines hsync & vsync
by replacing them with synchro codes embedded in data stream.
This mode is enabled when hsync-active & vsync-active
fields are not specified in devicetree.
===
= history =
Add support of BT656 parallel bus mode in DCMI.
This mode is enabled when hsync-active & vsync-active
fields are not specified.
Signed-off-by: Hugues Fruchet
---
.../devicetree/bindings/media/st,stm32-dcmi.yaml | 30 ++
1 file changed, 30 insertions(+)
diff --git
> Let's rename and move accordingly. While at it, rename sb_bitmap to
> "sb_states".
>
> Cc: "Michael S. Tsirkin"
> Cc: Jason Wang
> Cc: Pankaj Gupta
> Signed-off-by: David Hildenbrand
> ---
> drivers/virtio/virtio_mem.c | 118 +++-
> 1 file changed, 62
On 20.10.20 11:35, Christian Borntraeger wrote:
On 17.10.20 20:09, Alexander Graf wrote:
Hi Jason,
On 17.10.20 15:24, Jason A. Donenfeld wrote:
After discussing this offline with Jann a bit, I have a few general
comments on the design of this.
First, the UUID communicated by the hypervisor
On Mon, Oct 19, 2020 at 05:59:25PM -0700, Sean Christopherson wrote:
> On Mon, Oct 19, 2020 at 05:11:17PM +0200, Joerg Roedel wrote:
> > + push%rax
> > + push%rcx
>
> There's no need to save/restore RAX and RCX, they are callee save. This
> function is only called from C, so I doubt
On Tue, Oct 20, 2020 at 02:13:13AM +, Z.q. Hou wrote:
[...]
> > > For NXP Layerscape platforms (the ls1028a and ls2088a are also NXP
> > Layerscape platform), as the error response to AXI/AHB was enabled, it will
> > get UR error and trigger SError on AXI bus when it accesses a non-existent
Since dpm_watchdog just cover device power management,
we proposed sleep timer to cover not only device power management
issues, but also core power management hand issue.
Add sleep timer and timeout handler to prevent device stuck during suspend/
resume process. The timeout handler will dump
The MT6315 is a regulator found on boards based on MediaTek MT8192 and
probably other SoCs. It connects as a slave to SoC using SPMI.
Signed-off-by: Hsin-Hsiung Wang
---
drivers/regulator/Kconfig | 10 +
drivers/regulator/Makefile | 1 +
Add device tree binding information for MT6315 regulator driver.
Example bindings for MT6315 are added.
Signed-off-by: Hsin-Hsiung Wang
---
.../regulator/mtk,mt6315-regulator.yaml | 88 +++
include/dt-bindings/regulator/mtk,mt6315.h| 17
2 files changed, 105
This patch series add support for MediaTek PMIC MT6315 regulator driver,
which adds MT6315 related buck voltage data to the driver.
changes since v1:
- update binding document in DT schema format.
- add mtk,combined-regulator properity to show the relationship of MT6315 bucks.
- ignore the
Add new shutdown() method. Use it in the standard driver model style.
Signed-off-by: Hsin-Hsiung Wang
---
drivers/spmi/spmi.c | 9 +
include/linux/spmi.h | 1 +
2 files changed, 10 insertions(+)
diff --git a/drivers/spmi/spmi.c b/drivers/spmi/spmi.c
index c16b60f645a4..161a48ca4acc
> The calculation is already complicated enough, let's limit it to one
> location.
>
> Cc: "Michael S. Tsirkin"
> Cc: Jason Wang
> Cc: Pankaj Gupta
> Signed-off-by: David Hildenbrand
> ---
> drivers/virtio/virtio_mem.c | 20 +++-
> 1 file changed, 15 insertions(+), 5
On 20-10-20, 10:52, Sudeep Holla wrote:
> On Tue, Oct 20, 2020 at 03:11:34PM +0530, Viresh Kumar wrote:
> > On 20-10-20, 10:37, Sudeep Holla wrote:
> > > On Tue, Oct 20, 2020 at 11:24:32AM +0530, Viresh Kumar wrote:
> > > > On 20-10-20, 10:35, Viresh Kumar wrote:
> > > > > On 19-10-20, 15:10,
On 19.10.20 19:15, Mathieu Desnoyers wrote:
- On Oct 17, 2020, at 2:10 PM, Andy Lutomirski l...@kernel.org wrote:
On Fri, Oct 16, 2020 at 6:40 PM Jann Horn wrote:
[adding some more people who are interested in RNG stuff: Andy, Jason,
Theodore, Willy Tarreau, Eric Biggers. also
Add support of BT656 embedded synchronization bus.
This mode allows to save hardware synchro lines hsync & vsync
by replacing them with synchro codes embedded in data stream.
This mode is enabled when hsync-active & vsync-active
fields are not specified in devicetree.
===
= history =
On Mon, Oct 19, 2020 at 02:31:05PM -0700, Sean Christopherson wrote:
Good morning, I hope the day is starting well for everyone.
> On Sun, Oct 18, 2020 at 03:49:20AM -0500, Dr. Greg wrote:
> > Is this even a relevant control if we cede the notion of dynamically
> > loadable enclave code, which
Add support of BT656 parallel bus mode in DCMI.
This mode is enabled when hsync-active & vsync-active
fields are not specified.
Signed-off-by: Hugues Fruchet
---
.../devicetree/bindings/media/st,stm32-dcmi.yaml | 30 ++
1 file changed, 30 insertions(+)
diff --git
Add support of BT656 embedded synchronization busa
Add support of BT656 embedded synchronization bus.
This mode allows to save hardware synchro lines hsync & vsync by replacing
them with synchro codes embedded in data stream.
This bus type is only compatible with 8 bits
On Fri, Oct 16, 2020 at 12:14:31PM +0100, Mark Rutland wrote:
> Mark B's reply dropped this, but the next paragraph covered that:
>
> | I was planning to send a mail once I've finished writing a test, but
> | IIUC there are some windows where ftrace/kretprobes
> | detection/repainting may not
Hi Daniel, Andy,
On Mon, Oct 19, 2020 at 11:58:55PM +0100, Daniel Scally wrote:
> Software nodes that are children of another software node should be
> unregistered before their parent. To allow easy unregistering of an array
> of software_nodes ordered parent to child, add a helper function to
On Tue, Oct 20, 2020 at 2:23 PM Jason Wang wrote:
>
>
> On 2020/10/19 下午5:06, Zhenzhong Duan wrote:
> > If Post interrupt is disabled due to hardware limit or forcely disabled
> > by "intremap=nopost" parameter, return -EINVAL so that the legacy mode IRQ
> > isn't registered as IRQ bypass
Thanks Tom,
On Mon, 2020-10-19 at 12:33 -0700, t...@redhat.com wrote:
> From: Tom Rix
>
> A break is not needed if it is preceded by a return
>
> Signed-off-by: Tom Rix
> ---
> drivers/gpio/gpio-bd70528.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/gpio/gpio-bd70528.c
On 2020-10-20 07:43, Sumit Garg wrote:
On Mon, 19 Oct 2020 at 17:07, Marc Zyngier wrote:
[...]
> +{
> + if (!ipi_desc)
> + return;
> +
> + if (is_nmi) {
> + if (!prepare_percpu_nmi(ipi_id))
> + enable_percpu_nmi(ipi_id, IRQ_TYPE_NONE);
> +
On Tue, Oct 20, 2020 at 2:32 PM Jason Wang wrote:
>
>
> On 2020/10/19 下午5:06, Zhenzhong Duan wrote:
> > In case failure to setup Post interrupt for an IRQ, it make no sense
> > to assign irqfd->producer to the producer.
> >
> > This change makes code more robust.
>
>
> It's better to describe
On Tue, Oct 20, 2020 at 05:32:26AM +, Joel Stanley wrote:
> On Fri, 9 Oct 2020 at 05:20, Joel Stanley wrote:
> >
> > On Thu, 1 Oct 2020 at 04:30, Andrew Jeffery wrote:
> > >
> > > Setting both CONFIG_KPROBES=y and CONFIG_FORTIFY_SOURCE=y on ARM leads
> > > to a panic in memcpy() when
On Tue, 2020-10-20 at 08:00 +, David Laight wrote:
> From: Joe Perches
> > Sent: 19 October 2020 16:47
> > On Mon, 2020-10-19 at 03:13 +0800, kernel test robot wrote:
> > > Hi Ard,
> > >
> > > First bad commit (maybe != root cause):
> > >
> > > tree:
> > >
Add support of BT656 embedded synchronization bus.
This mode allows to save hardware synchro lines hsync & vsync by replacing
them with synchro codes embedded in data stream.
This bus type is only compatible with 8 bits width data bus.
Due to reserved values 0x00 & 0xff used for synchro codes,
Add support of BT656 embedded synchronization bus.
This mode allows to save hardware synchro lines hsync & vsync
by replacing them with synchro codes embedded in data stream.
This mode is enabled when hsync-active & vsync-active
fields are not specified in devicetree.
===
= history =
Add support of BT656 parallel bus mode in DCMI.
This mode is enabled when hsync-active & vsync-active
fields are not specified.
Signed-off-by: Hugues Fruchet
---
.../devicetree/bindings/media/st,stm32-dcmi.yaml | 30 ++
1 file changed, 30 insertions(+)
diff --git
On Tue, Oct 20, 2020 at 04:45:56PM +1300, Chris Packham wrote:
> When a port is configured with 'managed = "in-band-status"' don't force
> the link up, the switch MAC will detect the link status correctly.
>
> Signed-off-by: Chris Packham
> Reviewed-by: Andrew Lunn
I thought we had issues with
On Tue, Oct 20, 2020 at 04:45:58PM +1300, Chris Packham wrote:
> +void mv88e6123_serdes_get_regs(struct mv88e6xxx_chip *chip, int port, void
> *_p)
> +{
> + u16 *p = _p;
> + u16 reg;
> + int i;
> +
> + if (mv88e6xxx_serdes_get_lane(chip, port) == 0)
> + return;
> +
> +
On Thu, Oct 15, 2020 at 05:47:38PM -0500, Bjorn Helgaas wrote:
> On Wed, Sep 16, 2020 at 01:41:30PM +0800, Zhiqiang Hou wrote:
> > From: Hou Zhiqiang
> >
> > On NXP Layerscape platforms, it results in SError in the
> > enumeration of the PCIe controller, which is not connecting
> > with an
On Thu, Oct 15, 2020 at 11:09:23AM +0200, Oleksij Rempel wrote:
> Add Van der Laan LANMCU iMX6dl based board
>
> Signed-off-by: Oleksij Rempel
> ---
> Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Krzysztof Kozlowski
Best regards,
The cma_mutex which protects alloc_contig_range() was first appeared in
commit 7ee793a62fa8c ("cma: Remove potential deadlock situation"),
at that time, there is no guarantee the behavior of concurrency inside
alloc_contig_range().
After the commit 2c7452a075d4db2dc
("mm/page_isolation.c: make
On Thu, Oct 15, 2020 at 11:09:24AM +0200, Oleksij Rempel wrote:
> Van der Laan LANMCU is a module for the food storage rooms to control
> proper gas composition.
>
> Co-Developed-by: Robin van der Gracht
> Signed-off-by: Robin van der Gracht
> Signed-off-by: Oleksij Rempel
> ---
>
Looks good to me.
Signed-off-by: Robert Foss
On Sun, 18 Oct 2020 at 14:53, wrote:
>
> From: AngeloGioacchino Del Regno
>
> Add support for the Qualcomm SDM630/636/660 and SDA variants' camera
> subsystem. These SoCs are equipped with:
> - 3x CSI PHY 3-Phase v1.0 (downstream csiphy-v3.5)
> -
On Tue, Oct 20, 2020 at 04:57:11PM +0800, Shung-Hsi Yu wrote:
> Hi,
>
> This patch trigger the following KASAN error inside qlge_init_device().
>
> [...] general protection fault, probably for non-canonical address
> 0xdc4b: [#1] SMP DEBUG_PAGEALLOC KASAN PTI
> [...] KASAN:
Hi Marc,
> -Original Message-
> From: Marc Kleine-Budde
> Sent: 2020年10月20日 17:31
> To: Joakim Zhang ; robh...@kernel.org;
> shawn...@kernel.org; s.ha...@pengutronix.de
> Cc: ker...@pengutronix.de; dl-linux-imx ; Ying Liu
> ; linux-...@vger.kernel.org; Pankaj Bansal
> ;
Since WB feature has been added, WB related sysfs entries can be accessed
even when an UFS device does not support WB feature. In that case, the
descriptors which are not supported by the UFS device may be wrongly
reported when they are accessed from their corrsponding sysfs entries.
Fix it by
We returned earlier by mistake even when there were no failures. Fix it.
Fixes: dd461cd9183f ("opp: Allow dev_pm_opp_get_opp_table() to return
-EPROBE_DEFER")
Reported-by: Naresh Kamboju
Signed-off-by: Viresh Kumar
---
Rafael: Please pick up this one as well for 5.10-rc1/2 once Naresh gives
Looks good to me.
Signed-off-by: Robert Foss
On Sun, 18 Oct 2020 at 14:53, wrote:
>
> From: AngeloGioacchino Del Regno
>
> Add bindings for qcom,sdm660-camss in order to support the camera
> subsystem on SDM630/660 and SDA variants.
>
> Signed-off-by: AngeloGioacchino Del Regno
> ---
>
On 20/10/20 11:48, Alexander Graf wrote:
>
> count: 1,
> default_allow: false,
> ranges: [
> {
> flags: KVM_MSR_FILTER_READ,
> nmsrs: 1,
> base: MSR_EFER,
> bitmap: { 1 },
> },
> ],
> }
>
> That filter would set all
Looks good to me.
Signed-off-by: Robert Foss
On Sun, 18 Oct 2020 at 14:53, wrote:
>
> From: AngeloGioacchino Del Regno
>
> The SDM630/660 SoCs (and variants) have another clock source
> for the PHY, which must be set to a rate that's equal or
> greater than the CSI PHY timer clock: failing to
On 16-10-20, 11:15, Viresh Kumar wrote:
> +Dave,
>
> On 15-10-20, 15:26, Naresh Kamboju wrote:
> > The arm x15 boot failed on Linus 's mainline version 5.9.0.
>
> Don't mention the version as this doesn't give the right information.
> You tested it over 5.9 + 5.10-rc1 material.
>
> > I have
Hi Krzysztof,
On Mon, Oct 19, 2020 at 07:02:44PM +0200, Krzysztof Kozlowski wrote:
> Add bindings for the IMX258 camera sensor. The bindings, just like the
> driver, are quite limited, e.g. do not support regulator supplies.
>
> Signed-off-by: Krzysztof Kozlowski
> Reviewed-by: Rob Herring
>
Dear,
My names are Barrister Doswell Coakley,I am contacting you for a partnership in
business venture to invest on lucrative business in your country,I want to
partner with you for this investment purpose.
I am the legal trustee to late Mr.Paul Louis Halley,who died along with his
wife in a
1 - 100 of 1105 matches
Mail list logo
