Am 15.11.24 um 11:51 schrieb Uwe Kleine-König:
Hello Werner,
On Fri, Nov 15, 2024 at 10:40:56AM +0100, Werner Sembach wrote:
Then why does the proprietary NVIDIA driver exist?
Please don't use NVIDIA's behaviour as a blueprint for your actions.
INAL, but I would not recommend to deduce from
Am 15.11.24 um 11:22 schrieb Greg KH:
On Fri, Nov 15, 2024 at 10:40:56AM +0100, Werner Sembach wrote:
Am 15.11.24 um 10:18 schrieb Greg KH:
On Fri, Nov 15, 2024 at 10:00:23AM +0100, Werner Sembach wrote:
I guess what I try to convince you and others is that we _are_ taking Open
Source licens
Hello Werner,
On Fri, Nov 15, 2024 at 10:40:56AM +0100, Werner Sembach wrote:
> Then why does the proprietary NVIDIA driver exist?
Please don't use NVIDIA's behaviour as a blueprint for your actions.
INAL, but I would not recommend to deduce from "NVIDIA does it and
wasn't tried to stop" (for any
On Fri, Nov 15, 2024 at 10:40:56AM +0100, Werner Sembach wrote:
>
> Am 15.11.24 um 10:18 schrieb Greg KH:
> > On Fri, Nov 15, 2024 at 10:00:23AM +0100, Werner Sembach wrote:
> > > I guess what I try to convince you and others is that we _are_ taking Open
> > > Source licenses seriously, but still
Am 15.11.24 um 10:18 schrieb Greg KH:
On Fri, Nov 15, 2024 at 10:00:23AM +0100, Werner Sembach wrote:
I guess what I try to convince you and others is that we _are_ taking Open
Source licenses seriously, but still there are mistakes to be made,
especially with complex projects like the Linux k
On Fri, Nov 15, 2024 at 10:00:23AM +0100, Werner Sembach wrote:
> I guess what I try to convince you and others is that we _are_ taking Open
> Source licenses seriously, but still there are mistakes to be made,
> especially with complex projects like the Linux kernel, e.g. I'm not aware
> of any ot
Hello Uwe,
Am 15.11.24 um 08:29 schrieb Uwe Kleine-König:
Hello Werner,
On Fri, Nov 15, 2024 at 07:09:49AM +0100, Werner Sembach wrote:
Am 15.11.24 um 05:43 schrieb Greg KH:
On Thu, Nov 14, 2024 at 11:49:04AM +0100, Werner Sembach wrote:
Am 14.11.24 um 11:31 schrieb Uwe Kleine-König:
the ke
Hello Werner,
On Fri, Nov 15, 2024 at 07:09:49AM +0100, Werner Sembach wrote:
> Am 15.11.24 um 05:43 schrieb Greg KH:
> > On Thu, Nov 14, 2024 at 11:49:04AM +0100, Werner Sembach wrote:
> > > Am 14.11.24 um 11:31 schrieb Uwe Kleine-König:
> > > > the kernel modules provided by Tuxedo on
> > > > ht
On Fri, Nov 15, 2024 at 07:09:49AM +0100, Werner Sembach wrote:
> Hi,
>
> Am 15.11.24 um 05:43 schrieb Greg KH:
> > On Thu, Nov 14, 2024 at 11:49:04AM +0100, Werner Sembach wrote:
> > > Hello,
> > >
> > > Am 14.11.24 um 11:31 schrieb Uwe Kleine-König:
> > > > Hello,
> > > >
> > > > the kernel mo
Hi,
Am 15.11.24 um 05:43 schrieb Greg KH:
On Thu, Nov 14, 2024 at 11:49:04AM +0100, Werner Sembach wrote:
Hello,
Am 14.11.24 um 11:31 schrieb Uwe Kleine-König:
Hello,
the kernel modules provided by Tuxedo on
https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers
are licensed
On Thu, Nov 14, 2024 at 11:49:04AM +0100, Werner Sembach wrote:
> Hello,
>
> Am 14.11.24 um 11:31 schrieb Uwe Kleine-König:
> > Hello,
> >
> > the kernel modules provided by Tuxedo on
> > https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers
> > are licensed under GPLv3 or later.
Hello,
Am 14.11.24 um 12:14 schrieb Uwe Kleine-König:
Hello,
On 11/14/24 11:49, Werner Sembach wrote:
Am 14.11.24 um 11:31 schrieb Uwe Kleine-König:
the kernel modules provided by Tuxedo on
https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers
are licensed under GPLv3 or late
On Thu Nov 14, 2024 at 11:31 AM CET, Uwe Kleine-König wrote:
> Hello,
>
> the kernel modules provided by Tuxedo on
> https://protect2.fireeye.com/v1/url?k=2f239e82-70bfb7a8-2f2215cd-000babe598f7-32952349600b722d&q=1&e=9535a8fa-5a9d-4d94-a12d-ff39b9d3b9cf&u=https%3A%2F%2Fgitlab.com%2Ftuxedocomputers
Hello,
On 11/14/24 11:49, Werner Sembach wrote:
Am 14.11.24 um 11:31 schrieb Uwe Kleine-König:
the kernel modules provided by Tuxedo on
https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers
are licensed under GPLv3 or later. This is incompatible with the
kernel's license and so
Hello,
Am 14.11.24 um 11:31 schrieb Uwe Kleine-König:
Hello,
the kernel modules provided by Tuxedo on
https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers
are licensed under GPLv3 or later. This is incompatible with the
kernel's license and so makes it impossible for distribut
Hello,
the kernel modules provided by Tuxedo on
https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers
are licensed under GPLv3 or later. This is incompatible with the
kernel's license and so makes it impossible for distributions and other
third parties to support these at least in
On Mon, 11 Nov 2024 16:18:54 +, Mark Brown wrote:
> The PAC tests currently generate a very small number of false failures
> since the limited size of PAC keys, especially with fewer bits allocated
> for PAC due to larger VA, means collisions in generated PACs are
> possible even if the PAC key
On 11/6/2024 9:02 PM, Frederic Weisbecker wrote:
> Hello,
>
> Please find below the RCU NOCB patches targeted for the upcoming
> merge window.
>
> Yue Haibing (1):
> rcu: Remove unused declaration rcu_segcblist_offload()
>
> Zqiang (1):
> rcu/nocb: Fix missed RCU barrier on deoffloading
>
>
The PAC tests currently generate a very small number of false failures
since the limited size of PAC keys, especially with fewer bits allocated
for PAC due to larger VA, means collisions in generated PACs are
possible even if the PAC keys are different. The test tries to work around
this by testin
Hello,
Please find below the RCU NOCB patches targeted for the upcoming
merge window.
Yue Haibing (1):
rcu: Remove unused declaration rcu_segcblist_offload()
Zqiang (1):
rcu/nocb: Fix missed RCU barrier on deoffloading
kernel/rcu/rcu_segcblist.h | 1 -
kernel/rcu/tree_nocb.h | 13
Hi,
In /proc/PID/stat, there is the kstkesp field which is the stack pointer of
a thread. While the thread is active, this field reads zero. But during a
coredump, it should have a valid value.
However, at the moment, kstkesp is zero even during coredump.
The first commit fixes this problem, and
On 10/28/24 13:08, Alessandro Zanni wrote:
Address issues related to arithmetic expression compatibility and
cpupower operand expected.
Command to test:
make kselftest TARGETS=intel_pstate
Alessandro Zanni (2):
selftests/intel_pstate: fix operand expected
selftests/intel_pstate: c
One of the things that fp-stress does to stress the floating point
context switching is send signals to the test threads it spawns.
Currently we do this once per second but as suggested by Mark Rutland if
we increase this we can improve the chances of triggering any issues
with context switching th
Address issues related to arithmetic expression compatibility and
cpupower operand expected.
Command to test:
make kselftest TARGETS=intel_pstate
Alessandro Zanni (2):
selftests/intel_pstate: fix operand expected
selftests/intel_pstate: cpupower command not found
tools/testing/selft
This series implements feature detection of hardware virtualization on
Linux and macOS; the latter being my primary use case.
This yields approximately a 6x improvement using HVF on M3 Pro.
Signed-off-by: Tamir Duberstein
---
Tamir Duberstein (2):
kunit: add fallback for os.sched_getaffini
With the transition of pd-mapper into the kernel, the timing was altered
such that on some targets the initial rpmsg_send() requests from
pmic_glink clients would be attempted before the firmware had announced
intents, and the firmware reject intent requests.
Fix this
Signed-off-by: Bjorn Anderss
On Wed, Oct 16, 2024 at 11:41:39AM -0500, Andrew Davis wrote:
> Hello all,
>
> This is a follow up to [0] that adds the same for the other two K3
> RemoteProc drivers. Series is based on rproc-next branch.
>
> Thanks,
> Andrew
>
> [0] https://lore.kernel.org/lkml/20241007132441.2732215-1-a...@ke
Hello all,
This is a follow up to [0] that adds the same for the other two K3
RemoteProc drivers. Series is based on rproc-next branch.
Thanks,
Andrew
[0] https://lore.kernel.org/lkml/20241007132441.2732215-1-a...@kernel.org/
Andrew Davis (2):
remoteproc: k3-dsp: Add compile testing support
On Thu, 3 Oct 2024 21:17:09 + Edward Liaw wrote:
> On Android arm, pthread_create followed by a fork caused a deadlock in
> the case where the fork required work to be completed by the created
> thread.
>
> Updated the synchronization primitive to use pthread_barrier instead of
> atomic_boo
On Android arm, pthread_create followed by a fork caused a deadlock in
the case where the fork required work to be completed by the created
thread.
Updated the synchronization primitive to use pthread_barrier instead of
atomic_bool.
Applied the same fix to the wp-fork-with-event test.
Edward Lia
Introduce ptr_eq() to compare two addresses while preserving the address
dependencies for later use of the address. It should be used when
comparing an address returned by rcu_dereference().
Thanks,
Mathieu
Cc: Greg Kroah-Hartman
Cc: Sebastian Andrzej Siewior
Cc: "Paul E. McKenney"
Cc: Will D
On Tue, Sep 24 2024 at 09:56, Shuah Khan wrote:
> The first patch in this two patch fixes warn_unused_result compile
> time warning in posix_timers test.
>
> The second patch removes local NSEC_PER_SEC and USEC_PER_SEC defines.
> NSEC_PER_SEC and USEC_PER_SEC are defines in several timers tests.
>
> On Sep 25, 2024, at 21:08, Marcos Paulo de Souza wrote:
>
> On Wed, 2024-09-25 at 14:40 +0800, Wardenjohn wrote:
>> As previous discussion, maintainers think that patch-level sysfs
>> interface is the
>> only acceptable way to maintain the information of the order that
>> klp_patch is
>> app
On Wed, 2024-09-25 at 14:40 +0800, Wardenjohn wrote:
> As previous discussion, maintainers think that patch-level sysfs
> interface is the
> only acceptable way to maintain the information of the order that
> klp_patch is
> applied to the system.
>
> However, the previous patch introduce klp_ops
As previous discussion, maintainers think that patch-level sysfs interface is
the
only acceptable way to maintain the information of the order that klp_patch is
applied to the system.
However, the previous patch introduce klp_ops into klp_func is a optimization
methods of the patch introducing
The first patch in this two patch fixes warn_unused_result compile
time warning in posix_timers test.
The second patch removes local NSEC_PER_SEC and USEC_PER_SEC defines.
NSEC_PER_SEC and USEC_PER_SEC are defines in several timers tests.
These defines are inconsistent with variations of ULL, LL,
On 9/23/24 09:42, Pedro Orlando wrote:
+CC linux-kselftest
---
On 22/09/2024 17:16, Gabriela Bittencourt wrote:
Hey all,
We are making these changes as part of a KUnit Hackathon at LKCamp [1].
This patch sets out to refactor fs/unicode/utf8-selftest.c to KUnit tests.
The first commit is
+CC linux-kselftest
---
On 22/09/2024 17:16, Gabriela Bittencourt wrote:
Hey all,
We are making these changes as part of a KUnit Hackathon at LKCamp [1].
This patch sets out to refactor fs/unicode/utf8-selftest.c to KUnit tests.
The first commit is the refactoring itself from self test i
As previous discussion, maintainers think that patch-level sysfs interface is
the
only acceptable way to maintain the information of the order that klp_patch is
applied to the system.
However, the previous patch introduce klp_ops into klp_func is a optimization
methods of the patch introducing
On Wed, Sep 11, 2024 at 10:50:13AM +0200, Heiko Carstens wrote:
> Two s390 fixes to make vdso selftests running on s390.
>
> Jason, given that you carry already a lot of changes for vdso
> selftests I guess these should be routed via the random tree.
>
> Patches apply on top of current random.git
Two s390 fixes to make vdso selftests running on s390.
Jason, given that you carry already a lot of changes for vdso
selftests I guess these should be routed via the random tree.
Patches apply on top of current random.git master branch.
Thanks,
Heiko
Heiko Carstens (1):
selftests: vDSO: fix v
From: Carlos Bilbao
Initialize speed and duplex for virtio_net_config to UNKNOWN (mlx5_vdpa
vDPA devices currently do not support VIRTIO_NET_F_SPEED_DUPLEX). Include
logic to update these fields (for VHOST_VDPA_SET_CONFIG) -- even if
hardware support is not capable yet (Make a note of that). Also
Add the bindings and driver changes for DSP support on the QCS8300
platform in order to enable the ADSP, CDSP and GPDSP remoteproc to
boot.
Signed-off-by: Jingyi Wang
---
Jingyi Wang (2):
dt-bindings: remoteproc: qcom,sa8775p-pas: Document QCS8300 remoteproc
remoteproc: qcom: pas: Add QCS8300
On Fri, Aug 23, 2024 at 10:03:05PM +0900, Masahiro Yamada wrote:
> On Thu, Aug 22, 2024 at 5:36 PM Michal Suchánek wrote:
> >
> > Hello,
> >
> > On Thu, Aug 22, 2024 at 01:05:11AM -0500, Lucas De Marchi wrote:
> > > On Tue, Dec 19, 2023 at 05:37:31PM GMT, Masahiro Yamada wrote:
> > > > On Thu, Dec
On Thu, Aug 22, 2024 at 5:36 PM Michal Suchánek wrote:
>
> Hello,
>
> On Thu, Aug 22, 2024 at 01:05:11AM -0500, Lucas De Marchi wrote:
> > On Tue, Dec 19, 2023 at 05:37:31PM GMT, Masahiro Yamada wrote:
> > > On Thu, Dec 7, 2023 at 3:37 AM Lucas De Marchi
> > > wrote:
> > > >
> > > > On Fri, Nov
On 2024/08/21, Nathan Chancellor wrote:
> On Tue, Dec 19, 2023 at 05:37:31PM +0900, Masahiro Yamada wrote:
> > On Thu, Dec 7, 2023 at 3:37 AM Lucas De Marchi
> > wrote:
> > >
> > > On Fri, Nov 10, 2023 at 01:13:53PM +0100, Michal Suchanek wrote:
> > > >Hello,
> > > >
> > > >This is resend of the
Hello,
On Thu, Aug 22, 2024 at 01:05:11AM -0500, Lucas De Marchi wrote:
> On Tue, Dec 19, 2023 at 05:37:31PM GMT, Masahiro Yamada wrote:
> > On Thu, Dec 7, 2023 at 3:37 AM Lucas De Marchi
> > wrote:
> > >
> > > On Fri, Nov 10, 2023 at 01:13:53PM +0100, Michal Suchanek wrote:
> > > >Hello,
> > >
On Tue, Dec 19, 2023 at 05:37:31PM GMT, Masahiro Yamada wrote:
On Thu, Dec 7, 2023 at 3:37 AM Lucas De Marchi wrote:
On Fri, Nov 10, 2023 at 01:13:53PM +0100, Michal Suchanek wrote:
>Hello,
>
>This is resend of the last patch in the series that adds prefix support
>to kernel module location to
On Wed, Aug 21, 2024 at 10:58:43AM GMT, Nathan Chancellor wrote:
Did this conversation go anywhere? After the upgrade to kmod 33 in Arch
no, it stalled, thanks for reminding me. I will follow up on it.
Lucas De Marchi
On Tue, Dec 19, 2023 at 05:37:31PM +0900, Masahiro Yamada wrote:
> On Thu, Dec 7, 2023 at 3:37 AM Lucas De Marchi
> wrote:
> >
> > On Fri, Nov 10, 2023 at 01:13:53PM +0100, Michal Suchanek wrote:
> > >Hello,
> > >
> > >This is resend of the last patch in the series that adds prefix support
> > >t
On Mon, Jul 22, 2024 at 11:06:20AM +0200, Petr Pavlu wrote:
> Allow enabling the in-kernel module decompression support separately,
> without requiring to enable also the automatic compression during
> 'make modules_install'.
Applied and pushed, thanks!
Luis
Now that "reserve_mem" kernel command line option is upstream, add a patch
to use it with the ring buffer boot up mappings. That is:
reserve_mem=12M:4096:trace trace_instance=boot_mapped@trace
Will allocate 12 megabytes at boot up that is aligned by 4096 bytes and
label it with "trace". A tra
On Wed, 7 Aug 2024 13:51:37 +0200
Mathias Krause wrote:
> Hi Steven,
>
> We ran into yet another tracefs related bug but, fortunately, were able
> to root cause it ourselves.
>
> The problem only occurs when CONFIG_RANDSTRUCT is enabled and one gets
> (un)lucky to hit a random seed that'll ove
Hi Steven,
We ran into yet another tracefs related bug but, fortunately, were able
to root cause it ourselves.
The problem only occurs when CONFIG_RANDSTRUCT is enabled and one gets
(un)lucky to hit a random seed that'll overlay the 'rcu' member of the
union with a list_head in 'vfs_inode' -- qui
The dts and dtsi add support for msm8916 variant of Samsung Galaxy J3
SM-J320YZ smartphone released in 2016.
Add a device tree for SM-J320YZ with initial support for:
- GPIO keys
- SDHCI (internal and external storage)
- USB Device Mode
- UART (on USB connector via the SM5703 MUIC)
- WCNSS (WiFi/
Lock Holder Preemption (LHP) is classic problem especially on VM, if
lock holder vCPU is preempted on host, other vCPUs will do busy looping
and waste pCPU time. And there is no hw Pause Loop Exiting (PLE) supported
on LoongArch system also.
Here pavavirt qspinlock is introduced, by the kernel com
Allow enabling the in-kernel module decompression support separately,
without requiring to enable also the automatic compression during
'make modules_install'.
Petr Pavlu (2):
module: Split modules_install compression and in-kernel decompression
module: Clean up the description of MODULE_SIG_
hi,
the uretprobe syscall clashed in linux-next tree with xattrat syscalls,
so after discussing with Arnd, changing the syscall number to 467.
I'm also changing the ABI to 'common' which will ease up the global
scripts/syscall.tbl management.
I split the change into syscall_64.tbl and selftest ch
Hi Wolfram,
On Fri, Jul 12, 2024 at 08:34:11AM GMT, Wolfram Sang wrote:
> On Fri, Jul 12, 2024 at 01:19:24AM +0200, Andi Shyti wrote:
> > Hi,
> >
> > while reviewing Wolfram's series, I received some delivery
> > failure notifications for e-mails that don't exist anymore.
> >
> > With this serie
On Fri, Jul 12, 2024 at 01:19:24AM +0200, Andi Shyti wrote:
> Hi,
>
> while reviewing Wolfram's series, I received some delivery
> failure notifications for e-mails that don't exist anymore.
>
> With this series I'm removing:
>
> - Conghui Chen
> - Thor Thayer
Fixes for these two are alread
Hi,
while reviewing Wolfram's series, I received some delivery
failure notifications for e-mails that don't exist anymore.
With this series I'm removing:
- Conghui Chen
- Thor Thayer
unfortunately both from Intel :-(
In the case of Altera's subsystems (except for the i2c), I didn't
really
On Thu, Jul 04, 2024 at 03:05:05PM +0200, Peter Zijlstra wrote:
> And how are we to ascertain the software using these hooks is deemed
> secure? What security risks are there for the kernel if a malicious
> userspace process asks for these rights?
>
> The kernel must assume malice on the part of u
Thanks for the response, Dave.
On Wed, Jul 03, 2024 at 05:18:22PM -0700, Dave Hansen wrote:
>
> Could we please be frank and transparent about what you actually want
> here and how you expect this mechanism to be used?
>
Sorry for being unclear. open-vm-tools is currently broken on TDX and
the
On Wed, Jul 03, 2024 at 11:35:59PM +, Tim Merrifield wrote:
> VMCALL and VMMCALL instructions are used by x86 guests to request services
> from the host VMM. Both VMCALL and VMMCALL are not restricted to CPL 0.
> This allows userspace software like open-vm-tools to communicate directly
> with t
On 7/3/24 16:35, Tim Merrifield wrote:
> VMCALL and VMMCALL instructions are used by x86 guests to request services
> from the host VMM. Both VMCALL and VMMCALL are not restricted to CPL 0.
> This allows userspace software like open-vm-tools to communicate directly
> with the VMM.
Could we please
VMCALL and VMMCALL instructions are used by x86 guests to request services
from the host VMM. Both VMCALL and VMMCALL are not restricted to CPL 0.
This allows userspace software like open-vm-tools to communicate directly
with the VMM.
In the context of confidential VMs, direct communication with t
On Wed, 26 Jun 2024 22:12:36 +0300, Dmitry Baryshkov wrote:
> While refactoring pd-mapper to use auxiliary bus for the PD mapper
> instantiation I forgot to select the bus in Kconfig entries. Fix it now.
>
>
Applied, thanks!
[1/2] soc: qcom: add missing pd-mapper dependencies
commit: b8
While refactoring pd-mapper to use auxiliary bus for the PD mapper
instantiation I forgot to select the bus in Kconfig entries. Fix it now.
Signed-off-by: Dmitry Baryshkov
---
Dmitry Baryshkov (2):
soc: qcom: add missing pd-mapper dependencies
remoteproc: qcom: select AUXILIARY_BUS
On Fri, 21 Jun 2024 10:42:29 +0200, Luca Weiss wrote:
> With the PM8008 regulator driver scheduled for Linux v6.11[0] let's add
> the dts bits for Fairphone 4 and Fairphone 5 which both use this PMIC
> for powering the camera sensors - and the pull-up for the CCI (camera
> I2C bus).
>
> [0]
> h
With the PM8008 regulator driver scheduled for Linux v6.11[0] let's add
the dts bits for Fairphone 4 and Fairphone 5 which both use this PMIC
for powering the camera sensors - and the pull-up for the CCI (camera
I2C bus).
[0]
https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/log/?h=ib-m
On Tue, 18 Jun 2024 15:30:53 +0200, Luca Weiss wrote:
> As per individual commit messages:
>
> Without explicitly specifying names for the regulators they are named
> based on the DeviceTree node name. This results in multiple regulators
> with the same name, making debug prints and regulator_su
As per individual commit messages:
Without explicitly specifying names for the regulators they are named
based on the DeviceTree node name. This results in multiple regulators
with the same name, making debug prints and regulator_summary impossible
to reason about.
Signed-off-by: Luca Weiss
---
Hi,
On Fri, 31 May 2024, Joe Lawrence wrote:
> On 5/31/24 07:23, Miroslav Benes wrote:
> > Hi,
> >
> > On Tue, 21 Jul 2020, Joe Lawrence wrote:
> >
> >> In light of [PATCH] Revert "kbuild: use -flive-patching when
> >> CONFIG_LIVEPATCH is enabled" [1], we should add some loud disclaimers
> >> a
On Mon, 03 Jun 2024 02:28:55 -0400, Alexandre Messier wrote:
> Add an initial device tree to support the HTC One (M8) smartphone,
> aka "htc,m8".
>
>
Applied, thanks!
[2/2] ARM: dts: qcom: Add initial support for HTC One (M8)
commit: 0e8a41e511c98f5f5796c0dca8ff983d1c967b93
Best regard
On Mon, 03 Jun 2024 02:28:55 -0400, Alexandre Messier wrote:
> Add an initial device tree to support the HTC One (M8) smartphone,
> aka "htc,m8".
>
> Signed-off-by: Alexandre Messier
> ---
> Alexandre Messier (2):
> dt-bindings: arm: qcom: add HTC One (M8)
> ARM: dts: qcom: Add init
Add an initial device tree to support the HTC One (M8) smartphone,
aka "htc,m8".
Signed-off-by: Alexandre Messier
---
Alexandre Messier (2):
dt-bindings: arm: qcom: add HTC One (M8)
ARM: dts: qcom: Add initial support for HTC One (M8)
Documentation/devicetree/bindings/arm/qcom.yaml
On 5/31/24 07:23, Miroslav Benes wrote:
> Hi,
>
> On Tue, 21 Jul 2020, Joe Lawrence wrote:
>
>> In light of [PATCH] Revert "kbuild: use -flive-patching when
>> CONFIG_LIVEPATCH is enabled" [1], we should add some loud disclaimers
>> and explanation of the impact compiler optimizations have on
>>
Hi,
On Tue, 21 Jul 2020, Joe Lawrence wrote:
> In light of [PATCH] Revert "kbuild: use -flive-patching when
> CONFIG_LIVEPATCH is enabled" [1], we should add some loud disclaimers
> and explanation of the impact compiler optimizations have on
> livepatching.
>
> The first commit provides detaile
On Thu, 25 Apr 2024 21:14:29 +0200, Luca Weiss wrote:
> The mboxes property has been supported in those bindings since a while
> and was always meant to the replace qcom,ipc properties, so let's mark
> qcom,ipc as deprecated - and update the examples to use mboxes.
>
> Related:
> https://lore.ke
On Thu, 18 Apr 2024 08:36:53 +0200, Luca Weiss wrote:
> With the patches to add vibration support for PMI632 finally applied,
> let's enable this for the PMI632 PMIC and Fairphone 3 smartphone.
>
> https://lore.kernel.org/linux-arm-msm/20240416-pm8xxx-vibrator-new-design-v11-0-7b1c951e1...@quici
On Mon, 08 Apr 2024 21:32:02 +0200, Luca Weiss wrote:
> Finally fix a warning about the apcs-global syscon used on msm8974 that
> has been around forever.
>
>
Applied, thanks!
[2/2] ARM: dts: qcom: msm8974: Use proper compatible for APCS syscon
commit: c133cfc12cd717b72ce534477415446e1c
On Fri, 10 May 2024 14:27:07 +0200, Luca Weiss wrote:
> Validated on Fairphone 5 (QCM6490) smartphone by using DisplayPort over
> USB-C audio, connected to a TV, with a basic UCM to enable
> 'DISPLAY_PORT_RX Audio Mixer MultiMedia1':
> https://gitlab.com/postmarketOS/pmaports/-/tree/master/device
Fix a race between a reader swapping a new reader page into the
ring-buffer from rb_get_reader_page() and the rb_check_pages() check
invoked at the end of the resize operation in ring_buffer_resize().
Note that a similar problem with rb_check_pages() being executed with
concurrent readers looks to
On Fri, 10 May 2024 14:27:07 +0200, Luca Weiss wrote:
> Validated on Fairphone 5 (QCM6490) smartphone by using DisplayPort over
> USB-C audio, connected to a TV, with a basic UCM to enable
> 'DISPLAY_PORT_RX Audio Mixer MultiMedia1':
> https://gitlab.com/postmarketOS/pmaports/-/tree/master/device
Validated on Fairphone 5 (QCM6490) smartphone by using DisplayPort over
USB-C audio, connected to a TV, with a basic UCM to enable
'DISPLAY_PORT_RX Audio Mixer MultiMedia1':
https://gitlab.com/postmarketOS/pmaports/-/tree/master/device/testing/device-fairphone-fp5/ucm
Unfortunately all the device-
On Thu, 25 Apr 2024 21:14:29 +0200, Luca Weiss wrote:
> The mboxes property has been supported in those bindings since a while
> and was always meant to the replace qcom,ipc properties, so let's mark
> qcom,ipc as deprecated - and update the examples to use mboxes.
>
> Related:
> https://lore.ke
Attach detach ops are needed to connect to remote processor that is
running before remoteproc driver is probed. Implement remoteproc
framework ops that enables such use case on AMD-Xilinx platforms.
Remote processor can also use On Chip sram Memory (OCM) for various
purpose. For example, for fast
On Mon, Apr 29, 2024 at 04:06:39PM +0300, Jarkko Sakkinen wrote:
> On Mon Apr 29, 2024 at 1:43 PM EEST, Dmitrii Kuvaiskii wrote:
> > SGX runtimes such as Gramine may implement EDMM-based lazy allocation of
> > enclave pages and may support MADV_DONTNEED semantics [1]. The former
> > implies #PF-bas
On Mon Apr 29, 2024 at 1:43 PM EEST, Dmitrii Kuvaiskii wrote:
> SGX runtimes such as Gramine may implement EDMM-based lazy allocation of
> enclave pages and may support MADV_DONTNEED semantics [1]. The former
> implies #PF-based page allocation, and the latter implies the usage of
> SGX_IOC_ENCLAVE
SGX runtimes such as Gramine may implement EDMM-based lazy allocation of
enclave pages and may support MADV_DONTNEED semantics [1]. The former
implies #PF-based page allocation, and the latter implies the usage of
SGX_IOC_ENCLAVE_REMOVE_PAGES ioctl.
A trivial program like below (run under Gramine
The mboxes property has been supported in those bindings since a while
and was always meant to the replace qcom,ipc properties, so let's mark
qcom,ipc as deprecated - and update the examples to use mboxes.
Related:
https://lore.kernel.org/linux-arm-msm/20240424-apcs-mboxes-v1-0-6556c47cb...@z3ntu.
With the patches to add vibration support for PMI632 finally applied,
let's enable this for the PMI632 PMIC and Fairphone 3 smartphone.
https://lore.kernel.org/linux-arm-msm/20240416-pm8xxx-vibrator-new-design-v11-0-7b1c951e1...@quicinc.com/
Patches have landed in the input tree:
https://git.kern
When the ABI was updated to prevent same name w/different args, it
missed an important corner case when fields don't end with a space.
Typically, space is used for fields to help separate them, like
"u8 field1; u8 field2". If no spaces are used, like
"u8 field1;u8 field2", then the parsing works fo
Add below patches to support MT8188 SCP core 1
[PATCH 1/2] dt-bindings: remoteproc: mediatek:
Support MT8188 dual-core SCP
[PATCH 2/2] remoteproc: mediatek: Support MT8188 SCP core 1
olivia.wen (2):
dt-bindings: remoteproc: mediatek: Support MT8188 dual-core SCP
remoteproc: med
Finally fix a warning about the apcs-global syscon used on msm8974 that
has been around forever.
Signed-off-by: Luca Weiss
---
Luca Weiss (2):
dt-bindings: mailbox: qcom: Add MSM8974 APCS compatible
ARM: dts: qcom: msm8974: Use proper compatible for APCS syscon
.../devicetree/bindin
Resolve the dt validation failure on Nexus 5.
Signed-off-by: Luca Weiss
---
Luca Weiss (2):
dt-bindings: pinctrl: qcom,pmic-gpio: Allow gpio-hog nodes
ARM: dts: qcom: msm8974-hammerhead: Update gpio hog node name
.../devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml | 12
On Mon, 18 Mar 2024 10:24:40 +0100, Luca Weiss wrote:
> One fix for dt schema validation, one for the /chosen node.
>
>
Applied, thanks!
[1/2] ARM: dts: qcom: msm8974: Add @0 to memory node name
commit: cad23ffd46e2205582f5a9e9014b3d78ec0256db
[2/2] ARM: dts: qcom: msm8974: Add empty ch
Para-virt feature steal time is added in both kvm and guest kernel side.
It is silimar with other architectures, steal time structure comes from
guest memory, also pseduo register is used to save/restore base address
of steal time structure, so that vm migration is supported also.
Bibo Mao (2):
This series brings some missing validation for the IPI buffer size
that is read from the firmware retrieved from userspace: if the FW
declares IPI buffer offset starting at an out of range address, the
driver doesn't do any validation and naively goes on with IO R/W
operation.
That poses various r
On Tue, Mar 19, 2024 at 06:15:09PM -0400, Steven Rostedt wrote:
> On Tue, 19 Mar 2024 09:07:51 -0700
> Nathan Chancellor wrote:
>
> > Hi all,
> >
> > This series fully resolves the new instance of -Wstring-compare from
> > within the __assign_str() macro. The first patch resolves a build
> > fai
1 - 100 of 4286 matches
Mail list logo
