On Tue, 24 Oct 2023 20:11:57 +
"Alessandro Carminati (Red Hat)" wrote:
> In the kernel environment, scenarios often arise where identical names
> are shared among symbols within core image or modules.
> While this poses no complications for the kernel's binary itself, it
> creates challenges
The MHP_MEMMAP_ON_MEMORY flag for hotplugged memory is restricted to
'memblock_size' chunks of memory being added. Adding a larger span of
memory precludes memmap_on_memory semantics.
For users of hotplug such as kmem, large amounts of memory might get
added from the CXL subsystem. In some cases,
Large amounts of memory managed by the kmem driver may come in via CXL,
and it is often desirable to have the memmap for this memory on the new
memory itself.
Enroll kmem-managed memory for memmap_on_memory semantics if the dax
region originates via CXL. For non-CXL dax regions, retain the
A review of the memmap_on_memory modifications to add_memory_resource()
revealed an instance of an open-coded kmemdup(). Replace it with
kmemdup().
Cc: Andrew Morton
Cc: David Hildenbrand
Cc: Michal Hocko
Cc: Oscar Salvador
Cc: Dan Williams
Reported-by: Dan Williams
Reviewed-by: David
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
Hi Francis,
Thanks a lot for your feedback!
Il giorno mer 25 ott 2023 alle ore 15:21 Francis Laniel
ha scritto:
>
> Hi!
>
>
> Le mardi 24 octobre 2023, 23:11:57 EEST Alessandro Carminati (Red Hat) a
> écrit :
> > In the kernel environment, scenarios often arise where identical names
> > are
The pull request you sent on Wed, 25 Oct 2023 19:51:04 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git acpi-6.6-rc8
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/611da07b89fdd53f140d7b33013f255bf0ed8f34
Thank you!
--
Deet-doot-dot, I am
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
acpi-6.6-rc8
with top-most commit 9b311b7313d6c104dd4a2d43ab54536dce07f960
ACPI: NFIT: Install Notify() handler before getting NFIT table
on top of commit
On Wed, 25 Oct 2023 19:26:37 +0800
"wuqiang.matt" wrote:
> On 2023/10/24 22:52, Masami Hiramatsu (Google) wrote:
> > From: Masami Hiramatsu (Google)
> >
> > Use generic_cmpxchg_local() for arch_cmpxchg_local() implementation
> > in SH architecture because it does not implement
From: Masami Hiramatsu (Google)
Use __generic_cmpxchg_local() for arch_cmpxchg_local() implementation
in SH architecture because it does not implement arch_cmpxchg_local().
Reported-by: kernel test robot
Closes:
https://lore.kernel.org/oe-kbuild-all/202310241310.ir5uukog-...@intel.com/
On Wed, 25 Oct 2023 15:16:16 +0200
Geert Uytterhoeven wrote:
> Hi Adrian,
>
> On Wed, Oct 25, 2023 at 12:32 PM John Paul Adrian Glaubitz
> wrote:
> > On Wed, 2023-10-25 at 11:30 +0100, Mark Rutland wrote:
> > > On Wed, Oct 25, 2023 at 08:42:55AM +0900, Masami Hiramatsu wrote:
> > > > On Tue,
Hi!
Le mardi 24 octobre 2023, 23:11:57 EEST Alessandro Carminati (Red Hat) a
écrit :
> In the kernel environment, scenarios often arise where identical names
> are shared among symbols within core image or modules.
> While this poses no complications for the kernel's binary itself, it
> creates
Hi Adrian,
On Wed, Oct 25, 2023 at 12:32 PM John Paul Adrian Glaubitz
wrote:
> On Wed, 2023-10-25 at 11:30 +0100, Mark Rutland wrote:
> > On Wed, Oct 25, 2023 at 08:42:55AM +0900, Masami Hiramatsu wrote:
> > > On Tue, 24 Oct 2023 16:08:12 +0100
> > > Mark Rutland wrote:
> > > > On Tue, Oct 24,
On 2023/10/24 22:52, Masami Hiramatsu (Google) wrote:
From: Masami Hiramatsu (Google)
Use generic_cmpxchg_local() for arch_cmpxchg_local() implementation
in SH architecture because it does not implement arch_cmpxchg_local().
Reported-by: kernel test robot
Closes:
On 2023/10/25 09:51, wuqiang.matt wrote:
On 2023/10/25 07:42, Masami Hiramatsu (Google) wrote:
On Tue, 24 Oct 2023 16:08:12 +0100
Mark Rutland wrote:
On Tue, Oct 24, 2023 at 11:52:54PM +0900, Masami Hiramatsu (Google) wrote:
From: Masami Hiramatsu (Google)
Use generic_cmpxchg_local() for
On Wed, 2023-10-25 at 11:30 +0100, Mark Rutland wrote:
> On Wed, Oct 25, 2023 at 08:42:55AM +0900, Masami Hiramatsu wrote:
> > On Tue, 24 Oct 2023 16:08:12 +0100
> > Mark Rutland wrote:
> >
> > > On Tue, Oct 24, 2023 at 11:52:54PM +0900, Masami Hiramatsu (Google) wrote:
> > > > From: Masami
On Wed, Oct 25, 2023 at 08:42:55AM +0900, Masami Hiramatsu wrote:
> On Tue, 24 Oct 2023 16:08:12 +0100
> Mark Rutland wrote:
>
> > On Tue, Oct 24, 2023 at 11:52:54PM +0900, Masami Hiramatsu (Google) wrote:
> > > From: Masami Hiramatsu (Google)
> > >
> > > Use generic_cmpxchg_local() for
On Wed, Oct 25, 2023 at 09:47:36AM +0100, Alexandru Elisei wrote:
> Hi,
>
> On Wed, Oct 25, 2023 at 11:59:32AM +0900, Hyesoo Yu wrote:
> > On Wed, Sep 13, 2023 at 04:29:25PM +0100, Catalin Marinas wrote:
> > > On Mon, Sep 11, 2023 at 02:29:03PM +0200, David Hildenbrand wrote:
> > > > On 11.09.23
On 25/10/2023 10:52, Stefan Hansson wrote:
>
>
> On 2023-10-25 10:48, Krzysztof Kozlowski wrote:
>> On 25/10/2023 10:37, Stefan Hansson wrote:
>>> This series adds a common samsung-matisse dtsi and reworks
>>> samsung-matisse-wifi to use it, and introduces samsung-matisselte. I
>>> choose
On 2023-10-25 10:48, Krzysztof Kozlowski wrote:
On 25/10/2023 10:37, Stefan Hansson wrote:
This series adds a common samsung-matisse dtsi and reworks
samsung-matisse-wifi to use it, and introduces samsung-matisselte. I
choose matisselte over matisse-lte as this is how most other devices
On 25/10/2023 10:37, Stefan Hansson wrote:
> According to the dts from the kernel source code released by Samsung,
> matissewifi and matisselte only have minor differences in hardware, so
> use a shared dtsi to reduce duplicated code. Additionally, this should
> make adding support for matisse3g
On Wed, 25 Oct 2023 at 10:43, Neil Armstrong wrote:
>
> Add DSP Peripheral Authentication Service support for the SM8650 platform.
>
> Signed-off-by: Neil Armstrong
> ---
> drivers/remoteproc/qcom_q6v5_pas.c | 50
> ++
> 1 file changed, 50 insertions(+)
On 2023-10-25 10:48, Krzysztof Kozlowski wrote:
On 25/10/2023 10:37, Stefan Hansson wrote:
This documents Samsung Galaxy Tab 4 10.1 LTE (samsung,matisselte)
which is a tablet by Samsung based on the MSM8926 SoC.
Signed-off-by: Stefan Hansson
---
This is a friendly reminder during the
On 25/10/2023 10:37, Stefan Hansson wrote:
> This documents Samsung Galaxy Tab 4 10.1 LTE (samsung,matisselte)
> which is a tablet by Samsung based on the MSM8926 SoC.
>
> Signed-off-by: Stefan Hansson
> ---
This is a friendly reminder during the review process.
It looks like you received a
On 25/10/2023 10:37, Stefan Hansson wrote:
> This series adds a common samsung-matisse dtsi and reworks
> samsung-matisse-wifi to use it, and introduces samsung-matisselte. I
> choose matisselte over matisse-lte as this is how most other devices
> (klte, s3ve3g) do it and it is the codename that
Hi,
On Wed, Oct 25, 2023 at 11:59:32AM +0900, Hyesoo Yu wrote:
> On Wed, Sep 13, 2023 at 04:29:25PM +0100, Catalin Marinas wrote:
> > On Mon, Sep 11, 2023 at 02:29:03PM +0200, David Hildenbrand wrote:
> > > On 11.09.23 13:52, Catalin Marinas wrote:
> > > > On Wed, Sep 06, 2023 at 12:23:21PM
This was not enabled in the matisse-wifi tree. Without this, it is not
possible to use the USB port for serial debugging via a "Carkit debug
cable".
Signed-off-by: Stefan Hansson
---
.../boot/dts/qcom/qcom-msm8226-samsung-matisse-common.dtsi| 4
1 file changed, 4 insertions(+)
diff
According to the dts from the kernel source code released by Samsung,
matissewifi and matisselte only have minor differences in hardware, so
use a shared dtsi to reduce duplicated code. Additionally, this should
make adding support for matisse3g easier should someone want to do that
at a later
Add a device tree for the Samsung Galaxy Tab 4 10.1 (SM-T535) LTE tablet
based on the MSM8926 platform.
Signed-off-by: Stefan Hansson
---
arch/arm/boot/dts/qcom/Makefile | 1 +
.../qcom/qcom-msm8926-samsung-matisselte.dts | 36 +++
2 files changed, 37
This documents Samsung Galaxy Tab 4 10.1 LTE (samsung,matisselte)
which is a tablet by Samsung based on the MSM8926 SoC.
Signed-off-by: Stefan Hansson
---
Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
This series adds a common samsung-matisse dtsi and reworks
samsung-matisse-wifi to use it, and introduces samsung-matisselte. I
choose matisselte over matisse-lte as this is how most other devices
(klte, s3ve3g) do it and it is the codename that Samsung gave the
device. See individual commits for
On 10/24/2023 10:40 PM, Steven Rostedt wrote:
From: "Steven Rostedt (Google)"
It's eventfs_inode not eventfs_indoe. There's no deer involved!
:-)
Fixes: 5790b1fb3d672 ("eventfs: Remove eventfs_file and just use eventfs_inode")
Signed-off-by: Steven Rostedt (Google)
Reviewed-by:
The current memory region assign only supports a single
memory region.
But new platforms introduces more regions to make the
memory requirements more flexible for various use cases.
Those new platforms also shares the memory region between the
DSP and HLOS.
To handle this, make the region assign
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
Document the DSP Peripheral Authentication Service on the SM8650 Platform.
Signed-off-by: Neil Armstrong
---
.../bindings/remoteproc/qcom,sm8550-pas.yaml | 41 +-
1 file changed, 40 insertions(+), 1 deletion(-)
diff --git
Add DSP Peripheral Authentication Service support for the SM8650 platform.
Signed-off-by: Neil Armstrong
---
drivers/remoteproc/qcom_q6v5_pas.c | 50 ++
1 file changed, 50 insertions(+)
diff --git a/drivers/remoteproc/qcom_q6v5_pas.c
On 24/10/2023 22:33, Stefan Hansson wrote:
> This was not enabled in the matisse-wifi tree.
Your commit msg should explain why this should be enabled.
>
> Signed-off-by: Stefan Hansson
> ---
> .../boot/dts/qcom/qcom-msm8226-samsung-matisse-common.dtsi| 4
> 1 file changed, 4
On 24/10/2023 22:33, Stefan Hansson wrote:
> This documents Samsung Galaxy Tab 4 10.1 LTE (samsung,matisselte)
> which is a tablet by Samsung based on the MSM8926 SoC.
>
> Signed-off-by: Stefan Hansson
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
Reviewed-by: Krzysztof
On 24/10/2023 22:33, Stefan Hansson wrote:
> According to the dts from the kernel source code released by Samsung,
> matissewifi and matisselte only have minor differences in hardware, so
> use a shared dtsi to reduce duplicated code. Additionally, this should
> make adding support for matisse3g
39 matches
Mail list logo
