On Tue, Sep 16, 2025 at 10:35:46PM -0700, Namhyung Kim wrote:
> Hello,
>
> On Tue, Sep 16, 2025 at 10:13:12PM -0700, Ian Rogers wrote:
> > On Tue, Sep 16, 2025 at 6:47 PM Jinchao Wang
> > wrote:
> > >
> > > On Tue, Sep 16, 2025 at 05:03:48PM -0700, Ian Rogers wrote:
> > > > On Tue, Sep 16, 2025
On Wed, Sep 17, 2025 at 08:08:57AM +0200, Christophe Leroy wrote:
>
>
> Le 16/09/2025 à 16:50, Jinchao Wang a écrit :
> > Currently, the hard lockup detector is selected at compile time via
> > Kconfig, which requires a kernel rebuild to switch implementations.
> > This is inflexible, especially
On Fri, Sep 19, 2025 at 6:25 PM Nicolas Schichan wrote:
> Considering that the deprecation message didn't get displayed in some
> configurations, maybe it's a bit early at the very least.
I changed my opinion.
Breaking users, who did not see a deprecation message at all,
is unfair.
I will send a
Hi Dan,
On Fri, Sep 19, 2025 at 02:17:41PM +0300, Dan Carpenter wrote:
> Hi the Clang nightly builds are failing on PowerPC with the
> ppc64e_defconfig. They started failing on Sept 11. Clang is failing on
> PowerPC in both linux-next and stable so it seems like something changed
> in Clang and
On Fri, 19 Sep 2025 15:51:14 -0500 (CDT)
Timothy Pearson wrote:
> - Original Message -
> > From: "Alex Williamson"
> > To: "Timothy Pearson"
> > Cc: "kvm" , "linuxppc-dev"
> >
> > Sent: Friday, September 19, 2025 1:56:03 PM
> > Subject: Re: [PATCH] vfio/pci: Fix INTx handling on legac
Hello,
> > When booting with root=/dev/ram0 in the kernel commandline,
> > handle_initrd() where the deprecation message resides is never called,
> > which is rather unfortunate (init/do_mounts_initrd.c):
> Yes, this is unfortunate.
>
> I personally still think that initrd should be removed.
Con
On Thu, 18 Sep 2025 17:34:07 +0200, Christophe Leroy wrote:
> This is a RESEND of v3 sent one month ago, see:
> https://lore.kernel.org/all/cover.1754993232.git.christophe.le...@csgroup.eu/
>
> This series reduces significantly the amount of interrupts on
> fsl_qmc_audio device.
>
> Patches 1 and
- Original Message -
> From: "Alex Williamson"
> To: "Timothy Pearson"
> Cc: "kvm" , "linuxppc-dev"
>
> Sent: Friday, September 19, 2025 1:56:03 PM
> Subject: Re: [PATCH] vfio/pci: Fix INTx handling on legacy DisINTx- PCI
> devices
> On Tue, 9 Sep 2025 15:48:46 -0500 (CDT)
> Timoth
On Tue, 9 Sep 2025 15:48:46 -0500 (CDT)
Timothy Pearson wrote:
> PCI devices prior to PCI 2.3 both use level interrupts and do not support
> interrupt masking, leading to a failure when passed through to a KVM guest on
> at least the ppc64 platform, which does not utilize the resample IRQFD. This
On Mon, 1 Sep 2025, Simon Schuster via B4 Relay wrote:
> From: Simon Schuster
>
> With the introduction of clone3 in commit 7f192e3cd316 ("fork: add
> clone3") the effective bit width of clone_flags on all architectures was
> increased from 32-bit to 64-bit, with a new type of u64 for the flags.
The QUICC Engine provides interrupts for a few I/O ports. This is
handled via a separate interrupt ID and managed via a triplet of
dedicated registers hosted by the SoC.
Implement an interrupt driver for it for that those IRQs can then
be linked to the related GPIOs.
The number of ports for which
Remove legacy-of-mm-gpiochip.h header file. The above mentioned
file provides an OF API that's deprecated. There is no agnostic
alternatives to it and we have to open code the logic which was
hidden behind of_mm_gpiochip_add_data(). Note, most of the GPIO
drivers are using their own labeling schema
On 9/17/25 13:00, Andy Lutomirski wrote:
On Mon, Sep 15, 2025 at 10:09 AM Rob Landley wrote:
While you're at it, could you fix static/builtin initramfs so PID 1 has
a valid stdin/stdout/stderr?
A static initramfs won't create /dev/console if the embedded initramfs
image doesn't contain it, wh
From: Alexander Sverdlin
... otherwise it could be problematic to build external modules:
make[2]: Entering directory '.../kernel-module-hello-world'
| CC [M] hello-world.o
| MODPOST Module.symvers
| CC [M] hello-world.mod.o
| CC [M] .module-common.o
| LD [M] hello-world.ko
| power
On Fri, Sep 12, 2025 at 12:03:27PM +0300, Leon Romanovsky wrote:
> On Fri, Sep 12, 2025 at 12:25:38AM +0200, Marek Szyprowski wrote:
> > >
> > > This series does the core code and modern flows. A followup series
> > > will give the same treatment to the legacy dma_ops implementation.
> >
> > Appli
On Thu, Sep 18, 2025 at 06:23:27PM +0200, Christophe Leroy wrote:
> In the QE, a few GPIOs have an associated IRQ to notify changes.
> Add IRQ support to QE GPIO.
>
> As not all GPIOs have an associated IRQ, the driver needs to know
> to which GPIO corresponds each provided IRQ. This is provided v
On Thu, Sep 18, 2025 at 06:23:26PM +0200, Christophe Leroy wrote:
> Convert QE QPIO devicetree binding to DT schema.
Why is this in linux-next when it still needs review? Anything in
linux-next already gets removed from my review queue (patchwork), so
you're lucky I'm looking at it. It's also no
On 18/09/2025 at 15:12, Arnd Bergmann wrote:
* Microchip SAM9x7 is the newest ARMv5 chip, clearly does
get kernel updates, and the only one I can think of with
DDR3 support, but seems to be limited to 256MB total memory.
It is indeed.
No difficulty on this part of the product line ;-)
Be
This is a RESEND of v3 sent one month ago, see:
https://lore.kernel.org/all/cover.1754993232.git.christophe.le...@csgroup.eu/
This series reduces significantly the amount of interrupts on
fsl_qmc_audio device.
Patches 1 and 2 are preparatory patches.
Patch 3 is the main change
Patch 4 is a cleanu
From: Rohan McLure
This reverts commit aa232204c468 ("mm/page_table_check: remove unused
parameter in [__]page_table_check_pte_clear").
Reinstate previously unused parameters for the purpose of supporting
powerpc platforms, as many do not encode user/kernel ownership of the
page in the pte, but
On Wed, Sep 10, 2025, at 03:46, Matthew Wilcox wrote:
> On Tue, Sep 09, 2025 at 11:23:37PM +0200, Arnd Bergmann wrote:
>> While removing a feature that is actively used is clearly a regression
>> and not normally done, I expect removing highmem is going to happen
>> at some point anyway when there
Well, while on x86 1GB systems did use highmem, they'd typically not
use very much of it.
IOW, they'd have about 900MB as lowmem (ok, I think it was 896MB to
be exact), with something like 120MB highmem.
So they'd either lose a bit of memory, or they'd use the 2G:2G
split.
Right, 1G-128M of VMA
On Tue, Sep 16, 2025 at 12:10:14PM +1000, Ash Logan wrote:
> On 15/9/25 00:14, Segher Boessenkool wrote:
> > On Sat, Sep 13, 2025 at 08:53:08PM +1000, Ash Logan wrote:
> > > Wii (2006)
> > > - 1x PowerPC 750CL "Broadway" @ 729MHz
> > > - 24MB "MEM1" + 64MB "MEM2" (non-contiguous - MEM2 starts 256Mi
On Thu, 18 Sept 2025 at 13:49, Adrian Barnaś wrote:
> Because driver core can properly handle constant struct bus_type,
> move the ps3_system_bus_type to be a constant structure as well,
> placing it into read-only memory which can not be modified at runtime.
>
> Signed-off-by: Adrian Barnaś
Rev
prtd_tx and prtd_rx members are not used anymore and only qmc_chan
member remains so struct qmc_dai_chan has become pointless.
Use qmc_chan directly and drop struct qmc_dai_chan.
Acked-by: Herve Codina
Signed-off-by: Christophe Leroy
---
sound/soc/fsl/fsl_qmc_audio.c | 52 ++---
To reduce complexity of interrupt handling in following patch, ensure
audio channels are configured in the same order as timeslots on the
TDM bus. If we need a given ordering of audio sources in the audio
frame, it is possible to re-order codecs on the TDM bus, no need to
mix up timeslots in channe
Hi Arnd,
On Thu, 18 Sept 2025 at 15:13, Arnd Bergmann wrote:
> On Wed, Sep 17, 2025, at 14:59, Jason Gunthorpe wrote:
> > On Tue, Sep 09, 2025 at 11:23:37PM +0200, Arnd Bergmann wrote:
> >
> >> I'm still collecting information about which of the remaining highmem
> >> users plan to keep updating
27 matches
Mail list logo
