On Mon, Jul 27, 2020 at 4:15 PM Roman Gushchin wrote:
>
> On Mon, Jul 27, 2020 at 03:05:11PM -0700, Andrii Nakryiko wrote:
> > On Mon, Jul 27, 2020 at 12:21 PM Roman Gushchin wrote:
> > >
> > > As bpf is not using memlock rlimit for memory accounting anymore,
> > > let's remove the related code
e
> working on big endian
> date: 8 months ago
> config: arm64-randconfig-s031-20200728 (attached as .config)
> compiler: aarch64-linux-gcc (GCC) 9.3.0
> reproduce:
> wget
> https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
> ~/bin/make.cross
On Mon, Jul 27, 2020 at 12:21 PM Roman Gushchin wrote:
>
> Since bpf stopped using memlock rlimit to limit the memory usage,
> there is no more reason for bpftool to alter its own limits.
>
> Signed-off-by: Roman Gushchin
I think we will need feature check for memcg based accounting.
Thanks,
On Mon, Jul 27, 2020 at 12:21 PM Roman Gushchin wrote:
>
> Since bpf stopped using memlock rlimit to limit the memory usage,
> there is no more reason for bpftool to alter its own limits.
>
> Signed-off-by: Roman Gushchin
> ---
This can't be removed either, due to old kernel support. We
On Mon, Jul 27, 2020 at 12:24 PM Roman Gushchin wrote:
>
> Since bpf is not using memlock rlimit for memory accounting,
> there are no more reasons to bump the limit.
>
> Signed-off-by: Roman Gushchin
> ---
> tools/bpf/runqslower/runqslower.c | 16
> 1 file changed, 16
From: Jason Wang
Change-Id: Ifd7139cfbd122dc22493f4bb93fa884f8edbddb6
Signed-off-by: Jason Wang
---
drivers/vhost/vdpa.c | 23 +--
include/uapi/linux/vhost_types.h | 2 ++
2 files changed, 19 insertions(+), 6 deletions(-)
diff --git a/drivers/vhost/vdpa.c
Add code to support registering address space region for the device. The
virtio driver can run as either:
1. Guest virtio driver
2. Userspace virtio driver on the host
3. Kernel virtio driver on the host
In any case a memory key object is required to provide access to memory
for the device.
This
Fix documentation to match actual function prototypes.
Reviewed-by: Parav Pandit
Signed-off-by: Eli Cohen
---
drivers/vhost/iotlb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/vhost/iotlb.c b/drivers/vhost/iotlb.c
index 1f0ca6e44410..0d4213a54a88 100644
---
Modify get_vq_state() so it returns an error code. In case of hardware
acceleration, the available index may be retrieved from the device, an
operation that can possibly fail.
Reviewed-by: Parav Pandit
Signed-off-by: Eli Cohen
---
drivers/vdpa/ifcvf/ifcvf_main.c | 5 +++--
On Mon, 2020-07-27 at 11:07 +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 27.07.2020 10:14, Chunfeng Yun wrote:
>
> > If not clear u3port's dual mode when disable device, the IP
>
> If we don't clear ... when disabling ...?
>
> > will fail to enter sleep mode when suspend.
Ok, thanks a lot
From: Max Gurtovoy
This will enable vdpa providers to add support for multi queue feature
and publish it to upper layers (vhost and virtio).
Signed-off-by: Max Gurtovoy
Reviewed-by: Jason Wang
---
drivers/vdpa/ifcvf/ifcvf_main.c | 3 ++-
drivers/vdpa/vdpa.c | 3 +++
Keep all vdpa related hardware definitions in this file.
Reviewed-by: Parav Pandit
Signed-off-by: Eli Cohen
---
drivers/vdpa/mlx5/core/mlx5_vdpa_ifc.h | 168 +
1 file changed, 168 insertions(+)
create mode 100644 drivers/vdpa/mlx5/core/mlx5_vdpa_ifc.h
diff --git
Following patches introduce VDPA network driver for Mellanox Connectx6
devices. This patch provides functionality that will be used by those
patches.
Reviewed-by: Parav Pandit
Signed-off-by: Eli Cohen
---
drivers/vdpa/Kconfig | 8 +
drivers/vdpa/Makefile | 1 +
On Mon, Jul 27, 2020 at 12:21 PM Roman Gushchin wrote:
>
> Since bpf is not using memlock rlimit for memory accounting,
> there are no more reasons to bump the limit.
>
> Signed-off-by: Roman Gushchin
> ---
Similarly for bench, it's a tool that's not coupled with the latest
kernel version, it
On 28. 07. 20, 8:05, Jiri Slaby wrote:
> On 27. 07. 20, 15:05, Christoph Hellwig wrote:
>> Since commit 1355cba9c3ba ("tty/synclink: remove ISA support"), the
>> synlink driver only supports PCI card. Remove any leftover dead code
>> to support other cards.
>
> So now you can remove also the
On Mon, Jul 27, 2020 at 12:21 PM Roman Gushchin wrote:
>
> Since bpf stopped using memlock rlimit to limit the memory usage,
> there is no more reason for perf to alter its own limit.
>
> Signed-off-by: Roman Gushchin
> ---
Cc'd Armaldo, but I'm guessing it's a similar situation that latest
On Mon, 2020-07-27 at 17:02 +0200, Paul Cercueil wrote:
>
> Le lun. 27 juil. 2020 à 13:42, Chunfeng Yun
> a écrit :
> > On Sun, 2020-07-26 at 12:27 +0200, Paul Cercueil wrote:
> >>
> >> Le dim. 26 juil. 2020 à 13:14, Andy Shevchenko
> >> a écrit :
> >> > On Mon, Jun 22, 2020 at 1:51 AM
From: Jason Wang
Change-Id: I3751f1aecce285e0f61530c69616852d49e5f547
Signed-off-by: Jason Wang
---
drivers/vdpa/vdpa_sim/vdpa_sim.c | 20
drivers/vhost/vdpa.c | 1 -
2 files changed, 21 deletions(-)
diff --git a/drivers/vdpa/vdpa_sim/vdpa_sim.c
Hi Michael,
please note that this series depends on mlx5 core device driver patches
in mlx5-next branch in
git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git.
git pull git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git
mlx5-next
They also depend Jason Wang's patches
Add a front end VDPA driver that registers in the VDPA bus and provides
networking to a guest. The VDPA driver creates the necessary resources
on the VF it is driving such that data path will be offloaded.
Notifications are being communicated through the driver.
Currently, only VFs are
On Mon, Jul 27, 2020 at 10:58 PM Andrii Nakryiko
wrote:
>
> On Mon, Jul 27, 2020 at 10:47 PM Song Liu wrote:
> >
> > On Mon, Jul 27, 2020 at 12:26 PM Roman Gushchin wrote:
> > >
> > > Remove rlimit-based accounting infrastructure code, which is not used
> > > anymore.
> > >
> > > Signed-off-by:
> On Jul 27, 2020, at 11:06 PM, Andrii Nakryiko
> wrote:
>
> On Mon, Jul 27, 2020 at 12:25 PM Roman Gushchin wrote:
>>
>> As rlimit-based memory accounting is not used by bpf anymore,
>> there are no more reasons to play with memlock rlimit.
>>
>> Delete bpf_rlimit.h which contained a
On 27. 07. 20, 15:05, Christoph Hellwig wrote:
> Since commit 1355cba9c3ba ("tty/synclink: remove ISA support"), the
> synlink driver only supports PCI card. Remove any leftover dead code
> to support other cards.
So now you can remove also the defines and bus_type completely:
$ git grep -E
On Mon, Jul 27, 2020 at 12:25 PM Roman Gushchin wrote:
>
> As rlimit-based memory accounting is not used by bpf anymore,
> there are no more reasons to play with memlock rlimit.
>
> Delete bpf_rlimit.h which contained a code to bump the limit.
>
> Signed-off-by: Roman Gushchin
> ---
We run
For now VQ state involves 16 bit available index value encoded in u64
variable. In the future it will be extended to contain more fields. Use
struct to contain the state, now containing only a single u16 for the
available index. In the future we can add fields to this struct.
Reviewed-by: Parav
On Wed 01 Jul 12:59 PDT 2020, Sibi Sankar wrote:
> The Protection Domains (PD) have a mechanism to keep its resources
> enabled until the PD down indication is acked. Reorder the PD state
> indication ack so that clients get to release the relevant resources
> before the PD goes down.
>
> Fixes:
On Tue, 28 Jul 2020 at 07:37, Peilin Ye wrote:
>
> xsk_getsockopt() is copying uninitialized stack memory to userspace when
> `extra_stats` is `false`. Fix it.
>
> Fixes: 8aa5a33578e9 ("xsk: Add new statistics")
> Suggested-by: Dan Carpenter
> Signed-off-by: Peilin Ye
> ---
Acked-by: Björn
On Mon, Jul 27, 2020 at 12:26 PM Roman Gushchin wrote:
>
> Since bpf is not using rlimit memlock for the memory accounting
> and control, do not change the limit in sample applications.
>
> Signed-off-by: Roman Gushchin
Acked-by: Song Liu
> ---
[...]
> samples/bpf/xdp_rxq_info_user.c |
> On Jul 27, 2020, at 11:13 PM, Björn Töpel wrote:
>
> On Tue, 28 Jul 2020 at 07:37, Peilin Ye wrote:
>>
>> xsk_getsockopt() is copying uninitialized stack memory to userspace when
>> `extra_stats` is `false`. Fix it.
>>
>> Fixes: 8aa5a33578e9 ("xsk: Add new statistics")
>> Suggested-by:
_ti_omap4_clkctrl_setup() misses to call kfree() in an error path. Jump
to cleanup to fix it.
Fixes: 6c3090520554 ("clk: ti: clkctrl: Fix hidden dependency to node name")
Signed-off-by: Jing Xiangfeng
---
drivers/clk/ti/clkctrl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Wed 22 Jul 13:10 PDT 2020, Sibi Sankar wrote:
> The following mem abort is observed when one of the modem blob firmware
> size exceeds the allocated mpss region. Fix this by restricting the copy
> size to segment size using request_firmware_into_buf before load.
>
> Err Logs:
> Unable to
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 92ed301919932f13b9172e525674157e983d
commit: 48ba02b2e2b1a1c80718e93fefe99c8319597c4a usb: gadget: add udc driver
for max3420
date: 5 months ago
config: x86_64-randconfig-r001-20200728 (attached
On 2020/7/28 下午2:05, Eli Cohen wrote:
Hi Michael,
please note that this series depends on mlx5 core device driver patches
in mlx5-next branch in
git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git.
git pull git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git
On 7/22/2020 10:07 AM, Saravana Kannan wrote:
On Wed, Jul 22, 2020 at 4:01 AM Georgi Djakov wrote:
The bootloaders often do some initial configuration of the interconnects
in the system and we want to keep this configuration until all consumers
have probed and expressed their bandwidth needs.
From: Yi Sun
Current interface is good enough for SVA virtualization on an assigned
physical PCI device, but when it comes to mediated devices, a physical
device may attached with multiple aux-domains. Also, for guest unbind,
the PASID to be unbind should be allocated to the VM. This check
This patch refactors the vfio_iommu_type1_ioctl() to use switch instead of
if-else, and each command got a helper function.
Cc: Kevin Tian
CC: Jacob Pan
Cc: Alex Williamson
Cc: Eric Auger
Cc: Jean-Philippe Brucker
Cc: Joerg Roedel
Cc: Lu Baolu
Reviewed-by: Eric Auger
Suggested-by:
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 reduce programming complexity and enhance security.
This VFIO series is intended to expose SVA usage to VMs. i.e. Sharing
guest
On Tue, Jul 28, 2020 at 08:05:36AM +0200, Jiri Slaby wrote:
> On 27. 07. 20, 15:05, Christoph Hellwig wrote:
> > Since commit 1355cba9c3ba ("tty/synclink: remove ISA support"), the
> > synlink driver only supports PCI card. Remove any leftover dead code
> > to support other cards.
>
> So now you
This patch provides an interface allowing the userspace to invalidate
IOMMU cache for first-level page table. It is required when the first
level IOMMU page table is not managed by the host kernel in the nested
translation setup.
Cc: Kevin Tian
CC: Jacob Pan
Cc: Alex Williamson
Cc: Eric Auger
IOMMUs that support nesting translation needs report the capability info
to userspace. It gives information about requirements the userspace needs
to implement plus other features characterizing the physical implementation.
This patch reports nesting info by DOMAIN_ATTR_NESTING. Caller can get
Nesting translation allows two-levels/stages page tables, with 1st level
for guest translations (e.g. GVA->GPA), 2nd level for host translations
(e.g. GPA->HPA). This patch adds interface for binding guest page tables
to a PASID. This PASID must have been allocated by the userspace before
the
This patch reports nesting info, and only supports the case where all
the physical iomms have the same CAP/ECAP MASKS.
Cc: Kevin Tian
CC: Jacob Pan
Cc: Alex Williamson
Cc: Eric Auger
Cc: Jean-Philippe Brucker
Cc: Joerg Roedel
Cc: Lu Baolu
Signed-off-by: Liu Yi L
Signed-off-by: Jacob Pan
Recent years, mediated device pass-through framework (e.g. vfio-mdev)
is used to achieve flexible device sharing across domains (e.g. VMs).
Also there are hardware assisted mediated pass-through solutions from
platform vendors. e.g. Intel VT-d scalable mode which supports Intel
Scalable I/O
This patch allows userspace to request PASID allocation/free, e.g. when
serving the request from the guest.
PASIDs that are not freed by userspace are automatically freed when the
IOASID set is destroyed when process exits.
Cc: Kevin Tian
CC: Jacob Pan
Cc: Alex Williamson
Cc: Eric Auger
Cc:
Hi,
On 16/07/20 9:53 am, Faiz Abbas wrote:
> There might be some requests pending in the buffer when the
> interface close sequence occurs. In some devices, these
> pending requests might lead to the module not shutting down
> properly when m_can_clk_stop() is called.
>
> Therefore, move the
When an IOMMU domain with nesting attribute is used for guest SVA, a
system-wide PASID is allocated for binding with the device and the domain.
For security reason, we need to check the PASID passed from user-space.
e.g. page table bind/unbind and PASID related cache invalidation.
Cc: Kevin Tian
This patch is added as instead of returning a boolean for DOMAIN_ATTR_NESTING,
iommu_domain_get_attr() should return an iommu_nesting_info handle. For
now, return an empty nesting info struct for now as true nesting is not
yet supported by the SMMUs.
Cc: Will Deacon
Cc: Robin Murphy
Cc: Eric
From: Eric Auger
The VFIO API was enhanced to support nested stage control: a bunch of
new ioctls and usage guideline.
Let's document the process to follow to set up nested mode.
Cc: Kevin Tian
CC: Jacob Pan
Cc: Alex Williamson
Cc: Eric Auger
Cc: Jean-Philippe Brucker
Cc: Joerg Roedel
This patch exposes PCIe PASID capability to guest for assigned devices.
Existing vfio_pci driver hides it from guest by setting the capability
length as 0 in pci_ext_cap_length[].
And this patch only exposes PASID capability for devices which has PCIe
PASID extended struture in its configuration
This patch exports iommu nesting capability info to user space through
VFIO. Userspace is expected to check this info for supported uAPIs (e.g.
PASID alloc/free, bind page table, and cache invalidation) and the vendor
specific format information for first level/stage page table that will be
bound
>From IOMMU p.o.v., PASIDs allocated and managed by external components
(e.g. VFIO) will be passed in for gpasid_bind/unbind operation. IOMMU
needs some knowledge to check the PASID ownership, hence add an interface
for those components to tell the PASID owner.
In latest kernel design, PASID
Shared Virtual Addressing (a.k.a Shared Virtual Memory) allows sharing
multiple process virtual address spaces with the device for simplified
programming model. PASID is used to tag an virtual address space in DMA
requests and to identify the related translation structure in IOMMU. When
a
On Wed 03 Jun 15:33 PDT 2020, Evan Green wrote:
> On Tue, Jun 2, 2020 at 10:29 PM Sibi Sankar wrote:
> >
> > Evan,
> > Thanks for taking time to review
> > the series.
> >
> > On 2020-06-02 23:14, Evan Green wrote:
> > > On Tue, Jun 2, 2020 at 9:33 AM Sibi Sankar
> > > wrote:
> > >>
> > >>
On Mon, 27 Jul 2020 13:49:00 -0700 Joe Perches wrote:
> On Mon, 2020-07-27 at 13:44 -0700, Andrew Morton wrote:
> > On Mon, 27 Jul 2020 08:54:41 +0200 SeongJae Park wrote:
> >
> > > > > > Unfortunately, the inexperienced _do_ in fact run
> > > > > > checkpatch on files and submit inappropriate
On Tue 02 Jun 09:32 PDT 2020, Sibi Sankar wrote:
> Remove the redundant running state, as an equivalent is maintained in
> the common q6v5 resource handling helpers.
>
> Signed-off-by: Sibi Sankar
Reviewed-by: Bjorn Andersson
> ---
> drivers/remoteproc/qcom_q6v5_mss.c | 5 -
> 1 file
Hi Jonathan,
Thanks for review, comments inline.
> -Original Message-
> From: Jonathan Cameron
> Sent: Monday, July 27, 2020 8:27 PM
> To: Berghe, Darius
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> devicet...@vger.kernel.org; ji...@kernel.org; r...@kernel.org
>
On Mon, Jul 27, 2020 at 6:39 PM Pascal Bouchareine wrote:
> > struct file is nicely aligned to 256 bytes on distro configs.
> > Will this break everything?
> >
> > $ cat /sys/kernel/slab/filp/object_size
>
> Indeed on the config I'm using here this jumped to 264 bytes
>
> Would it be
This series adds support for the AMS AS73211 digital XYZ sensor.
Changes in v2:
---
- Fix $id in dt binding
- Document full I2C address range in "reg" property
- Move "buffer" member out of "struct as73211_data"
- Fix sparse warnings by using correct data types
On 07/28/2020 12:03 AM, Michael S. Tsirkin wrote:
free cmd id is read using virtio endian, spec says all fields
in balloon are LE. Fix it up.
Fixes: 86a559787e6f ("virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT")
Cc: sta...@vger.kernel.org
Signed-off-by: Michael S. Tsirkin
---
Add DT bindings for AMS AS73211 XYZ True Color Sensor.
Signed-off-by: Christian Eggers
---
.../bindings/iio/light/ams,as73211.yaml | 54 +++
1 file changed, 54 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/light/ams,as73211.yaml
diff --git
On Mon 27 Jul 21:40 PDT 2020, Sai Prakash Ranjan wrote:
> On 2020-07-28 02:28, Bjorn Andersson wrote:
> > On Tue 23 Jun 23:56 PDT 2020, Sai Prakash Ranjan wrote:
> >
> > > Hi Bjorn,
> > >
> > > On 2020-06-21 13:39, Sai Prakash Ranjan wrote:
> > > > Hi Bjorn,
> > > >
> > > > On 2020-06-21 12:52,
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
On Thu, 23 Jul 2020, Hsin-Hsiung Wang wrote:
> This adds compatible for the MediaTek MT6359 PMIC.
>
> Signed-off-by: Hsin-Hsiung Wang
> ---
> Documentation/devicetree/bindings/mfd/mt6397.txt | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
For my own reference (apply this as-is
On 7/21/2020 1:35 PM, Stephen Boyd wrote:
Quoting Akshu Agrawal (2020-07-19 22:04:59)
diff --git a/drivers/clk/x86/clk-fch.c b/drivers/clk/x86/clk-fch.c
index b252f0cf0628..d68bca7b213f 100644
--- a/drivers/clk/x86/clk-fch.c
+++ b/drivers/clk/x86/clk-fch.c
[...]
static int
Hi arm-soc,
On Fri, 26 Jun 2020 10:06:41 +0200 Krzysztof Kozlowski wrote:
>
>
> Fix dtschema validator warnings like:
> l2-cache-controller@ac: $nodename:0:
> 'l2-cache-controller@ac' does not match
> '^(cache-controller|cpu)(@[0-9a-f,]+)*$'
>
> Signed-off-by: Krzysztof
On Tue, Jul 28, 2020 at 08:11:40AM +0300, 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
In case of an error during the initialization of the sensor,
the video device is still available since created at the
probe of the dcmi driver. Moreover the device wouldn't
be released even when removing the module since the release
is performed as part of the notifier unbind callback
(not called
This serie implements fixes in error path of the stm32-dcmi driver.
As part of it, it also fixes the way video device is handled in
order to ensure that it is only created when the attached sensor
is well initialized. (current implementation leads to having a
video device always created and but
This commit add missing vb2_queue_release calls with the
probe error path and module remove.
Missing v4l2_async_notifier_unregister is also added within
the probe error path
Fixes: 37404f91ef8b ("[media] stm32-dcmi: STM32 DCMI camera interface driver")
Signed-off-by: Alain Volmat
---
On 28. 07. 20, 8:20, Christoph Hellwig wrote:
> On Tue, Jul 28, 2020 at 08:05:36AM +0200, Jiri Slaby wrote:
>> On 27. 07. 20, 15:05, Christoph Hellwig wrote:
>>> Since commit 1355cba9c3ba ("tty/synclink: remove ISA support"), the
>>> synlink driver only supports PCI card. Remove any leftover dead
On 2020/7/28 下午2:32, Eli Cohen wrote:
On Tue, Jul 28, 2020 at 02:18:16PM +0800, Jason Wang wrote:
On 2020/7/28 下午2:05, Eli Cohen wrote:
Hi Michael,
please note that this series depends on mlx5 core device driver patches
in mlx5-next branch in
On 7/21/2020 1:36 PM, Stephen Boyd wrote:
Quoting Akshu Agrawal (2020-07-19 22:04:57)
diff --git a/drivers/clk/x86/clk-st.c b/drivers/clk/x86/clk-fch.c
similarity index 73%
rename from drivers/clk/x86/clk-st.c
rename to drivers/clk/x86/clk-fch.c
index 25d4b97aff9b..b252f0cf0628 100644
---
On Tue, Jul 28, 2020 at 02:18:16PM +0800, Jason Wang wrote:
>
> On 2020/7/28 下午2:05, Eli Cohen wrote:
> >Hi Michael,
> >please note that this series depends on mlx5 core device driver patches
> >in mlx5-next branch in
> >git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git.
> >
> >git
On Thu, 23 Jul 2020, Hsin-Hsiung Wang wrote:
> This adds support for the MediaTek MT6359 PMIC. This is a
> multifunction device with the following sub modules:
>
> - Regulator
> - Codec
> - Interrupt
>
> It is interfaced to the host controller using SPI interface
> by a proprietary hardware
We found a case of kernel panic on our server. The stack trace is as
follows(omit some irrelevant information):
BUG: kernel NULL pointer dereference, address: 0080
RIP: 0010:kprobe_ftrace_handler+0x5e/0xe0
RSP: 0018:b512c6550998 EFLAGS: 00010282
RAX: RBX:
According to reference manual, the i.MX7ULP WDOG's operations should
follow below sequence:
1. disable global interrupts;
2. unlock the wdog and wait unlock bit set;
3. reconfigure the wdog and wait for reconfiguration bit set;
4. enabel global interrupts.
Strictly follow the recommended
When kernel idle, system will enter wait/stop mode, wdog should continue
running in this scenario, and the refresh thread can wake up system from
wait/stop mode.
Signed-off-by: Anson Huang
---
drivers/watchdog/imx7ulp_wdt.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
in case of an error tty_register_device_attr() returns ERR_PTR(),
add IS_ERR() check
Reported-and-tested-by: syzbot+67b2bd0e34f952d03...@syzkaller.appspotmail.com
Link: https://syzkaller.appspot.com/bug?extid=67b2bd0e34f952d0321e
Signed-off-by: Rustam Kovhaev
---
drivers/net/usb/hso.c | 5 -
> > + Permanent Long Life: Last longer battery life, this mode
> > + is programmed once in the factory. Switching to a
> > + different mode is unavailable.
>
> The documentation lacks one important aspect: What happens if I have a
> device where the
On Mon 27 Jul 11:20 PDT 2020, Konrad Dybcio wrote:
> Bumping this up, in case it just got overlooked.
>
It was just overlooked, thanks for the bump!
I think it looks good, will pick up the patches, and the previous series
that it depends on.
Thanks,
Bjorn
On 2020/7/28 下午2:40, Jason Wang wrote:
On 2020/7/28 下午2:32, Eli Cohen wrote:
On Tue, Jul 28, 2020 at 02:18:16PM +0800, Jason Wang wrote:
On 2020/7/28 下午2:05, Eli Cohen wrote:
Hi Michael,
please note that this series depends on mlx5 core device driver
patches
in mlx5-next branch in
On Tue, 28 Jul 2020, Gene Chen wrote:
> Lee Jones 於 2020年7月27日 週一 下午7:29寫道：
> >
> > On Fri, 17 Jul 2020, Gene Chen wrote:
> >
> > > From: Gene Chen
> > >
> > > Combine mt6360 pmic/ldo resouces into mt6360 regulator resources
> > > to simplify the similar resources object.
> >
> > Do the
On Tue, Jul 28, 2020 at 5:52 AM Ramuthevar, Vadivel MuruganX
wrote:
> On 27/7/2020 7:09 pm, Andy Shevchenko wrote:
> > On Mon, Jul 27, 2020 at 1:08 PM Ramuthevar,Vadivel MuruganX
> > wrote:
...
> >> v7:
> >>- No Change
> >
> > I guess it's not the correct changelog entry.
> > You moved
On Tue, 28 Jul 2020, Gene Chen wrote:
> Lee Jones 於 2020年7月27日 週一 下午7:08寫道：
> >
> > On Fri, 17 Jul 2020, Gene Chen wrote:
> >
> > > From: Gene Chen
> > >
> > > Rearrange include file without sorting by alphabet.
> >
> > Why are you making this change?
> >
>
> Personal coding style references
On Tue, Jul 28, 2020 at 02:53:34PM +0800, Jason Wang wrote:
>
> On 2020/7/28 下午2:40, Jason Wang wrote:
> >
> >On 2020/7/28 下午2:32, Eli Cohen wrote:
> >>On Tue, Jul 28, 2020 at 02:18:16PM +0800, Jason Wang wrote:
> >>>On 2020/7/28 下午2:05, Eli Cohen wrote:
> Hi Michael,
> please note that
[AMD Official Use Only - Internal Distribution Only]
So Actually for rt5682 codec Now in 5.8 there are three flags :
SND_SOC_RT5682
SND_SOC_RT5682_I2C
SND_SOC_RT5682_SDW
But till 5.7.8 we have
SND_SOC_RT5682
SND_SOC_RT5682_SDW
So in our design we were using SND_SOC_RT5682 which build
Hi Brian Norris,
I'm wishing to change a driver from using "hard_header_len" to using
"needed_headroom" to declare its needed headroom. I submitted a patch
and it is decided it needs to be reviewed. I see you submitted a similar
patch in the past. So I think you might be able to help review my
The scope of select_idle_sibling idle cpu search is LLC. This
becomes a problem for the AMD CCX architecture, as the sd_llc is only
4 cores. On a many core machine, the range of search is too small to
reach a satisfactory level of statistical multiplexing / efficient
utilization of short idle time
On 06.07.20 18:41, Alan Stern wrote:
> On Tue, Jun 30, 2020 at 20:49:58PM -0400, Alan Stern wrote:
>> On Tue, Jun 30, 2020 at 04:31:58PM -0700, Bart Van Assche wrote:
>>> On 2020-06-30 12:38, Alan Stern wrote:
Assume that BLK_MQ_REQ_PREEMPT is set in flags. Then where exactly
does
Hi Abhishek,
> Unregister from suspend notifications and cancel suspend preparations
> before running hci_dev_do_close. Otherwise, the suspend notifier may
> race with unregister and cause cmd_timeout even after hdev has been
> freed.
>
> Signed-off-by: Abhishek Pandit-Subedi
> Reviewed-by:
On Mon, 27 Jul 2020, Linus Walleij wrote:
> This converts the DaVinci DM355EVM LEDs to use GPIO
> descriptor look-ups.
>
> Cc: Sekhar Nori
> Cc: Bartosz Golaszewski
> Signed-off-by: Linus Walleij
> ---
> drivers/mfd/dm355evm_msp.c | 49 --
> 1 file
Hello Martin,
On Mon, Jul 27, 2020 at 11:16:57PM +0200, Martin Botka wrote:
> Mo 27. 7. 2020 at 22:10 Uwe Kleine-König
> wrote:
> >
> > On Fri, Jul 24, 2020 at 11:36:53PM +0200, Martin Botka wrote:
> > > From: Fenglin Wu
> > >
> > > Add pwm_chip to support QTI LPG module and export LPG
Hi Boris,
On Sun, Jul 12, 2020 at 9:01 AM Souptick Joarder wrote:
>
> This series contains few clean up, minor bug fixes and
> Convert get_user_pages() to pin_user_pages().
>
> I'm compile tested this, but unable to run-time test,
> so any testing help is much appriciated.
>
> v2:
>
On Mon, Jul 27, 2020 at 11:42:17PM -0700, Rustam Kovhaev wrote:
> in case of an error tty_register_device_attr() returns ERR_PTR(),
> add IS_ERR() check
>
> Reported-and-tested-by: syzbot+67b2bd0e34f952d03...@syzkaller.appspotmail.com
> Link:
Hi Nicolas,
> HCI_UART_RESET_ON_INIT belongs in hdev_flags, not flags.
>
> Fixes: ce945552fde4a09 ("Bluetooth: hci_h5: Add support for serdev enumerated
> devices")
> Signed-off-by: Nicolas Boichat
>
> ---
>
> drivers/bluetooth/hci_h5.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Hi Max,
> The original return is NOTIFY_STOP, but notifier_call_chain would stop
> the future call for register_pm_notifier even registered on other Kernel
> modules with the same priority which value is zero.
>
> Signed-off-by: Max Chou
> ---
> net/bluetooth/hci_core.c | 2 +-
> 1 file changed,
On Tue, Jul 28, 2020 at 08:40:25AM +0200, Jiri Slaby wrote:
> On 28. 07. 20, 8:20, Christoph Hellwig wrote:
> > On Tue, Jul 28, 2020 at 08:05:36AM +0200, Jiri Slaby wrote:
> >> On 27. 07. 20, 15:05, Christoph Hellwig wrote:
> >>> Since commit 1355cba9c3ba ("tty/synclink: remove ISA support"), the
在 2020/7/28 上午7:34, Alexander Duyck 写道:
>> @@ -847,11 +847,21 @@ static bool too_many_isolated(pg_data_t *pgdat)
>> * contention, to give chance to IRQs. Abort completely if
>> * a fatal signal is pending.
>> */
>> - if
Hi Nicolas,
> We should not call hci_unregister_dev if the device was not
> successfully registered.
>
> Fixes: c34dc3bfa7642fd ("Bluetooth: hci_serdev: Introduce
> hci_uart_unregister_device()")
> Signed-off-by: Nicolas Boichat
>
> ---
>
> drivers/bluetooth/hci_serdev.c | 3 ++-
> 1 file
On Sun, 26 Jul 2020, Michael Walle wrote:
> There are I2C devices which contain several different functions but
> doesn't require any special access functions. For these kind of drivers
> an I2C regmap should be enough.
>
> Create an I2C driver which creates an I2C regmap and enumerates its
>
1 - 100 of 1424 matches
Mail list logo
