Hi,
The main purpose of this series is to expose CPU cache attributes for
OpenRISC in sysfs using the cacheinfo API. The core implementation
to achieve this is in patch #3. Patch #1 and #2 add certain enhancements
to simplify the implementation of cacheinfo support.
The difference between this pa
Direct HLT instruction execution causes #VEs for TDX VMs which is routed
to hypervisor via TDCALL. safe_halt() routines execute HLT in STI-shadow
so IRQs need to remain disabled until the TDCALL to ensure that pending
IRQs are correctly treated as wake events. As per current TDX spec, HLT
#VE handl
On Sat, 15 Feb 2025 at 04:49, Miguel Ojeda
wrote:
>
> On Fri, Feb 14, 2025 at 8:41 AM David Gow wrote:
> >
> > After much delay, v6 of the KUnit/Rust integration patchset is here.
> > This change incorporates most of Miguels suggestions from v5 (save for
> > some of the copyright headers I wasn't
On Fri, Feb 14, 2025 at 8:41 AM David Gow wrote:
>
> After much delay, v6 of the KUnit/Rust integration patchset is here.
> This change incorporates most of Miguels suggestions from v5 (save for
> some of the copyright headers I wasn't comfortable unilaterally
> changing). This means the documenta
Hi all,
After much delay, v6 of the KUnit/Rust integration patchset is here.
This change incorporates most of Miguels suggestions from v5 (save for
some of the copyright headers I wasn't comfortable unilaterally
changing). This means the documentation is much improved, and it should
work more clea
Changes in v6:
- Move la57 check to using mmap().
- Merge kernel_has_lam() and cpu_has_lam() into lam_is_available() since
the syscall (if CONFIG_ADDRESS_MASKING is set) and cpuid check
provides the same information.
Recent change in how get_user() handles pointers [1] has a specific case
for
On Wed, Jan 15, 2025 at 07:13:26PM +0800, Celeste Liu wrote:
> The orig_a0 is missing in struct user_regs_struct of riscv, and there is
> no way to add it without breaking UAPI. (See Link tag below)
>
> Like NT_ARM_SYSTEM_CALL do, we add a new regset name NT_RISCV_ORIG_A0 to
> access original a0 r
The orig_a0 is missing in struct user_regs_struct of riscv, and there is
no way to add it without breaking UAPI. (See Link tag below)
Like NT_ARM_SYSTEM_CALL do, we add a new regset name NT_RISCV_ORIG_A0 to
access original a0 register from userspace via ptrace API.
Link:
https://lore.kernel.org/
On Wed, Nov 13, 2024 at 08:35:54AM -0600, Konstantin Shkolnyy wrote:
Parameters were created using wrong C types, which caused them to be of
wrong size on some architectures, causing problems.
The problem with SO_RCVLOWAT was found on s390 (big endian), while x86-64
didn't show it. After the fix
Parameters were created using wrong C types, which caused them to be of
wrong size on some architectures, causing problems.
The problem with SO_RCVLOWAT was found on s390 (big endian), while x86-64
didn't show it. After the fix, all tests pass on s390.
Then Stefano Garzarella pointed out that SO_V
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.
EDMM-based lazy allocation and MADV_DONTNEED sem
KVM_FEATURE_VIRT_EXTIOI is paravirt feature defined with EXTIOI
interrupt controller, it can route interrupt to 256 vCPUs and CPU
interrupt pin IP0-IP7. Now EXTIOI irqchip is emulated in user space
rather than kernel space, here interface is provided for VMM to pass
this feature to KVM hypervisor.
On 06/10/24 20:20, Qais Yousef wrote:
> Make rt_task() return true only for RT class and add new realtime_task() to
> return true for RT and DL classes to avoid some confusion the old API can
> cause.
I am not aware of any pending review comments for this series. Is it ready to
be picked up?
Tha
Make rt_task() return true only for RT class and add new realtime_task() to
return true for RT and DL classes to avoid some confusion the old API can
cause.
No functional changes intended in patch 1. Patch 2 cleans up the return type as
suggested by Steve. Patch 3 uses rt_or_dl() instead of 'realt
This small series enables virtio-net device type in VDUSE.
With it, basic operation have been tested, both with
virtio-vdpa and vhost-vdpa using DPDK Vhost library series
adding VDUSE support using split rings layout (merged in
DPDK v23.07-rc1).
Control queue support (and so multiqueue) has also b
On Tue, 05 Dec 2023 15:38:53 +0100, Luca Weiss wrote:
> This patch adds UFS host controller and Phy nodes for Qualcomm sc7280
> SoC and enable it on some sc7280-based boards.
>
> Pick up the patchset from Nitin since the last revision (v4) has been
> sent end of September and is blocking qcm6490-
Add the bindings and driver changes for DSP support on the
SM8650 platform in order to enable the aDSP, cDSP and MPSS
subsystems to boot.
Compared to SM8550, where SM8650 uses the same dual firmware files,
(dtb file and main firmware) the memory zones requirement has changed:
- cDSP: now requires
On Tue, 05 Dec 2023 15:38:53 +0100, Luca Weiss wrote:
> This patch adds UFS host controller and Phy nodes for Qualcomm sc7280
> SoC and enable it on some sc7280-based boards.
>
> Pick up the patchset from Nitin since the last revision (v4) has been
> sent end of September and is blocking qcm6490
This patch adds UFS host controller and Phy nodes for Qualcomm sc7280
SoC and enable it on some sc7280-based boards.
Pick up the patchset from Nitin since the last revision (v4) has been
sent end of September and is blocking qcm6490-fairphone-fp5 UFS.
---
Changes in v6:
- Use MX power domain for
The dax/kmem driver can potentially hot-add large amounts of memory
originating from CXL memory expanders, or NVDIMMs, or other 'device
memories'. There is a chance there isn't enough regular system memory
available to fit the memmap for this new memory. It's therefore
desirable, if all other condi
I found a inefficient behavior from multipage bvec. Large chunk DIO
scenario is that. This patch series could be a solution to improve it.
Changheun Lee (3):
bio: limit bio max size
ufs: set QUEUE_FLAG_LIMIT_BIO_SIZE
bio: add limit_bio_size sysfs
Documentation/ABI/testing/sysfs-block | 10
A bus lock [1] is acquired through either split locked access to
writeback (WB) memory or any locked access to non-WB memory. This is
typically >1000 cycles slower than an atomic operation within
a cache line. It also disrupts performance on other cores.
Although split lock can be detected by #AC
22.03.2021 01:44, Dmitry Torokhov пишет:
> Hi Dmitry,
>
> On Sat, Mar 20, 2021 at 07:02:43PM +0300, Dmitry Osipenko wrote:
>> 02.03.2021 13:21, Dmitry Osipenko пишет:
>>> Some Atmel maXTouch controllers, like mXT1386 and mXT3432S1 for example,
>>> have a WAKE line that needs to be asserted in orde
Hi Dmitry,
On Sat, Mar 20, 2021 at 07:02:43PM +0300, Dmitry Osipenko wrote:
> 02.03.2021 13:21, Dmitry Osipenko пишет:
> > Some Atmel maXTouch controllers, like mXT1386 and mXT3432S1 for example,
> > have a WAKE line that needs to be asserted in order to wake controller
> > from a deep sleep, othe
02.03.2021 13:21, Dmitry Osipenko пишет:
> Some Atmel maXTouch controllers, like mXT1386 and mXT3432S1 for example,
> have a WAKE line that needs to be asserted in order to wake controller
> from a deep sleep, otherwise it will be unusable. This series implements
> support for the wakeup methods in
The following series of patches
- Add support for GPIO subsystem in main and wakeup domains.
- Add voltage regulator device tree nodes and their corresponding pinmux
to support power cycle and voltage switch required for UHS-I modes
- sets respective tags in sdhci0 node to support higher speeds
-
On a typical end product, a vendor may choose to secure some regions in
the NAND memory which are supposed to stay intact between FW upgrades.
The access to those regions will be blocked by a secure element like
Trustzone. So the normal world software like Linux kernel should not
touch these region
The existed pGp shows the names of page flags only, rather than the full
information including section, node, zone, last cpuipid and kasan tag.
While it is not easy to parse these information manually because there
are so many flavors. We'd better interpret them in printf.
To be compitable with th
On Fri, Mar 05, 2021 at 08:01:29AM +0100, Álvaro Fernández Rojas wrote:
> Some devices may need to perform a reset before using the RNG, such as the
> BCM6368.
>
> v6: fix dt-bindings documentation, add patch makings clocks mandatory for
> BCM6368.
> v5: remove reset_control_rearm() and apply on
Some devices may need to perform a reset before using the RNG, such as the
BCM6368.
v6: fix dt-bindings documentation, add patch makings clocks mandatory for
BCM6368.
v5: remove reset_control_rearm() and apply on latest herbert/cryptodev-2.6.git.
v4: fix documentation, add reset_control_rearm().
Some Atmel maXTouch controllers, like mXT1386 and mXT3432S1 for example,
have a WAKE line that needs to be asserted in order to wake controller
from a deep sleep, otherwise it will be unusable. This series implements
support for the wakeup methods in accordance to the mXT1386 datasheet [1],
see pag
This series provides the Microchip Sparx5 Switch Reset Driver
The Sparx5 Switch SoC has a number of components that can be reset
individually, but at least the Switch Core needs to be in a well defined
state at power on, when any of the Sparx5 drivers starts to access the
Switch Core, this reset d
On Wed, 24 Feb 2021, Rik van Riel wrote:
> On Wed, 2021-02-24 at 00:41 -0800, Hugh Dickins wrote:
> > On Mon, 14 Dec 2020, Vlastimil Babka wrote:
> >
> > > > (There's also a specific issue with the gfp_mask limiting: I have
> > > > not yet reviewed the allowing and denying in detail, but it looks
On Wed, 2021-02-24 at 00:41 -0800, Hugh Dickins wrote:
> On Mon, 14 Dec 2020, Vlastimil Babka wrote:
>
> > > (There's also a specific issue with the gfp_mask limiting: I have
> > > not yet reviewed the allowing and denying in detail, but it looks
> > > like it does not respect the caller's GFP_ZON
On Mon, 14 Dec 2020, Vlastimil Babka wrote:
> On 12/14/20 10:16 PM, Hugh Dickins wrote:
> > On Tue, 24 Nov 2020, Rik van Riel wrote:
> >
> >> The allocation flags of anonymous transparent huge pages can be controlled
> >> through the files in /sys/kernel/mm/transparent_hugepage/defrag, which can
>
* Drew Fustini [210216 22:46]:
> This series first converts the debugfs files in the pinctrl subsystem to
> octal permissions and then adds a new debugfs file "pinmux-select".
>
> Function name and group name can be written to "pinmux-select" which
> will cause the function and group to be activa
This series first converts the debugfs files in the pinctrl subsystem to
octal permissions and then adds a new debugfs file "pinmux-select".
Function name and group name can be written to "pinmux-select" which
will cause the function and group to be activated on the pin controller.
The final patc
This patch series supports A64FX PMU event v1.2.
The first patch add more common and microarchitecture events.
This patch is based on john's patch [1].
The second patch fixes the lexical definition of event name so that
perf can recognize event name that start with a number.
The third patch adds
This is a different approach to [1] where I tried to add this proximity
sensor logic to the input subsystem. Instead, we'll take the approach of
making a small IIO proximity driver that parses the EC switch bitmap to
find out if the front proximity sensor is detecting something or not.
This allows
Hi all,
This set adds support for %p4cc printk modifier for printing V4L2 and DRM
fourcc codes. The codes are cumbersome to print manually and by adding the
modifier, this task is saved from the V4L2 and DRM frameworks as well as
related drivers. DRM actually had it handled in a way (see 3rd patch
On 04-02-21, 16:14, Hsin-Yi Wang wrote:
> Saravana Kannan (3):
> OPP: Add function to look up required OPP's for a given OPP
> PM / devfreq: Cache OPP table reference in devfreq
> PM / devfreq: Add required OPPs support to passive governor
I have applied all the patches with significant modi
The devfreq passive governor scales the frequency of a "child" device based
on the current frequency of a "parent" device (not parent/child in the
sense of device hierarchy). As of today, the passive governor requires one
of the following to work correctly:
1. The parent and child device have the s
[REQUEST]
Thanks Rob for reviewing the dt patches.
Would it be possible for the maintainers and reviewers to review the code as
well?
[COVER LETTER]
Add support to enable VBUS detection in the pm8941 extcon driver.
Changes from v5:
- Gathered Rob H's Acked-by for the dt-bindings patch.
Chang
On 1/14/21 6:50 AM, Kyle Tso wrote:
> v5 https://lore.kernel.org/r/20210105163927.1376770-1-kyle...@google.com
>
> "usb: typec: tcpm: AMS and Collision Avoidance"
> - removed the signed-off
> - modified the coding style suggested from Heikki
> - added FR_SWAP AMS handling
>
> "usb: typec: tcpm
On Wed, Jan 20, 2021 at 06:17:35PM +0100, Greg KH wrote:
> On Wed, Jan 20, 2021 at 02:45:02PM +0100, Hans de Goede wrote:
> > Hi,
> >
> > On 1/14/21 3:50 PM, Kyle Tso wrote:
> > > v5 https://lore.kernel.org/r/20210105163927.1376770-1-kyle...@google.com
> > >
> > > "usb: typec: tcpm: AMS and Colli
Hi,
On 1/14/21 3:50 PM, Kyle Tso wrote:
> v5 https://lore.kernel.org/r/20210105163927.1376770-1-kyle...@google.com
>
> "usb: typec: tcpm: AMS and Collision Avoidance"
> - removed the signed-off
> - modified the coding style suggested from Heikki
> - added FR_SWAP AMS handling
>
> "usb: typec:
On Wed, Jan 20, 2021 at 02:45:02PM +0100, Hans de Goede wrote:
> Hi,
>
> On 1/14/21 3:50 PM, Kyle Tso wrote:
> > v5 https://lore.kernel.org/r/20210105163927.1376770-1-kyle...@google.com
> >
> > "usb: typec: tcpm: AMS and Collision Avoidance"
> > - removed the signed-off
> > - modified the codin
Hi All,
On 1/14/21 3:50 PM, Kyle Tso wrote:
> v5 https://lore.kernel.org/r/20210105163927.1376770-1-kyle...@google.com
>
> "usb: typec: tcpm: AMS and Collision Avoidance"
> - removed the signed-off
> - modified the coding style suggested from Heikki
> - added FR_SWAP AMS handling
>
> "usb: ty
v5 https://lore.kernel.org/r/20210105163927.1376770-1-kyle...@google.com
"usb: typec: tcpm: AMS and Collision Avoidance"
- removed the signed-off
- modified the coding style suggested from Heikki
- added FR_SWAP AMS handling
"usb: typec: tcpm: Protocol Error handling"
- removed the signed-off
On 12/14/20 10:16 PM, Hugh Dickins wrote:
> On Tue, 24 Nov 2020, Rik van Riel wrote:
>
>> The allocation flags of anonymous transparent huge pages can be controlled
>> through the files in /sys/kernel/mm/transparent_hugepage/defrag, which can
>> help the system from getting bogged down in the page
On Mon, 14 Dec 2020 13:16:39 -0800 (PST) Hugh Dickins wrote:
> Andrew, please don't rush
>
> mmthpshmem-limit-shmem-thp-alloc-gfp_mask.patch
> mmthpshm-limit-gfp-mask-to-no-more-than-specified.patch
> mmthpshmem-make-khugepaged-obey-tmpfs-mount-flags.patch
>
> to Linus in your first wave of mmo
On Tue, 24 Nov 2020, Rik van Riel wrote:
> The allocation flags of anonymous transparent huge pages can be controlled
> through the files in /sys/kernel/mm/transparent_hugepage/defrag, which can
> help the system from getting bogged down in the page reclaim and compaction
> code when many THPs are
On Tue, 8 Dec 2020 17:43:59 +0530, Manivannan Sadhasivam wrote:
> This series adds PCIe support for Qualcomm SM8250 SoC with relevant PHYs.
> There are 3 PCIe instances on this SoC each with different PHYs. The PCIe
> controller and PHYs are mostly comaptible with the ones found on SDM845
> SoC, he
Hello,
This series adds PCIe support for Qualcomm SM8250 SoC with relevant PHYs.
There are 3 PCIe instances on this SoC each with different PHYs. The PCIe
controller and PHYs are mostly comaptible with the ones found on SDM845
SoC, hence the old drivers are modified to add the support.
This serie
From: Nick Terrell
Please pull from
g...@github.com:terrelln/linux.git tags/zstd-1.4.6-v6
to get these changes. Alternatively the patchset is included.
This patchset upgrades the zstd library to the latest upstream release. The
current zstd version in the kernel is a modified version of upst
To make it possible to optimize cross-socket memory accessing with
AutoNUMA even if the memory of the application is bound to multiple
NUMA nodes.
Patch [2/3] and [3/3] are NOT kernel patches. Instead, they are
patches for man-pages and numactl respectively. They are sent
together to make it eas
On Wed, 25 Nov 2020 at 17:45, Jakub Kicinski wrote:
> On Wed, 25 Nov 2020 17:24:52 +0100 Marco Elver wrote:
> > This patch series enables remote KCOV coverage collection during 802.11
> > frames processing. These changes make it possible to perform
> > coverage-guided fuzzing in search of remotely
On Wed, 25 Nov 2020 17:24:52 +0100 Marco Elver wrote:
> This patch series enables remote KCOV coverage collection during 802.11
> frames processing. These changes make it possible to perform
> coverage-guided fuzzing in search of remotely triggerable bugs.
Hi Marco, this stuff is only present in n
Marco Elver wrote:
[..]
> v6:
> * Revert usage of skb extensions due to potential memory leak. Patch 2/3 is
> now
> idential to that in v2.
> * Patches 1/3 and 3/3 are otherwise identical to v5.
The earlier series was already applied to net-next, so you need to
rebase on top of net-next and i
From: Aleksandr Nogikh
This patch series enables remote KCOV coverage collection during 802.11
frames processing. These changes make it possible to perform
coverage-guided fuzzing in search of remotely triggerable bugs.
Normally, KCOV collects coverage information for the code that is
executed i
The allocation flags of anonymous transparent huge pages can be controlled
through the files in /sys/kernel/mm/transparent_hugepage/defrag, which can
help the system from getting bogged down in the page reclaim and compaction
code when many THPs are getting allocated simultaneously.
However, the g
[REQUEST]
Thanks Rob for reviewing the dt patches.
Would it be possible for the maintainers and reviewers to review the code as
well?
[COVER LETTER]
Add support to enable VBUS detection in the pm8941 extcon driver.
Changes from v5:
- Gathered Rob H's Acked-by for the dt-bindings patch.
Chang
This series adds support for Qcom GSI dma controller found on Qualcomm SoCs.
This controller can program the peripheral configuration so we add
additional parameters in dma_slave_config for configuring the peripherals
like spi and i2c.
Changes in v6:
- Fix error reported by dt tool
Changes in v5
Roja Rani Yarubandi (3):
soc: qcom: geni: Remove "iova" check
i2c: i2c-qcom-geni: Store DMA mapping data in geni_i2c_dev struct
i2c: i2c-qcom-geni: Add shutdown callback for i2c
drivers/i2c/busses/i2c-qcom-geni.c | 104 -
drivers/soc/qcom/qcom-geni-se.c| 4
From: AngeloGioacchino Del Regno
This patch series adds support for the Novatek NT36xxx Series' In-Cell
touchscreen (integrated into the DriverIC).
This patch series has been tested against the following devices:
- Sony Xperia 10(SDM630 Ganges Kirin)
- Sony Xperia 10 Plus (SDM636 Gan
Hi Wolfram,
On Saturday, 10 October 2020, 13:06:58 CEST, Wolfram Sang wrote:
> > Changes in v5:
> Changes in v6 were missing... Because patch 1 was updated, I reverted it
> from for-current and will apply this series to for-next instead to give
> it some more time for testing.
can may patches be
The series add support for the serial GPIO controller used by
Microchip Sparx5, as well as (MSCC) ocelot/jaguar2 SoCs.
v6 changes:
- Use "bus-frequency" instead of "microchip,sgpio-frequency". Drop
'$ref'. (Robh)
- Added "ngpios" description, bumped minimum to 32. (Linus)
- Added "#size-cells" d
The series add support for the serial GPIO controller used by
Microchip Sparx5, as well as (MSCC) ocelot/jaguar2 SoCs.
v6 changes:
- Use "bus-frequency" instead of "microchip,sgpio-frequency". Drop
'$ref'. (Robh)
- Added "ngpios" description, bumped minimum to 32. (Linus)
- Added "#size-cells"
From: Sanjay R Mehta
This patch series adds support for AMD PTDMA controller which
performs high bandwidth memory-to-memory and IO copy operation,
performs DMA transfer through queue based descriptor management.
AMD Processor has multiple ptdma device instances with each controller
having single
> Changes in v5:
Changes in v6 were missing... Because patch 1 was updated, I reverted it
from for-current and will apply this series to for-next instead to give
it some more time for testing.
signature.asc
Description: PGP signature
On Thu, 1 Oct 2020 16:54:05 +0800
Gene Chen wrote:
> This patch series add MT6360 ADC support contains driver, testing document
> and binding document
>
> Gene Chen (2)
> dt-bindings: iio: adc: add bindings doc for MT6360 ADC
> Documentation: ABI: testing: mt6360: Add ADC sysfs guideline
>
Changes in v5:
---
- Added missing "Tested-By" tags.
Changes in v4:
---
- Extend comment (W1C vs. W0C)
Changes in v3:
---
- dedicated function for clearing an irq
Changes in v2:
---
- Don't accidently clear additional status flags on Vybrid
(report
Changes in v6:
---
- Fixed commit (W1C vs. W0C)
- Extended patch 1/3 for atomic case
- Added acks by Oleksij Rempel
Changes in v5:
---
- Added missing "Tested-By" tags.
Changes in v4:
---
- Extend comment (W1C vs. W0C)
Changes in v3:
---
- dedicate
This series is to add PCI support in tegra-smmu driver.
Changelog (Detail in each patch)
v5->v6
* Dropped a NULL check, per Dmitry's comments
* Added Dmitry's Reviewed-by and Tested-by
v4->v5
* PATCH-1 Cleaned two variables inits
* PATCH-2 Fixed put() in ->of_xlate() and Updated commit message
This patch series add MT6360 ADC support contains driver, testing document
and binding document
Gene Chen (2)
dt-bindings: iio: adc: add bindings doc for MT6360 ADC
Documentation: ABI: testing: mt6360: Add ADC sysfs guideline
iio: adc: mt6360: Add ADC driver for MT6360
Documentation/ABI/te
On 9/29/20 4:33 PM, Bjorn Andersson wrote:
> On Tue 29 Sep 03:44 CDT 2020, Arnaud POULIQUEN wrote:
>
>>
>>
>> On 9/29/20 12:17 AM, Rishabh Bhatnagar wrote:
>>> From Android R onwards Google has restricted access to debugfs in user
>>> and user-debug builds. This restricts access to most of the
On Tue 29 Sep 03:44 CDT 2020, Arnaud POULIQUEN wrote:
>
>
> On 9/29/20 12:17 AM, Rishabh Bhatnagar wrote:
> > From Android R onwards Google has restricted access to debugfs in user
> > and user-debug builds. This restricts access to most of the features
> > exposed through debugfs. 'Coredump' an
On 9/29/20 12:17 AM, Rishabh Bhatnagar wrote:
> From Android R onwards Google has restricted access to debugfs in user
> and user-debug builds. This restricts access to most of the features
> exposed through debugfs. 'Coredump' and 'Recovery' are critical
> interfaces that are required for remot
>From Android R onwards Google has restricted access to debugfs in user
and user-debug builds. This restricts access to most of the features
exposed through debugfs. 'Coredump' and 'Recovery' are critical
interfaces that are required for remoteproc to work on Qualcomm Chipsets.
Coredump configurat
On 9/24/2020 4:27 PM, Amelie DELAUNAY wrote:
> Gentle reminder on the whole series instead.
>
> Thanks,
> Amelie
>
> On 9/9/20 11:35 AM, Amelie DELAUNAY wrote:
>> When using usb-c connector (but it can also be the case with a micro-b
>> connector), iddig, avalid, bvalid, vbusvalid input signals may
Gentle reminder on the whole series instead.
Thanks,
Amelie
On 9/9/20 11:35 AM, Amelie DELAUNAY wrote:
When using usb-c connector (but it can also be the case with a micro-b
connector), iddig, avalid, bvalid, vbusvalid input signals may not be
connected to the DWC2 OTG controller.
DWC2 OTG cont
[Cc'ing Nayna Jain, linuxppc-...@lists.ozlabs.org]
Hi Lakshmi,
On Tue, 2020-09-08 at 16:08 -0700, Lakshmi Ramasubramanian wrote:
> On kexec file load Integrity Measurement Architecture(IMA) subsystem
> may verify the IMA signature of the kernel and initramfs, and measure
> it. The command line pa
This patch series includes
- Fix for proper Y_OUT_SIZE register configuration.
- Remove sensor i2c register writes to stop stream during remove.
- Power on/off sequence implementation through runtime PM.
Delta between patch versions:
[v6]: Includes below v5 feedback
- Added separate smal
> You're going to have to update every single SWITCHDEV_PORT_ADD_OBJ
> handler and subsequent helpers to check the validate the protocol value.
>
> You also are going to have to make sure that every instantiated
> switchdev_obj_port_vlan object initializes the vlan protocol field properly.
>
> Ba
On 9/18/2020 5:20 PM, David Miller wrote:
From: hongbo.w...@nxp.com
Date: Wed, 16 Sep 2020 17:48:42 +0800
1. Overview
a) 0001* is for support to set dsa slave into 802.1AD(QinQ) mode.
b) 0002* is for vlan_proto support for br_switchdev_port_vlan_add and
br_switchdev_port_vlan_del.
c) 0003*
From: hongbo.w...@nxp.com
Date: Wed, 16 Sep 2020 17:48:42 +0800
> 1. Overview
> a) 0001* is for support to set dsa slave into 802.1AD(QinQ) mode.
> b) 0002* is for vlan_proto support for br_switchdev_port_vlan_add and
> br_switchdev_port_vlan_del.
> c) 0003* is for setting QinQ related registers
This patch set adds and modify device tree nodes in the NPCM7xx
Baseboard Management Controller (BMC) device tree.
The following device node add:
- NPCM7xx Pin controller and GPIO
- NPCM7xx PWM and FAN.
- NPCM7xx EHCI USB.
- NPCM7xx KCS.
- NPCM Reset.
Hi All,
This patch series adds support for BT.656 mode in the ov772x sensor
and also enables color bar test pattern control.
Cheers,
Prabhakar
v5->v6
* Introduced new function ov772x_parse_dt()
* Moved the backward compatibility comment from 1/3 to 2/3
v4->v5:
* Put the ep instance back using f
From: "hongbo.wang"
1. Overview
a) 0001* is for support to set dsa slave into 802.1AD(QinQ) mode.
b) 0002* is for vlan_proto support for br_switchdev_port_vlan_add and
br_switchdev_port_vlan_del.
c) 0003* is for setting QinQ related registers in ocelot switch driver, after
applying this patch,
On Mon, 7 Sep 2020 18:46:54 +0100, Cristian Marussi wrote:
> this series wants to add the core SCMI System Power support and related
> events' handling logic: the protocol support itself is trivial and boils
> down to some bare initializations and supporting one SCMI System Power
> notification eve
When using usb-c connector (but it can also be the case with a micro-b
connector), iddig, avalid, bvalid, vbusvalid input signals may not be
connected to the DWC2 OTG controller.
DWC2 OTG controller features an overriding control of the PHY voltage valid
and ID input signals.
So, missing signals ca
On kexec file load Integrity Measurement Architecture(IMA) subsystem
may verify the IMA signature of the kernel and initramfs, and measure
it. The command line parameters passed to the kernel in the kexec call
may also be measured by IMA. A remote attestation service can verify
the measurement thro
This patch series adds support for the external interrupt controller
(SIRQ) found in the Actions Semi Owl family of SoC's (S500, S700 and
S900). The controller handles up to 3 external interrupt lines through
dedicated SIRQ pins.
This is a rework of the patch series submitted some time ago by
Par
Hi all,
this series wants to add the core SCMI System Power support and related
events' handling logic: the protocol support itself is trivial and boils
down to some bare initializations and supporting one SCMI System Power
notification event meant to carry platform-originated System transition
re
Version v4 of these patches was sent by Colin Cross a long time ago [1]
and [2]. At the time, these patches were not merged, and it looks like they
just fell off the radar since.
In our efforts to run Android on mainline kernels, we realised that since past
some time, this patchset is needed for A
This is the V5 version of a series that introduces the writeback support
to VKMS. The first two patches of this series are a pre-work for the
latest patch that adds the writeback connector, this patchset can be seen
in two parts:
* A pre-work that aims to make vkms composer operations a little bit
On 8/27/20 8:58 AM, Stefano Garzarella wrote:
> v6:
> - moved restriction checks in a function [Jens]
> - changed ret value handling in io_register_restrictions() [Jens]
>
> v5:
> https://lore.kernel.org/io-uring/20200827134044.82821-1-sgarz...@redhat.com/
> v4:
> https://lore.kernel.org/io-ur
v6:
- moved restriction checks in a function [Jens]
- changed ret value handling in io_register_restrictions() [Jens]
v5: https://lore.kernel.org/io-uring/20200827134044.82821-1-sgarz...@redhat.com/
v4: https://lore.kernel.org/io-uring/20200813153254.93731-1-sgarz...@redhat.com/
v3: https://lore
On Thu, Aug 20, 2020 at 11:36 AM James Morris wrote:
>
> On Fri, 7 Aug 2020, Lokesh Gidra wrote:
>
> > Userfaultfd in unprivileged contexts could be potentially very
> > useful. We'd like to harden userfaultfd to make such unprivileged use
> > less risky. This patch series allows SELinux to manage
On Fri, 7 Aug 2020, Lokesh Gidra wrote:
> Userfaultfd in unprivileged contexts could be potentially very
> useful. We'd like to harden userfaultfd to make such unprivileged use
> less risky. This patch series allows SELinux to manage userfaultfd
> file descriptors and in the future, other kinds of
1 - 100 of 609 matches
Mail list logo
