On 12/01/2024 06:43, Chancel Liu wrote:
> Add compatible string "fsl,imx95-micfil" for i.MX95 platform.
>
> Signed-off-by: Chancel Liu
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
On 12/01/2024 06:43, Chancel Liu wrote:
> Add compatible string "fsl,imx95-sai" for i.MX95 platform.
>
> Signed-off-by: Chancel Liu
> ---
Acked-by: Krzysztof Kozlowski
Best regards,
Krzysztof
kasprintf() returns a pointer to dynamically allocated memory
which can be NULL upon failure.
Uniformly handle resource release in error paths. And when an
error occurs, an error pointer should be returned.
Fixes: bdecf76e319a ("cxl: Fix coredump generation when cxl_get_fd() is used")
Add compatible string "fsl,imx95-micfil" for i.MX95 platform.
Signed-off-by: Chancel Liu
---
.../devicetree/bindings/sound/fsl,micfil.yaml | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/sound/fsl,micfil.yaml
Add compatible string and specific soc data to support SAI on i.MX95
platform.
Signed-off-by: Chancel Liu
---
sound/soc/fsl/fsl_sai.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/sound/soc/fsl/fsl_sai.c b/sound/soc/fsl/fsl_sai.c
index 546bd4e333b5..0e2c31439670 100644
---
Add compatible string "fsl,imx95-sai" for i.MX95 platform.
Signed-off-by: Chancel Liu
---
Documentation/devicetree/bindings/sound/fsl,sai.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/sound/fsl,sai.yaml
Support SAI and MICFIL on i.MX95 platform
changes in v2
- Remove unnecessary "item" in fsl,micfil.yaml
- Don't change alphabetical order in fsl,sai.yaml
Chancel Liu (3):
ASoC: dt-bindings: fsl,sai: Add compatible string for i.MX95 platform
ASoC: fsl_sai: Add support for i.MX95 platform
On Thu, Dec 28, 2023 at 4:49 PM Timothy Pearson
wrote:
>
> Hrmm, potentially related, I'm getting a kernel oops when I try to hot unplug
> the entire PCIe switch from the PHB4:
IIRC there's hard to fix races in the pci core around removal of pci
slot devices. Maybe someone fixed those since I
On Thu, Dec 28, 2023 at 3:16 PM Timothy Pearson
wrote:
>
> I've been evaluating some new options for our POWER9-based hardware in the
> NVMe space, and would like some clarification on the current status of PCIe
> hotplug for the PowerNV platforms.
>
> From what I understand, the pnv_php driver
of_node_put(root);
+ return 0;
+}
+machine_device_initcall(pseries, check_migratable_partition);
+
#endif /* CONFIG_PPC_SMLPAR */
#endif /* CONFIG_PPC_BOOK3S_64 */
---
base-commit: 44a1aad2fe6c10bfe0589d8047057b10a4c18a19
change-id: 20240111-h_page_set_unused-for-lpm-d9027c672fe8
Best regards,
--
Nathan Lynch
On Wed, Jan 10, 2024 at 4:46 PM Kees Cook wrote:
>
> On Tue, Jan 09, 2024 at 03:16:28PM -0700, Nathan Chancellor wrote:
> > This series updates all instances of LLVM Phabricator and Bugzilla links
> > to point to GitHub commits directly and LLVM's Bugzilla to GitHub issue
> > shortlinks
7
> > > > -__ https://reviews.llvm.org/D109073
> > > > +__
> > > > https://github.com/llvm/llvm-project/commit/ea72b0319d7b0f0c2fcf41d121afa5d031b319d
> > >
> > > To be consistent with other links, could you add the missing last alnum
> > > '5'
On Thu, Jan 11, 2024 at 11:40 AM Nathan Chancellor wrote:
>
> Hi Yonghong,
>
> On Wed, Jan 10, 2024 at 08:05:36PM -0800, Yonghong Song wrote:
> >
> > On 1/9/24 2:16 PM, Nathan Chancellor wrote:
> > > reviews.llvm.org was LLVM's Phabricator instances for code review. It
> > > has been abandoned in
Hi Yonghong,
On Wed, Jan 10, 2024 at 08:05:36PM -0800, Yonghong Song wrote:
>
> On 1/9/24 2:16 PM, Nathan Chancellor wrote:
> > reviews.llvm.org was LLVM's Phabricator instances for code review. It
> > has been abandoned in favor of GitHub pull requests. While the majority
> > of links in the
Haren Myneni writes:
> VAS allocate, modify and deallocate HCALLs returns
> H_LONG_BUSY_ORDER_1_MSEC or H_LONG_BUSY_ORDER_10_MSEC for busy
> delay and expects OS to reissue HCALL after that delay. But using
> msleep() will often sleep at least 20 msecs even though the
> hypervisor suggests OS
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt :
On Fri, 24 Nov 2023 12:39:00 +0530 you wrote:
> The SBI v2.0 specification is now frozen. The SBI v2.0 specification defines
> SBI debug console (DBCN) extension which replaces the legacy SBI v0.1
> functions
The patch titled ("powerpc: make fadump resilient with memory add/remove
events") has made significant changes to the implementation of fadump,
particularly on elfcorehdr creation and fadump crash info header
structure. Therefore, updating the fadump implementation documentation
to reflect those
The elfcorehdr describes the CPUs and memory of the crashed kernel to
the kernel that captures the dump, known as the second or fadump kernel.
The elfcorehdr needs to be updated if the system's memory changes due to
memory hotplug or online/offline events.
Currently, memory hotplug events are
Due to changes in memory resources caused by either memory hotplug or
online/offline events, the elfcorehdr, which describes the CPUs and
memory of the crashed kernel to the kernel that collects the dump (known
as second/fadump kernel), becomes outdated. Consequently, attempting
dump collection
Problem:
Due to changes in memory resources caused by either memory hotplug or
online/offline events, the elfcorehdr, which describes the cpus and
memory of the crashed kernel to the kernel that collects the dump (known
as second/fadump kernel), becomes outdated. Consequently, attempting
On 11/01/2024 12:06, Chancel Liu wrote:
>>> Add compatible string "fsl,imx95-sai" for i.MX95 platform.
>>>
>>> Signed-off-by: Chancel Liu
>>> ---
>>> Documentation/devicetree/bindings/sound/fsl,sai.yaml | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git
> > Add compatible string "fsl,imx95-sai" for i.MX95 platform.
> >
> > Signed-off-by: Chancel Liu
> > ---
> > Documentation/devicetree/bindings/sound/fsl,sai.yaml | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/Documentation/devicetree/bindings/sound/fsl,sai.yaml
>
In the event of memory hotplug or online/offline events, the crash
memory hotplug notifier `crash_memhp_notifier()` receives a
`memory_notify` object but doesn't forward that object to the
generic and architecture-specific crash hotplug handler.
The `memory_notify` object contains the starting
Commit 247262756121 ("crash: add generic infrastructure for crash
hotplug support") added a generic infrastructure that allows
architectures to selectively update the kdump image component during CPU
or memory add/remove events within the kernel itself.
This patch series adds crash hotplug
Extend the arch crash hotplug handler, as introduced by the patch title
("powerpc: add crash CPU hotplug support"), to also support memory
add/remove events.
Elfcorehdr describes the memory of the crash kernel to capture the
kernel; hence, it needs to be updated if memory resources change due to
Move the functions update_cpus_node and get_crash_memory_ranges from
kexec/file_load_64.c to kexec/core_64.c to make these functions usable
by other kexec components.
get_crash_memory_ranges uses functions defined in ranges.c, so take
ranges.c out of CONFIG_KEXEC_FILE.
Later in the series, these
Due to CPU/Memory hotplug or online/offline events, the elfcorehdr
(which describes the CPUs and memory of the crashed kernel) and FDT
(Flattened Device Tree) of kdump image becomes outdated. Consequently,
attempting dump collection with an outdated elfcorehdr or FDT can lead
to failed or
Commit a72bbec70da2 ("crash: hotplug support for kexec_load()")
introduced a new kexec flag, `KEXEC_UPDATE_ELFCOREHDR`. Kexec tool uses
this flag to indicate to the kernel that it is safe to modify the
elfcorehdr of the kdump image loaded using the kexec_load system call.
However, it is possible
On 09/01/2024 08:55, Chancel Liu wrote:
> Add compatible string "fsl,imx95-sai" for i.MX95 platform.
>
> Signed-off-by: Chancel Liu
> ---
> Documentation/devicetree/bindings/sound/fsl,sai.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
29 matches
Mail list logo
