Let imx-audio-rpmsg register platform device for card. So that card
register and unregister can be controlled by rpmsg driver's register
and unregister.
Signed-off-by: Chancel Liu
---
sound/soc/fsl/fsl_rpmsg.c | 11 ---
sound/soc/fsl/imx-audio-rpmsg.c | 18 +-
2
This rpmsg driver registers device for ASoC platform driver. To align
with platform driver use rpmsg channel name to create device.
Signed-off-by: Chancel Liu
---
sound/soc/fsl/imx-audio-rpmsg.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Machine driver uses rpmsg channel name to link this platform component.
However if the component is re-registerd card will not find this new
created component in snd_soc_try_rebind_card().
Explicitly register this component with rpmsg channel name so that
card can always find this component.
Platform device for card to probe is registered in imx-audio-rpmsg.
According to this change DT node of ASoC CPU DAI device is updated.
Signed-off-by: Chancel Liu
---
sound/soc/fsl/imx-rpmsg.c | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git
echo /lib/firmware/fw.elf > /sys/class/remoteproc/remoteproc0/firmware
(A) echo start > /sys/class/remoteproc/remoteproc0/state
(B) echo stop > /sys/class/remoteproc/remoteproc0/state
The rpmsg sound card is registered in (A) and unregistered in (B).
After "start", imx-audio-rpmsg
On Tue, Mar 05, 2024 at 12:37:50PM +0800, pet...@redhat.com wrote:
> From: Peter Xu
>
> Even if pXd_leaf() API is defined globally, it's not clear on the retval,
> and there are three types used (bool, int, unsigned log).
>
> Always return a boolean for pXd_leaf() APIs.
>
> Suggested-by: Jason
On Tue, Mar 05, 2024 at 12:37:49PM +0800, pet...@redhat.com wrote:
> From: Peter Xu
>
> They're not used anymore, drop all of them.
>
> Reviewed-by: Jason Gunthorpe
> Signed-off-by: Peter Xu
Reviewed-by: Mike Rapoport (IBM)
> ---
> arch/arm/include/asm/pgtable-2level.h| 1 -
>
On Tue, Mar 05, 2024 at 12:37:47PM +0800, pet...@redhat.com wrote:
> From: Peter Xu
>
> pmd_large() is always defined as pmd_leaf(). Merge their usages. Chose
> pmd_leaf() because pmd_leaf() is a global API, while pmd_large() is not.
>
> Reviewed-by: Jason Gunthorpe
> Signed-off-by: Peter Xu
On Tue, Mar 05, 2024 at 12:37:46PM +0800, pet...@redhat.com wrote:
> From: Peter Xu
>
> There is an old trick in shadow_mapped() to use pXd_bad() to detect huge
> pages. After commit 93fab1b22ef7 ("mm: add generic p?d_leaf() macros") we
> have a global API for huge mappings. Use that to
On Tue, Mar 05, 2024 at 12:37:45PM +0800, pet...@redhat.com wrote:
> From: Peter Xu
>
> pud_leaf() has a fallback macro defined in include/linux/pgtable.h already.
> Drop the extra two for x86.
>
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: Borislav Petkov
> Cc: Dave Hansen
> Cc:
On Tue, Mar 05, 2024 at 12:37:44PM +0800, pet...@redhat.com wrote:
> From: Peter Xu
>
> pgd_leaf() is a global API while pgd_large() is not. Always use
> the global pgd_leaf(), then drop pgd_large().
>
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: Borislav Petkov
> Cc: Dave Hansen
> Cc:
On Tue, Mar 05, 2024 at 12:37:43PM +0800, pet...@redhat.com wrote:
> From: Peter Xu
>
> p4d_large() is always defined as p4d_leaf(). Merge their usages. Chose
> p4d_leaf() because p4d_leaf() is a global API, while p4d_large() is not.
>
> Only x86 has p4d_leaf() defined as of now. So it also
On Tue, Mar 05, 2024 at 12:37:42PM +0800, pet...@redhat.com wrote:
> From: Peter Xu
>
> They're the same macros underneath. Drop pXd_is_leaf(), instead always use
> pXd_leaf().
>
> At the meantime, instead of renames, drop the pXd_is_leaf() fallback
> definitions directly in
On Tue, Mar 05, 2024 at 12:37:41PM +0800, pet...@redhat.com wrote:
> From: Peter Xu
>
> The two definitions are the same. The only difference is that pXd_large()
> is only defined with THP selected, and only on book3s 64bits.
>
> Instead of implementing it twice, make pXd_large() a macro to
Kees Cook writes:
> On Tue, 05 Mar 2024 23:56:44 +1100, Michael Ellerman wrote:
>> This test is userspace code, but uses some kernel headers via symlinks,
>> and mocks other headers, in order to test load_unaligned_zeropad().
>>
>> Currently the test fails to build with:
>>
>> In file
John Paul Adrian Glaubitz writes:
> On Fri, 2024-03-01 at 12:56 +1100, Michael Ellerman wrote:
>> That second iso boots OK for me in qemu. It boots grub and then the
>> kernel loads and shows:
>>
>> Loading ...
>> OF stdout device is: /pci@f000/mac-io@c/escc@13000/ch-a@13020
>>
Nathan Chancellor writes:
> Ping? We have been applying this in our CI since it was sent, it would
> be nice to have this upstream soon so it can start filtering through the
> stable trees.
Sorry, I was away in January and missed this. Will pick it up.
cheers
> On Sat, Jan 27, 2024 at
Ping? We have been applying this in our CI since it was sent, it would
be nice to have this upstream soon so it can start filtering through the
stable trees.
On Sat, Jan 27, 2024 at 11:07:43AM -0700, Nathan Chancellor wrote:
> arch/powerpc/lib/xor_vmx.o is built with '-msoft-float' (from the main
Le 05/03/2024 à 19:14, Sean Anderson a écrit :
> [Vous ne recevez pas souvent de courriers de sean.ander...@linux.dev.
> Découvrez pourquoi ceci est important à
> https://aka.ms/LearnAboutSenderIdentification ]
>
> Hi,
>
> On 2/23/24 11:02, Sean Anderson wrote:
>> On 2/23/24 00:38,
90d35da658da8cff0d4ecbb5113f5fac9d00eb72
change-id: 20240305-macintosh-9b027d413a05
Best regards,
--
Ricardo B. Marliere
-Wflex-array-member-not-at-end is coming in GCC-14, and we are getting
ready to enable it globally. So, we are deprecating flexible-array
members in the middle of another structure.
There is currently an object (`header`) in `struct nx842_crypto_ctx`
that contains a flexible structure (`struct
On Tue, 05 Mar 2024 23:56:44 +1100, Michael Ellerman wrote:
> This test is userspace code, but uses some kernel headers via symlinks,
> and mocks other headers, in order to test load_unaligned_zeropad().
>
> Currently the test fails to build with:
>
> In file included from
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 11afac187274a6177a7ac82997f8691c0f469e41 Add linux-next specific
files for 20240305
Error/Warning reports:
https://lore.kernel.org/oe-kbuild-all/202403051732.lucjfzah-...@intel.com
https
Hi,
On 2/23/24 11:02, Sean Anderson wrote:
> On 2/23/24 00:38, Christophe Leroy wrote:
>> Le 22/02/2024 à 18:07, Sean Anderson a écrit :
>>> [Vous ne recevez pas souvent de courriers de sean.ander...@linux.dev.
>>> Découvrez pourquoi ceci est important à
>>>
On 3/5/24 13:02, Rob Herring wrote:
>
> On Thu, 01 Feb 2024 13:29:30 -0600, Rob Herring wrote:
>> There is no reason to use RESERVEDMEM_OF_DECLARE() as the initialization
>> hook just saves off the base address and size. Use of
>> RESERVEDMEM_OF_DECLARE() is reserved for non-driver code and
>>
On Thu, 01 Feb 2024 13:29:30 -0600, Rob Herring wrote:
> There is no reason to use RESERVEDMEM_OF_DECLARE() as the initialization
> hook just saves off the base address and size. Use of
> RESERVEDMEM_OF_DECLARE() is reserved for non-driver code and
> initialization which must be done early. For
Le 05/03/2024 à 05:37, pet...@redhat.com a écrit :
> From: Peter Xu
>
> They're the same macros underneath. Drop pXd_is_leaf(), instead always use
> pXd_leaf().
>
> At the meantime, instead of renames, drop the pXd_is_leaf() fallback
> definitions directly in
Le 05/03/2024 à 05:37, pet...@redhat.com a écrit :
> From: Peter Xu
>
> The two definitions are the same. The only difference is that pXd_large()
> is only defined with THP selected, and only on book3s 64bits.
>
> Instead of implementing it twice, make pXd_large() a macro to pXd_leaf().
>
Calculating the offset of an address is image specific, which is
architecture specific. Until now, all architectures and architecture
configurations which select CONFIG_RELOC were able to subtract
_etext, but the EFI configuration of riscv cannot (it must subtract
ImageBase). Make this function
We should never pass the result of __builtin_frame_address(0) to
another function since the compiler is within its rights to pop the
frame to which it points before making the function call, as may be
done for tail calls. Nobody has complained about backtrace(), so
likely all compilations have
On Tue, Mar 05 2024 at 18:57, Bitao Hu wrote:
> On 2024/3/4 22:24, Thomas Gleixner wrote:
> "GENERIC_IRQ_STAT_SNAPSHOT" visible to the user. However, after
> analyzing the previous emails, it seems that what you were actually
> proposing was to directly disable "GENERIC_IRQ_STAT_SNAPSHOT" when
>
Hello,
this series converts all drivers below drivers/char/ipmi to struct
platform_driver::remove_new(). See commit 5c5a7680e67b ("platform: Provide a
remove callback that returns no value") for an extended explanation and the
eventual goal.
All conversations are trivial, because their .remove()
The .remove() callback for a platform driver returns an int which makes
many driver authors wrongly assume it's possible to do error handling by
returning an error code. However the value returned is ignored (apart
from emitting a warning) and this typically results in resource leaks.
To improve
On Tue, Mar 05, 2024 at 12:37:44PM +0800, pet...@redhat.com wrote:
> From: Peter Xu
>
> pgd_leaf() is a global API while pgd_large() is not. Always use
> the global pgd_leaf(), then drop pgd_large().
>
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: Borislav Petkov
> Cc: Dave Hansen
> Cc:
Recent additions in BPF like cpu v4 instructions, test_bpf module
exhibits the following failures:
test_bpf: #82 ALU_MOVSX | BPF_B jited:1 ret 2 != 1 (0x2 != 0x1)FAIL (1
times)
test_bpf: #83 ALU_MOVSX | BPF_H jited:1 ret 2 != 1 (0x2 != 0x1)FAIL (1
times)
test_bpf: #84
On Tue, Mar 05, 2024 at 12:02:26PM +0100, Herve Codina wrote:
> On Thu, 29 Feb 2024 17:23:32 +0200
> Andy Shevchenko wrote:
...
> > I think it's a good series and next version will be final. The only
> > question is
> > possible use of the returned values from bitmap_scatter()/bitmap_gather(),
On Tue, 2024-03-05 at 11:51 +1100, Michael Ellerman wrote:
> I gave it a quick boot test, all good.
>
> Acked-by: Michael Ellerman (powerpc)
Thanks! Christophe was advocating for slight spin on this (not doing
the member initializing in the declaration, but dropping the
assignments that set 0):
On Tue, Mar 05, 2024 at 12:37:50PM +0800, pet...@redhat.com wrote:
> From: Peter Xu
>
> Even if pXd_leaf() API is defined globally, it's not clear on the retval,
> and there are three types used (bool, int, unsigned log).
>
> Always return a boolean for pXd_leaf() APIs.
>
> Suggested-by: Jason
This test is userspace code, but uses some kernel headers via symlinks,
and mocks other headers, in order to test load_unaligned_zeropad().
Currently the test fails to build with:
In file included from load_unaligned_zeropad.c:26:
word-at-a-time.h:7:10: fatal error: linux/bitops.h: No such
The 44x/warp_defconfig build fails with:
arch/powerpc/platforms/44x/warp.c:109:15: error: variable ‘warp_gpio_leds’
has initializer but incomplete type
109 | static struct platform_device warp_gpio_leds = {
| ^~~
Fix it by including platform_device.h.
Move the prototypes into mpc10x.h which is included by all the relevant
C files, fixes:
arch/powerpc/platforms/embedded6xx/ls_uart.c:59:6: error: no previous
prototype for 'avr_uart_configure'
arch/powerpc/platforms/embedded6xx/ls_uart.c:82:6: error: no previous
prototype for
These functions can all be static. Make them so. That also fixes no
previous prototype warnings:
arch/powerpc/platforms/amigaone/setup.c:28:6: error: no previous prototype
for 'amigaone_show_cpuinfo'
arch/powerpc/platforms/amigaone/setup.c:68:13: error: no previous prototype
for
On Tue, Mar 05, 2024 at 07:26:18AM +0100, Thomas Huth wrote:
> On 05/03/2024 03.19, Nicholas Piggin wrote:
> > On Fri Mar 1, 2024 at 10:41 PM AEST, Thomas Huth wrote:
> > > On 26/02/2024 11.12, Nicholas Piggin wrote:
> > > > Add basic testing of various kinds of interrupts, machine check,
> > > >
On Mon, 2024-02-26 at 17:14 +0100, Arnd Bergmann wrote:
>
> arch/um/Kconfig| 1 +
> arch/um/include/asm/page.h | 2 +-
LGTM, thanks.
Acked-by: Johannes Berg
johannes
Hi Andy,
On Thu, 29 Feb 2024 17:23:32 +0200
Andy Shevchenko wrote:
...
>
> I think it's a good series and next version will be final. The only question
> is
> possible use of the returned values from bitmap_scatter()/bitmap_gather(), the
> rest are minors.
I replied about the reason why I
Hi,
On 2024/3/4 22:24, Thomas Gleixner wrote:
The above is not even configurable by the user. It's only selectable by
some other config option.
+# Snapshot for interrupt statistics
+config GENERIC_IRQ_STAT_SNAPSHOT
+ bool
+ help
+
+ Say Y here to enable the kernel to
Le 05/03/2024 à 11:04, Thomas Zimmermann a écrit :
> Hi
>
> Am 05.03.24 um 10:25 schrieb Christophe Leroy:
>>
>> Le 05/03/2024 à 10:01, Thomas Zimmermann a écrit :
>>> Replace with a forward declaration in to
>>> resolves an unnecessary dependency. Remove pmac_backlight_curve_lookup()
>>> and
Hi
Am 05.03.24 um 10:25 schrieb Christophe Leroy:
Le 05/03/2024 à 10:01, Thomas Zimmermann a écrit :
Replace with a forward declaration in to
resolves an unnecessary dependency. Remove pmac_backlight_curve_lookup()
and struct fb_info from source and header files. The function and the
Le 05/03/2024 à 10:01, Thomas Zimmermann a écrit :
> Replace with a forward declaration in to
> resolves an unnecessary dependency. Remove pmac_backlight_curve_lookup()
> and struct fb_info from source and header files. The function and the
> framebuffer struct is unused. No functional
On Tue, 05 Mar 2024, Thomas Zimmermann wrote:
> Replace with a forward declaration in to
> resolves an unnecessary dependency. Remove pmac_backlight_curve_lookup()
*resolve
> and struct fb_info from source and header files. The function and the
> framebuffer struct is unused. No functional
On Tue, 05 Mar 2024, Thomas Zimmermann wrote:
> Fix builds with CONFIG_PMAC_BACKLIGHT=y. The include statement for the
> backlight header has recently been removed from . Add it to
> via-pmu-backlight.c to get the necessary symbols.
>
> Reported-by: Naresh Kamboju
> Closes:
>
Fix builds with CONFIG_PMAC_BACKLIGHT=y. The include statement for the
backlight header has recently been removed from . Add it to
via-pmu-backlight.c to get the necessary symbols.
Reported-by: Naresh Kamboju
Closes:
Replace with a forward declaration in to
resolves an unnecessary dependency. Remove pmac_backlight_curve_lookup()
and struct fb_info from source and header files. The function and the
framebuffer struct is unused. No functional changes.
Signed-off-by: Thomas Zimmermann
---
Fix builds with CONFIG_PMAC_BACKLIGHT=y. The include statement for
the backlight header has recently been removed from .
Reported-by: Naresh Kamboju
Closes:
https://lore.kernel.org/dri-devel/ca+g9fysak5tbqqxfc2w4ohlga0cbthmxbeq8qayfxtu75yi...@mail.gmail.com/
Signed-off-by: Thomas Zimmermann
After cleaning up in commit 11b4eedfc87d ("fbdev: Do
not include in header"), building with
CONFIG_PMAC_BACKLIGHT=y returns errors about missing declarations.
Patches 1 and 2 resolve the errors. Patch 1 has been reviewed at [1].
Patch 3 removes another dependency between backlight and fbdev
On Tue, 05 Mar 2024, Michael Ellerman wrote:
> I prefer Thomas' patch, but I'm fine with either to go in via drm.
Thanks!
--
Jani Nikula, Intel
Hi
Am 05.03.24 um 01:36 schrieb Michael Ellerman:
Christophe Leroy writes:
Le 04/03/2024 à 11:32, Thomas Zimmermann a écrit :
Hi
Am 04.03.24 um 10:55 schrieb Jani Nikula:
Removal of the backlight include from fb.h uncovered an implicit
dependency in powerpc asm/backlight.h. Add the
57 matches
Mail list logo
