Refer to audio graph card, add playback-only and capture-only property
for imx-audio-card.yaml for the case that only playback or capture is
supported.
Signed-off-by: Shengjiu Wang
Reviewed-by: Daniel Baluta
Reviewed-by: Iuliana Prodan
---
.../devicetree/bindings/sound/imx-audio-card.yaml | 1
Be similar to audio graph card, support playback or capture only for
imx-audio-card.
imx-card can't directly refer to audio-graph-port.yaml, because it is
not based on 'ports'. Add playback-only and capture-only property
directly
changes in v3:
- add mutually exclusive expression
changes in v2:
The AER driver has historically avoided reading the configuration space of
an endpoint or RCiEP that reported a fatal error, considering the link to
that device unreliable. Consequently, when a fatal error occurs, the AER
and DPC drivers do not report specific error types, resulting in logs like:
dpc_handler() is registered for error port which recevie DPC interrupt
and acpi_dpc_port_get() locate the port that experienced the containment
event.
Rename edev and pdev to err_port for clear so that later patch will
avoid misused err_port in pcie_do_recovery().
No functional changes intended.
With the DPCM case, the backend only support capture or playback, then
the linked frontend can only support capture or playback, but frontend
can't automatically enable only capture or playback, it needs the input
from dt-binding.
Signed-off-by: Shengjiu Wang
Reviewed-by: Daniel Baluta
Reviewed-
The current implementation of pcie_do_recovery() assumes that the
recovery process is executed on the device that detected the error.
However, the DPC driver currently passes the error port that experienced
the DPC event to pcie_do_recovery().
Use the SOURCE ID register to correctly identify the d
changes since v3:
- squash patch 1 and 2 into one patch per Sathyanarayanan
- add comments note for dpc_process_error per Sathyanarayanan
- pick up Reviewed-by tag from Sathyanarayanan
changes since v2:
- moving the "err_port" rename to a separate patch per Sathyanarayanan
- rewrite comments of dp
Changes include:
- Replaced [[ ... ]] with [ ... ]
- Replaced == with =
- Replaced printf -v with cur=$(printf ...).
- Replaced echo -e with printf "%b\n" ...
The above mentioned are Bash/GNU extensions and are not part of POSIX.
Using shells like dash or non-GNU coreutils may produce errors.
They
On Sun, Feb 16, 2025 at 05:32:25PM +0530, Aditya Dutt wrote:
> Changes include:
> - Replaced [[ ... ]] with [ ... ]
> - Replaced == with =
> - Replaced printf -v with cur=$(printf ...).
> - Replaced echo -e with printf "%b\n" ...
>
> The above mentioned are Bash/GNU extensions and are not part of
vpa-pmu driver is used to collect latency metrics for host to guest
or guest to host context switches in a PowerVM KVM guest scenario.
This may not be used during the dump kernel, avoid loading it
Signed-off-by: Madhavan Srinivasan
---
arch/powerpc/perf/vpa-pmu.c | 5 +
1 file changed, 5 ins
hv-24x7 pmu driver is intended to get system-wide resourse
metrics and may not be used during the dump kernel, avoid
loading it
Signed-off-by: Madhavan Srinivasan
---
arch/powerpc/perf/hv-24x7.c | 3 +++
arch/powerpc/perf/hv-common.h | 2 ++
2 files changed, 5 insertions(+)
diff --git a/arch/
Platform pmu driver may not be used in the dump kernel.
Avoid loading it.
Signed-off-by: Madhavan Srinivasan
---
arch/powerpc/perf/core-book3s.c | 8
1 file changed, 8 insertions(+)
diff --git a/arch/powerpc/perf/core-book3s.c b/arch/powerpc/perf/core-book3s.c
index 2b79171ee185..9a009
hv-gpci pmu driver is intended to get powervm hypervisor
system-wide metrics and this may not be used during the
dump kernel, avoid loading it
Signed-off-by: Madhavan Srinivasan
---
arch/powerpc/perf/hv-gpci.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/powerpc/perf/hv-gpci.c b/a
Greetings!!!
I am observing kernel oops on IBM Power system while running LTP test
readahead02 on 6.14.0-rc2-next-20250214 kernel.
By Reverting the below patch, issue is not seen.
Revert "VFS: add common error checks to lookup_one_qstr_excl()"
This reverts commit 22d9d5e93d0eaf7e86
If stream names of DAI driver are duplicated there'll be warnings when
machine driver tries to add widgets on a route:
[8.831335] fsl-asoc-card sound-wm8960: ASoC: sink widget CPU-Playback
overwritten
[8.839917] fsl-asoc-card sound-wm8960: ASoC: source widget CPU-Capture
overwritten
Use
Thanks for the report. I've posted a revised version of that patch which
adds the missing error check on the result of ->lookup.
NeilBrown
On Mon, 17 Feb 2025, Venkat Rao Bagalkote wrote:
> Greetings!!!
>
>
> I am observing kernel oops on IBM Power system while running LTP test
> readahead0
From: Pei Xiao
sparse warning:
sparse: symbol 'ugeth_mac_ops' was not declared. Should it be
static.
Add static to fix sparse warnings and add const. phylink_create() will
accept a const struct.
Reported-by: kernel test robot
Closes:
https://lore.kernel.org/oe-kbuild-all/202502141128.9hfx
Amit Machhiwal writes:
> Currently on book3s-hv, the capability KVM_CAP_SPAPR_TCE_VFIO is only
> available for KVM Guests running on PowerNV and not for the KVM guests
> running on pSeries hypervisors. This prevents a pSeries L2 guest from
> leveraging the in-kernel acceleration for H_PUT_TCE_IND
The series reworks generic PTDUMP configs before eventually renaming them
after some basic clean ups first. This is derived after splitting changes
from the following patch.
https://lore.kernel.org/all/20250205050039.1506377-1-anshuman.khand...@arm.com/
This series applies on v6.14-rc3 and has be
Platforms subscribe into generic ptdump implementation via GENERIC_PTDUMP.
But generic ptdump gets enabled via PTDUMP_CORE. These configs combination
is confusing as they sound very similar and does not differentiate between
platform's feature subscription and feature enablement for ptdump. Rename
GENERIC_PTDUMP gets selected on powerpc explicitly and hence can be dropped
off from mpc885_ads_defconfig.
Cc: Madhavan Srinivasan
Cc: Michael Ellerman
Cc: Nicholas Piggin
Cc: Christophe Leroy
Cc: linuxppc-dev@lists.ozlabs.org
Cc: linux-ker...@vger.kernel.org
Signed-off-by: Anshuman Khandual
Both GENERIC_PTDUMP and PTDUMP_CORE are not user selectable config options.
Just drop these from documentation.
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Jonathan Corbet
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
Suggested-by: Steven Pr
DEBUG_WX selects PTDUMP_CORE without even ensuring that the given platform
implements GENERIC_PTDUMP. This problem has been latent until now, as all
the platforms subscribing ARCH_HAS_DEBUG_WX also subscribe GENERIC_PTDUMP.
Cc: Andrew Morton
Cc: linux...@kvack.org
Cc: linux-ker...@vger.kernel.org
The platforms that support GENERIC_PTDUMP select the config explicitly. But
enabling this feature on platforms that don't really support - does nothing
or might cause a build failure. Hence just drop GENERIC_PTDUMP from generic
debug.config
Cc: Andrew Morton
Cc: linux...@kvack.org
Cc: linux-ker..
On Sun, Feb 16, 2025 at 06:11:51AM -1000, Tejun Heo wrote:
> On Sun, Feb 16, 2025 at 05:32:25PM +0530, Aditya Dutt wrote:
> > Changes include:
> > - Replaced [[ ... ]] with [ ... ]
> > - Replaced == with =
> > - Replaced printf -v with cur=$(printf ...).
> > - Replaced echo -e with printf "%b\n" ..
On Mon, Feb 10, 2025 at 07:45:09PM +0100, David Hildenbrand wrote:
> On 04.02.25 23:48, Alistair Popple wrote:
> > Currently DAX folio/page reference counts are managed differently to normal
> > pages. To allow these to be managed the same as normal pages introduce
> > vmf_insert_folio_pmd. This wi
Hello,
Please review this patch and let me know if there are any issues with
the same.
Thanks,
Gautam
Restricted pointers ("%pK") are not meant to be used through printk().
It can unintentionally expose security sensitive, raw pointer values.
Use regular pointer formatting instead.
Link:
https://lore.kernel.org/lkml/20250113171731-dc10e3c1-da64-4af0-b767-7c7070468...@linutronix.de/
Signed-off-by
Hi Eddie,
On 11/02/25 9:50 pm, Eddie James wrote:
In non-smp configurations, crash_kexec_prepare is never called in
the crash shutdown path. One result of this is that the crashing_cpu
variable is never set, preventing crash_save_cpu from storing the
NT_PRSTATUS elf note in the core dump.
Tha
On Mon, 13 Jan 2025 11:40:37 -0500, adu...@linux.ibm.com wrote:
> Define macros and wrapper functions to handle
> H_HTM (Hardware Trace Macro) hypervisor call.
> H_HTM is new HCALL added to export data from
> Hardware Trace Macro (HTM) function.
>
>
Applied to powerpc/next.
[1/3] powerpc/pserie
On Mon, 13 Jan 2025 13:28:54 +0530, Athira Rajeev wrote:
> Add check for power11 pvr in the selftest utility
> functions. Selftests uses pvr value to check for platform
> support inorder to run the tests. pvr is also used to
> send the extended mask value to capture sampling registers.
>
> Update
On Tue, 21 Jan 2025 18:46:20 +0530, Athira Rajeev wrote:
> perf mem report aborts as below sometimes (during some corner
> case) in powerpc:
>
># ./perf mem report 1>out
>*** stack smashing detected ***: terminated
>Aborted (core dumped)
>
> [...]
Applied to powerpc/next.
[1/2] arch
On Thu, 30 Jan 2025 12:38:54 -0600, Gaurav Batra wrote:
> iommu_mem_notifier() is invoked when RAM is dynamically added/removed. This
> notifier call is responsible to add/remove TCEs from the Dynamic DMA Window
> (DDW) when TCEs are pre-mapped. TCEs are pre-mapped only for RAM and not
> for persis
On Wed, 08 Jan 2025 10:48:14 -0600, Gaurav Batra wrote:
> Starting with PAPR level 2.13, platform supports placing PHB in limited
> address mode. Devices that support DMA masks less that 64-bit but greater
> than 32-bits are placed in limited address mode. In this mode, the
> starting DMA address r
On Thu, 23 Jan 2025 17:12:50 +0530, Sourabh Jain wrote:
> Change RMA size from 512 MB to 768 MB which will result
> in more RMA at boot time for PowerPC. When PowerPC LPAR use/uses vTPM,
> Secure Boot or FADump, the 512 MB RMA memory is not sufficient for
> booting. With this 512 MB RMA, GRUB2 run
On Mon, Feb 10, 2025 at 06:01:57PM -0600, Rob Herring wrote:
> On Fri, Feb 07, 2025 at 10:30:28PM +0100, J. Neuschäfer wrote:
> > Formalize the binding already supported by the fsl_elbc_nand.c driver
> > and used in several device trees in arch/powerpc/boot/dts/.
> >
> > Signed-off-by: J. Neuschäf
I did attempt git bisect, and the first bad commit is
d49e636ed7014be354d1ee279b8f4957e8def389.
Git bisect log:
#git bisect log
#git bisect start
# status: waiting for both good and bad commits
# good: [a64dcfb451e254085a7daee5fe51bf22959d52d3] Linux 6.14-rc2
git bisect good a64dcfb451e254085a7
On Mon, Feb 10, 2025 at 03:53:24PM -0600, Rob Herring wrote:
> On Sun, Feb 09, 2025 at 02:31:34PM -0600, Crystal Wood wrote:
> > On Fri, Feb 07, 2025 at 10:30:26PM +0100, J. Neuschäfer via B4 Relay wrote:
> > > From: "J. Neuschäfer"
> > >
> > > Convert the Freescale localbus controller bindings f
On Mon, Feb 10, 2025 at 09:27:22AM +0100, Miquel Raynal wrote:
> Hello,
>
> On 07/02/2025 at 22:30:29 +01, J. Neuschäfer via B4 Relay
> wrote:
>
> > From: "J. Neuschäfer"
> >
> > In some scenarios, such as under the Freescale eLBC bus, there are raw
> > NAND chips with a unit address that has
39 matches
Mail list logo
