On Tue, Dec 29, 2020 at 11:17:15PM +0200, Cristian Ciocaltea wrote:
> Hi,
>
> This patchset brings a series of improvements for the Actions Semi S500
> SoCs family, by adding support for Clock & Reset Management Units, DMA,
> MMC, I2C & SIRQ controllers.
>
> Please note the patches consist
"Linux kernel's Kroah-Hartman: We're not struggling to get new coders,
it's code review that's the bottleneck", says article at The Register.
Ok, I've used C++ for 20 years, taught C/C++ at two universities, and
developed real-time safety-critical systems. Need me? Contact me off-list.
Rob
On Tue, Dec 29, 2020 at 11:17:26PM +0200, Cristian Ciocaltea wrote:
> Add uSD support for RoseapplePi SBC using a fixed regulator as a
> temporary solution until PMIC support becomes available.
>
> Signed-off-by: Cristian Ciocaltea
Reviewed-by: Manivannan Sadhasivam
Thanks,
Mani
> ---
>
On Tue, Dec 29, 2020 at 02:05:51AM -0500, Carl Huang wrote:
> If client driver has specified the irq_flags, mhi uses this specified
> irq_flags. Otherwise, mhi uses default irq_flags.
>
> The purpose of this change is to support one MSI vector for QCA6390.
> MHI will use one same MSI vector too
mits/Timon-Baetz/extcon-max8997-Add-CHGINS-and-CHGRM-interrupt-handling/20201231-045812
> base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
> for-next
> config: arm-randconfig-r004-20201230 (attached as .config)
> compiler: clan
Hi Mika,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f6e1ea19649216156576aeafa784e3b4cee45549
commit: 2c6ea4e2cefe2e86af782a5b8e1070f4d434f2f2 thunderbolt: Allow KUnit tests
to be built also when
Am 30.12.20 um 16:45 schrieb Arnd Bergmann:
> From: Arnd Bergmann
>
> Changing some inline functions to use the new irq_check_status_bit
> function out of line breaks calling them from loadable modules:
>
> ERROR: modpost: "irq_check_status_bit" [drivers/perf/arm_spe_pmu.ko]
> undefined!
Just
On 12/22/2020 2:18 PM, Md Sadre Alam wrote:
of_device_get_match_data returns NULL when no match.
So add the NULL pointer check to avoid dereference.
Signed-off-by: Md Sadre Alam
---
Reviewed-by: Veerabhadrarao Badiganti
drivers/mmc/host/sdhci-msm.c | 2 ++
1 file changed, 2
allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a005-20201230
x86_64 randconfig-a001-20201230
x86_64 randconfig-a006-20201230
x86_64 randconfig-a002-20201230
When the EnableLPIs bit is set to 0, any ITS LPI requests in the
Redistributor would be ignored. And this check is independent from
the ITS LPI translation. So it might be better to move the check
of the EnableLPIs bit out of the LPI resolving, and also add it
to the path that uses the translation
Category: feature
Bugzilla: NA
CVE: NA
Use reserved memory to create a pmem device to store the
processes information that dumped before kernel update.
When you want to use this feature you need to declare by
"pmemmem=pmem_size:pmem_phystart" in cmdline.
(exp: pmemmem=100M:0x2020)
HDA controller can't be runtime-suspended after commit 215a22ed31a1
("ALSA: hda: Refactor codjc PM to use direct-complete optimization"),
which enables direct-complete for HDA codec.
The HDA codec driver doesn't expect direct-complete will be disabled
after it returns a positive value from
Hi Zhu,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f6e1ea19649216156576aeafa784e3b4cee45549
commit: 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 vhost_vdpa: implement IRQ
offloading in vhost_vdpa
date: 5
-20201230
i386 randconfig-a006-20201230
i386 randconfig-a004-20201230
i386 randconfig-a003-20201230
i386 randconfig-a002-20201230
i386 randconfig-a001-20201230
x86_64 randconfig-a005-20201230
x86_64
Hi Jason,
Thanks for the detailed research and explanation.That's ok for me.
Regards.
Fatih USTA
On 30.12.2020 15:39, Jason A. Donenfeld wrote:
Hi Fatih,
Thanks for the report and the detailed test case. From what I can see,
this behavior presents itself both with the explicit ip link del
On Tue, Dec 29, 2020 at 6:16 AM Jakub Kicinski wrote:
>
> On Mon, 28 Dec 2020 18:45:07 +0900 Bongsu Jeon wrote:
> > From: Bongsu Jeon
> >
> > A NCI virtual device can be made to simulate a NCI device in user space.
> > Using the virtual NCI device, The NCI module and application can be
> >
Hi Stanley,
I slightly updated this change, because I found that in
ufshcd_devfreq_scale(),
in order to call ufshcd_wb_ctrl(), clk_scale_lock write sem is released
once,
which breaks the assumption that clk_scale_lock wraps the entire func.
So,
in ufshcd_devfreq_scale(), I changed the
On 12/31/20 12:05 PM, Yi Li wrote:
> iput handles NULL pointers gracefully, so there's no need to
> check the pointer before the call.
>
> Signed-off-by: Yi Li
Acked-by: Joseph Qi
> ---
> fs/ocfs2/super.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/fs/ocfs2/super.c
User layer may access sysfs nodes when system PM ops or error handling
is running, which can cause various problems. Rename eh_sem to host_sem
and use it to protect PM ops and error handling from user layer intervene.
Signed-off-by: Can Guo
diff --git a/drivers/scsi/ufs/ufs-sysfs.c
During system resume/suspend, hba could be NULL. In this case, do not touch
eh_sem.
Fixes: 88a92d6ae4fe ("scsi: ufs: Serialize eh_work with system PM events and
async scan")
Signed-off-by: Can Guo
diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
index e221add..34e2541 100644
On Wed, Dec 30, 2020 at 11:56:04PM +0100, Heiner Kallweit wrote:
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -3024,7 +3024,9 @@ void pci_pm_init(struct pci_dev *dev)
> u16 status;
> u16 pmc;
>
> - pm_runtime_forbid(>dev);
> + if (pci_acpi_forbid_runtime_pm())
> +
iput handles NULL pointers gracefully, so there's no need to
check the pointer before the call.
Signed-off-by: Yi Li
---
fs/ocfs2/super.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/ocfs2/super.c b/fs/ocfs2/super.c
index 2febc76e9de7..079f8826993e 100644
--- a/fs/ocfs2/super.c
+++
Hi Will,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f6e1ea19649216156576aeafa784e3b4cee45549
commit: eb5c2d4b45e3d2d5d052ea6b8f1463976b1020d5 compiler.h: Move
compiletime_assert() macros into compiler_types.h
On 2020/12/4 下午12:03, Jason Wang wrote:
Hi all:
This series tries to implement a vDPA driver for virtio-pci device
which will bridge between vDPA bus and virtio-pci device.
This could be used for future feature prototyping and testing.
Please review
Changes from V2:
- don't try to use
On Wed, Dec 30, 2020 at 01:46:44PM +, Mark Brown wrote:
> On Wed, Dec 30, 2020 at 10:24:20AM +0800, Xu Yilun wrote:
> > On Tue, Dec 29, 2020 at 01:13:08PM +, Mark Brown wrote:
>
> > > Does this still apply with current code? There have been some fixes in
> > > this area which I think
In config PCIE_TEGRA194_EP the mode incorrectly referred to
host mode.
Signed-off-by: Wesley Sheng
---
drivers/pci/controller/dwc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/controller/dwc/Kconfig
b/drivers/pci/controller/dwc/Kconfig
index
On Wed, Dec 30, 2020 at 11:43 PM Arnd Bergmann wrote:
>
> From: Arnd Bergmann
>
> Randconfig builds often show harmless warnings like
>
> WARNING: unmet direct dependencies detected for SND_SOC_MT6359
> Depends on [n]: SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] &&
> MTK_PMIC_WRAP [=n]
>
From: Bongsu Jeon
If there is a NCI command in work queue after closing the NCI device at
nci_unregister_device, The NCI command timer starts at flush_workqueue
function and then NCI command timeout handler would be called 5 second
after flushing the NCI command work queue and destroying the
> On 31 Dec 2020, at 4:23 am, Martin Blumenstingl
> wrote:
>
> On Wed, Dec 30, 2020 at 11:38 AM Christian Hewitt
> wrote:
>>
>> The Shenzen AZW (Beelink) GS-King-X is based on the Amlogic W400 reference
>> board with an S922X-H chip.
>>
>> - 4GB LPDDR4 RAM
>> - 64GB eMMC storage
>> -
On Wed, Dec 30, 2020 at 12:05:17PM +, Jonathan Cameron wrote:
> On Tue, 15 Dec 2020 13:44:41 +0800
> Ye Xiang wrote:
>
> > Here we register one iio device with three channels which present angle for
> > hinge, keyboard and screen.
> >
> > This driver works on devices with Intel integrated
Hello,
I tried -Wframe-larger-than=512 in x86_64, and only below two functions
exceed the frame size threshold, will check powerpc64 later.
namei.c: In function ‘f2fs_update_extension_list’:
namei.c:276:1: warning: the frame size of 560 bytes is larger than 512 bytes
[-Wframe-larger-than=]
On 2020/12/30 下午6:05, Eli Cohen wrote:
On Wed, Dec 16, 2020 at 02:48:09PM +0800, Jason Wang wrote:
Follows the vDPA support for multiple address spaces, this patch
introduce uAPI for the userspace to know the number of virtqueue
groups supported by the vDPA device.
Signed-off-by: Jason Wang
Add MIPI rx DPI input support
Signed-off-by: Xin Ji
Reported-by: kernel test robot
---
drivers/gpu/drm/bridge/analogix/anx7625.c | 344 --
drivers/gpu/drm/bridge/analogix/anx7625.h | 24 ++-
2 files changed, 348 insertions(+), 20 deletions(-)
diff --git
Add DPI flag for distinguish MIPI input signal type, DSI or DPI. Add
swing setting for adjusting DP tx PHY swing
Signed-off-by: Xin Ji
---
.../bindings/display/bridge/analogix,anx7625.yaml | 25 --
1 file changed, 23 insertions(+), 2 deletions(-)
diff --git
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f6e1ea19649216156576aeafa784e3b4cee45549
commit: 476b70b4d1adff4465e9ff68021c52858555ac28 PCI: keystone: Enable
compile-testing on !ARM
date: 6 weeks ago
config: x86_64-randconfig-a001-20201231 (attached
Hi all, this patch series implement MIPI rx DPI feature. Please help to review.
This is the v2 version, any mistakes, please let me know,
I'll fix it in the next series.
Change history:
v2: Fix Rob Herring comment
- Fix yamllint warnings/errors in analogix,anx7625.yaml
- Fix kernel robot
On Sun, Dec 27, 2020 at 6:55 PM Roger Lu wrote:
>
> The Smart Voltage Scaling(SVS) engine is a piece of hardware
> which calculats suitable SVS bank voltages to OPP voltage table.
calculates
> Then, DVFS driver could apply those SVS bank voltages to PMIC/Buck
> when receiving
On Wed, Dec 30, 2020 at 04:46:17PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> A recent patch added a local variable twice:
>
> drivers/pinctrl/nomadik/pinctrl-nomadik.c:953:8: error: unused variable
> 'wake' [-Werror,-Wunused-variable]
>
> Remove the unused outer declaration
>
>
list_for_each + list_entry can be changed to list_for_each_entry
It reduces number of variables and lines.
Signed-off-by: Daejun Park
---
fs/ext4/fast_commit.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/fs/ext4/fast_commit.c b/fs/ext4/fast_commit.c
index
On Mon, Dec 28, 2020 at 4:38 PM Yongqiang Niu
wrote:
>
> the mmsys will more and more complicated after support
> more and more SoCs, add an independent folder will be
> more clear
>
> Signed-off-by: Yongqiang Niu
> ---
> drivers/soc/mediatek/Makefile | 2 +-
>
This reverts commit 65f746e8285f0a67d43517d86fedb9e29ead49f2.
As commit 8a473dbadccfc ("drm/i915: Fix DMA mapped scatterlist walks") and
commit 934941ed5a307 ("drm/i915: Fix DMA mapped scatterlist lookup") fixed
the DMA scatterlist limitations in the i915 driver, remove this temporary
workaround.
Lock(>lock) without disabling irq causes lockdep warnings.
WARNING: possible irq lock inversion dependency detected
5.11.0-rc1+ #828 Not tainted
kworker/0:1H/120 just changed the
The VT-d hardware will ignore those Addr bits which have been masked by
the AM field in the PASID-based-IOTLB invalidation descriptor. As the
result, if the starting address in the descriptor is not aligned with
the address mask, some IOTLB caches might not invalidate. Hence people
will see below
Use IS_ALIGNED() instead. Otherwise, an unaligned address will be ignored.
Fixes: 33cd6e642d6a7 ("iommu/vt-d: Flush PASID-based iotlb for iova over first
level")
Signed-off-by: Lu Baolu
---
drivers/iommu/intel/dmar.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
With commit c588072bba6b5 ("iommu/vt-d: Convert intel iommu driver to
the iommu ops"), the trace events for dma map/unmap have no users any
more. Remove them so that they don't show up under
/sys/kernel/debug/tracing/events/intel_iommu. The users should use the
map/unmap traces defined in the
发件人: Paul E. McKenney
发送时间: 2020年12月31日 0:19
收件人: Zhang, Qiang
抄送: a...@linux-foundation.org; manf...@colorfullife.com; gustavo...@kernel.org;
linux-kernel@vger.kernel.org
主题: Re: [PATCH] ipc/sem.c: Convert kfree_rcu() to call_rcu() in freeary function
On Tue, 29 Dec 2020 at 20:15, Deucher, Alexander
wrote:
>
> It looks like the driver is not able to access the firmware for some reason.
> Please make sure it is available in your initrd or compiled into the kernel
> depending on your config.
Exactly! Thanks!
# lsinitrd
On 12/31/20 4:49 AM, Linus Torvalds wrote:
On Tue, Dec 29, 2020 at 6:59 PM kernel test robot wrote:
[ 235.553325] BUG: sleeping function called from invalid context at
arch/x86/mm/fault.c:1351
[ 235.554684] in_atomic(): 0, irqs_disabled(): 1, non_block: 0, pid: 7515,
name: trinity-c1
[
Hi, Jiaxun,
On Wed, Dec 30, 2020 at 11:26 AM Jiaxun Yang wrote:
>
> Loongson64C is known to be vulnerable to meltdown according to
> PoC from Rui Wang .
How about Loongson-3A1000/3B1500, and Loongson-2E/2F?
Huacai
>
> Loongson64G defended these side-channel attack by silicon.
>
> Signed-off-by:
Reviewed-by: Huacai Chen
On Wed, Dec 30, 2020 at 11:25 AM Jiaxun Yang wrote:
>
> Accorading to MIPS's announcement[1], only P5600 and P6600 is
> affected by spectre v1 and v2, other cores are not affected.
>
> So we mark vulnerabilities states for MIPS cores as known and
> set P5600 and P6600
Hi, Jiaxun,
On Wed, Dec 30, 2020 at 11:25 AM Jiaxun Yang wrote:
>
> Add infrastructure to display CPU vulnerabilities.
> As most MIPS CPU vendors are dead today and we can't confirm
> vulnerabilities states with them, we'll display vulnerabilities
> as "Unknown" by default and override them in
Remove the __kvm_handle_fault_on_reboot() and __ex() macros now that all
VMX and SVM instructions use asm goto to handle the fault (or in the
case of VMREAD, completely custom logic). Drop kvm_spurious_fault()'s
asmlinkage annotation as __kvm_handle_fault_on_reboot() was the only
flow that
From: Uros Bizjak
Move the declaration of kvm_spurious_fault() to KVM's "private" x86.h,
it should never be called by anything other than low level KVM code.
Cc: Paolo Bonzini
Cc: Sean Christopherson
Signed-off-by: Uros Bizjak
[sean: rebased to a series without
Add svm_asm*() macros, a la the existing vmx_asm*() macros, to handle
faults on SVM instructions instead of using the generic __ex(), a.k.a.
__kvm_handle_fault_on_reboot(). Using asm goto generates slightly
better code as it eliminates the in-line JMP+CALL sequences that are
needed by
Reviewed-by: Huacai Chen
On Wed, Dec 30, 2020 at 11:49 AM Jiaxun Yang wrote:
>
> .cprestore is removed as we don't expect Position Independent
> zboot ELF.
>
> .noreorder is also removed and rest instructions are massaged
> to improve readability.
>
> t9 register is used for indirect jump as
Move the Intel PT tracking outside of the VMXON/VMXOFF helpers so that
a future patch can drop KVM's kvm_cpu_vmxoff() in favor of the kernel's
cpu_vmxoff() without an associated PT functional change, and without
losing symmetry between the VMXON and VMXOFF flows.
Barring undocumented behavior,
Drop kvm_cpu_vmxoff() in favor of the kernel's cpu_vmxoff(). Modify the
latter to return -EIO on fault so that KVM can invoke
kvm_spurious_fault() when appropriate. In addition to the obvious code
reuse, dropping kvm_cpu_vmxoff() also eliminates VMX's last usage of the
From: Uros Bizjak
Replace inline assembly in nested_vmx_check_vmentry_hw
with a call to __vmx_vcpu_run. The function is not
performance critical, so (double) GPR save/restore
in __vmx_vcpu_run can be tolerated, as far as performance
effects are concerned.
Cc: Paolo Bonzini
Cc: Sean
From: David P. Reed
Explicitly tell the compiler that VMXOFF modifies flags (like all VMX
instructions), and mark memory as clobbered since VMXOFF must not be
reordered and also may have memory side effects (though the kernel
really shouldn't be accessing the root VMCS anyways).
Practically
Force all CPUs to do VMXOFF (via NMI shootdown) during an emergency
reboot if VMX is _supported_, as VMX being off on the current CPU does
not prevent other CPUs from being in VMX root (post-VMXON). This fixes
a bug where a crash/panic reboot could leave other CPUs in VMX root and
prevent them
Silently ignore all faults on VMXOFF in the reboot flows as such faults
are all but guaranteed to be due to the CPU not being in VMX root.
Because (a) VMXOFF may be executed in NMI context, e.g. after VMXOFF but
before CR4.VMXE is cleared, (b) there's no way to query the CPU's VMX
state without
This series is a conglomeration of three previous series/patches and a bit
of new code. None of the previous series are directly related, but they
are all needed to achieve the overarching goal of nuking
__kvm_handle_fault_on_reboot(), which is a rather ugly inline asm macro
that has the
Reviewed-by: Huacai Chen
On Wed, Dec 30, 2020 at 11:43 AM Jiaxun Yang wrote:
>
> cluster is required for cacheinfo to set shared_cpu_map correctly.
>
> Signed-off-by: Jiaxun Yang
> Reviewed-by: Tiezhu Yang
> Tested-by: Tiezhu Yang
> ---
> arch/mips/loongson64/smp.c | 2 ++
> 1 file changed,
Hi, Jiaxun,
On Wed, Dec 30, 2020 at 11:41 AM Jiaxun Yang wrote:
>
> Victim Cache is defined by Loongson as per-core unified
> private Cache.
> Add this into cacheinfo and make cache levels selfincrement
> instead of hardcode levels.
>
> Signed-off-by: Jiaxun Yang
> Reviewed-by: Tiezhu Yang
>
On Wed, Dec 30, 2020 at 11:38 AM Christian Hewitt
wrote:
>
> The Shenzen AZW (Beelink) GS-King-X is based on the Amlogic W400 reference
> board with an S922X-H chip.
>
> - 4GB LPDDR4 RAM
> - 64GB eMMC storage
> - 10/100/1000 Base-T Ethernet
> - AP6356S Wireless (802.11 a/b/g/n/ac, BT 4.1)
> -
On Wed, Dec 30, 2020 at 11:38 AM Christian Hewitt
wrote:
>
> The Shenzen AZW (Beelink) GS-King-X is based on the Amlogic W400 reference
> board with an S922X-H chip.
>
> Signed-off-by: Christian Hewitt
> Acked-by: Rob Herring
Reviewed-by: Martin Blumenstingl
On Tue, Sep 08, 2020 at 11:36:22PM +0200, Arnd Bergmann wrote:
> It sounds unwise to let user space pass an unchecked 32-bit
> offset into a kernel structure in an ioctl. This is an unsigned
> variable, so checking the upper bound for the size of the structure
> it points into is sufficient to
Hi Linus,
On Mon, Dec 21, 2020 at 4:28 PM Martin Blumenstingl
wrote:
>
> Hi Linus,
>
> On Wed, Oct 7, 2020 at 9:44 PM Martin Blumenstingl
> wrote:
> [...]
> > > As noted on the earlier patches I think this should be folded into the
> > > existing XHCI USB driver in drivers/usb/host/xhci-pci.c
On 12/25/20 6:15 PM, William Breathitt Gray wrote:
Changes in v7:
- Implemented u32 enums; enum types can now be used directly for
callbacks and values
- Fixed refcount underflow bug
- Refactored all err check to check for err < 0; this should help
prevent future oversights on
On 12/25/20 6:15 PM, William Breathitt Gray wrote:
diff --git a/drivers/counter/ti-eqep.c b/drivers/counter/ti-eqep.c
index a60aee1a1a29..6c058b93dc98 100644
--- a/drivers/counter/ti-eqep.c
+++ b/drivers/counter/ti-eqep.c
-static ssize_t ti_eqep_position_floor_write(struct counter_device
Hi Neil and all interested people,
in the past there were concerns about how some of the components are
coupled in our Meson DRM driver(s).
With this discussion I would like to achieve four things:
1. understand the current issues that we have
2. come up with a TODO list of things that need to be
/kernel/git/broonie/regulator.git
for-next
config: arm-randconfig-r004-20201230 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project
3c0d36f977d9e012b245c796ddc8596ac3af659b)
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel
-a005-20201230
i386 randconfig-a006-20201230
i386 randconfig-a004-20201230
i386 randconfig-a003-20201230
i386 randconfig-a002-20201230
i386 randconfig-a001-20201230
x86_64 randconfig-a005-20201230
x86_64
Hi Sergei,
On Wed, Dec 30, 2020 at 4:27 PM Sergei Shtylyov
wrote:
>
> On 12/30/20 5:57 PM, Lad Prabhakar wrote:
>
> > Replace C++ style comment with C style.
>
>Note that the switch to // was made following the SPI maintainer's
> request...
>
Thanks for letting me know, let's drop this
On Wed, Dec 30, 2020 at 4:55 PM Arnd Bergmann wrote:
>
> Change the definition of CPUIDLE_METHOD_OF_DECLARE() to silently
> drop the table and all code referenced from it when CONFIG_CPU_IDLE
> is disabled.
Re-Cc'ing Nick (Arnd's email had a wrong address).
Cheers,
Miguel
Add the bindings for the bq256xx series of battery charging ICs.
Datasheets:
- https://www.ti.com/lit/ds/symlink/bq25600.pdf
- https://www.ti.com/lit/ds/symlink/bq25601.pdf
- https://www.ti.com/lit/ds/symlink/bq25600d.pdf
- https://www.ti.com/lit/ds/symlink/bq25601d.pdf
-
Hello,
This patchset introduces the bq256xx family of charging ICs. The bq256xx
ICs are highly integrated, buck, switching chargers intended for use in
smartphones, tablets, and portable electronics.
Ricardo Rivera-Matos (2):
dt-bindings: power: Add the bq256xx dt bindings
power: supply:
The BQ256XX family of devices are highly integrated buck chargers
for single cell batteries.
Signed-off-by: Ricardo Rivera-Matos
v5 - adds power_supply_put_battery_info() and devm_add_action_or_rest() calls
v6 - implements bq256xx_remove function
v7 - applies various fixes
- implements
On Wed, Dec 30, 2020 at 4:55 PM Arnd Bergmann wrote:
>
> Change the definition of CPUIDLE_METHOD_OF_DECLARE() to silently
> drop the table and all code referenced from it when CONFIG_CPU_IDLE
> is disabled.
Looks good,
Reviewed-by: Miguel Ojeda
Cheers,
Miguel
On 17.11.2020 17:57, Rafael J. Wysocki wrote:
> On Tue, Nov 17, 2020 at 5:38 PM Bjorn Helgaas wrote:
>>
>> [+to Rafael, author of the commit you mentioned,
>> +cc Mika, Kai Heng, Lukas, linux-pm, linux-kernel]
>>
>> On Tue, Nov 17, 2020 at 04:56:09PM +0100, Heiner Kallweit wrote:
>>> More than 10
Sebastian,
On 10/19/20 4:53 PM, Sebastian Reichel wrote:
Hi Ricardo,
On Mon, Oct 05, 2020 at 04:47:09PM -0500, Ricardo Rivera-Matos wrote:
The BQ256XX family of devices are highly integrated buck chargers
for single cell batteries.
Signed-off-by: Ricardo Rivera-Matos
v5 - adds
In 4.x kernel a dst in DST_OBSOLETE_DEAD state is associated
with loopback net_device and leads to loopback neighbour. It
leads to an ethernet header with all zero addresses.
A very troubling case is working with mac80211 and ath9k.
A packet with all zero source MAC address to mac80211 will
On Wed, Dec 30, 2020 at 05:51:29PM +0200, Iskren Chernev wrote:
> From: Brian Masney
>
> Add support for the a3xx GPU
>
> Signed-off-by: Brian Masney
Reviewed-by: Brian Masney
On Wed, Dec 30, 2020 at 05:29:42PM +0200, Iskren Chernev wrote:
> From: Craig Tatlor
>
> vram.size is needed when binding a gpu without an iommu and is defined
> in msm_init_vram(), so run that before binding it.
>
> Signed-off-by: Craig Tatlor
For the series:
Reviewed-by: Brian Masney
On Wed, Dec 30, 2020 at 12:56:27AM +0100, Donald Buczek wrote:
> Threads, which committed items to the CIL, wait in the xc_push_wait
> waitqueue when used_space in the push context goes over a limit. These
> threads need to be woken when the CIL is pushed.
>
> The CIL push worker tries to avoid
On Wed, Dec 30, 2020 at 1:25 AM YANG LI wrote:
>
> The error is due to dereference a null pointer in function
> reset_one_sub_crq_queue():
>
> if (!scrq) {
> netdev_dbg(adapter->netdev,
>"Invalid scrq reset. irq (%d) or msgs(%p).\n",
> scrq->irq, scrq->msgs);
>
On 30/12/2020 14:43:21-0700, Nathan Chancellor wrote:
> On Wed, Dec 30, 2020 at 10:40:53PM +0100, Alexandre Belloni wrote:
> > On 30/12/2020 16:23:56-0500, Nicolas Pitre wrote:
> > > On Wed, 30 Dec 2020, Arnd Bergmann wrote:
> > >
> > > > From: Arnd Bergmann
> > > >
> > > > clang warns because
Yes, good call!
Reposted with allocation failure handling.
Thanks,
Ignat
On Wed, Dec 30, 2020 at 6:11 PM Mikulas Patocka wrote:
>
> Hi
>
> This patch doesn't handle allocation failure gracefully.
>
> Mikulas
>
>
>
> On Tue, 29 Dec 2020, Ignat Korchagin wrote:
>
> > Commit
Commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 made it possible for some code
paths in dm-crypt to be executed in softirq context, when the underlying driver
processes IO requests in interrupt/softirq context.
When Crypto API backlogs a crypto request, dm-crypt uses wait_for_completion to
avoid
Changes from v1:
0001: Handle memory allocation failure for GFP_ATOMIC
Ignat Korchagin (2):
dm crypt: use GFP_ATOMIC when allocating crypto requests from softirq
dm crypt: do not wait for backlogged crypto request completion in
softirq
drivers/md/dm-crypt.c | 135
Commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 made it possible for some code
paths in dm-crypt to be executed in softirq context, when the underlying driver
processes IO requests in interrupt/softirq context.
In this case sometimes when allocating a new crypto request we may get a
stacktrace
On Wed, Dec 30, 2020 at 10:40:53PM +0100, Alexandre Belloni wrote:
> On 30/12/2020 16:23:56-0500, Nicolas Pitre wrote:
> > On Wed, 30 Dec 2020, Arnd Bergmann wrote:
> >
> > > From: Arnd Bergmann
> > >
> > > clang warns because the added __maybe_unused attribute is in
> > > the wrong place:
> >
On 30/12/2020 16:23:56-0500, Nicolas Pitre wrote:
> On Wed, 30 Dec 2020, Arnd Bergmann wrote:
>
> > From: Arnd Bergmann
> >
> > clang warns because the added __maybe_unused attribute is in
> > the wrong place:
> >
> > drivers/i3c/master/mipi-i3c-hci/core.c:780:21: error: attribute declaration
The glibc wrapper doesn't provide the third argument.
Simplify the info about the (unused) kernel parameter
to the minimum that is useful.
kernels <=2.6.23 are EOL since a long time ago.
The old info is commented out instead of removed.
..
$ syscall='getcpu';
$ ret='int';
$ find glibc/
On Wed, Dec 30, 2020 at 08:04:49PM +, Al Viro wrote:
> On Wed, Dec 30, 2020 at 03:01:25PM +0800, YANG LI wrote:
> > Goto statement jumping will cause lock to be executed again without
> > executing unlock, placing the lock statement in front of goto
> > label to fix this problem.
> >
> >
On 12/25/20 6:15 PM, William Breathitt Gray wrote:
diff --git a/include/uapi/linux/counter.h b/include/uapi/linux/counter.h
new file mode 100644
index ..7585dc9db19d
--- /dev/null
+++ b/include/uapi/linux/counter.h
@@ -0,0 +1,123 @@
+/* SPDX-License-Identifier: GPL-2.0 WITH
On Mon, 28 Dec 2020 16:14:17 -0500 Konstantin Ryabitsev wrote:
> On Mon, Dec 28, 2020 at 01:05:26PM -0800, Florian Fainelli wrote:
> > On 12/28/2020 12:23 PM, Konstantin Ryabitsev wrote:
> > > On Thu, Dec 24, 2020 at 01:57:40PM -0800, Florian Fainelli wrote:
> > Konstantin, would you be
Hello RT-list!
I'm pleased to announce the 4.14.213-rt103 stable release.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch: v4.14-rt
Head SHA1: af29de213eb180fe8a0db0d4aadde83f1a74be13
Or to build 4.14.213-rt103
crypto: Fix divide error in do_xor_speed()
From: Kirill Tkhai
Latest (but not only latest) linux-next panics with divide
error on my QEMU setup.
The patch at the bottom of this message fixes the problem.
xor: measuring software checksum speed
divide error: [#1] PREEMPT SMP KASAN
PREEMPT
On 12/30/20 10:22 PM, Bert Vermeulen wrote:
The RTL838x/839x family of SoCs are Realtek switches with an embedded
MIPS core.
Oops, forgot patch version note:
v3:
- all code removed, the base system is now only device tree files and docs
and some build config.
- ioremap.h restored to the v1
1 - 100 of 485 matches
Mail list logo
