mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Santhosh Kumar K <s-k6@ti.com>
To: <catalin.marinas@arm.com>, <will@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <krzk@kernel.org>,
	<vigneshr@ti.com>, <p-mantena@ti.com>, <s-k6@ti.com>
Subject: Re: [PATCH v2] arm64: defconfig: Enable SPI NAND flashes
Date: Thu, 30 Jan 2025 11:53:58 +0530	[thread overview]
Message-ID: <c00ae17b-b006-4b28-86e8-e82d1067e7d3@ti.com> (raw)
In-Reply-To: <20250116035145.370734-1-s-k6@ti.com>

Hi, all,

On 16/01/25 09:21, Santhosh Kumar K wrote:
> Add support for SPI NAND flashes on ARM64 boards/EVMs such as:
> 
> 1. W35N01JW on AM62x LP SK, AM62A7 SK, J721S2 EVM, J784S4 EVM,
>     J722S EVM, J742S2 EVM
> 2. W25N01JW on AM62Lx EVM
> 
> by enabling the MTD_SPI_NAND config as a module.
> 
> Signed-off-by: Santhosh Kumar K <s-k6@ti.com>
> ---

Gentle ping.

Regards,
Santhosh.

> 
> Changes in v2:
>   - Fix commit message
>   - Rebase on next
>   - Link to v1: https://lore.kernel.org/linux-arm-kernel/20250102120043.1404843-1-s-k6@ti.com/
>   
> Repo: https://github.com/santhosh21/linux/tree/uL_next
> Test results: https://gist.github.com/santhosh21/71ab6646dccc238a0b3c47c0382f219a
> 
> ---
>   arch/arm64/configs/defconfig | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index e729948b7d69..35f312a39e38 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -283,6 +283,7 @@ CONFIG_MTD_NAND_BRCMNAND=m
>   CONFIG_MTD_NAND_FSL_IFC=y
>   CONFIG_MTD_NAND_QCOM=y
>   CONFIG_MTD_SPI_NOR=y
> +CONFIG_MTD_SPI_NAND=m
>   CONFIG_MTD_UBI=m
>   CONFIG_MTD_HYPERBUS=m
>   CONFIG_HBMC_AM654=m

  reply	other threads:[~2025-01-30  6:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16  3:51 Santhosh Kumar K
2025-01-30  6:23 ` Santhosh Kumar K [this message]
2025-01-30  6:28   ` Vignesh Raghavendra
2025-01-30 11:37   ` Catalin Marinas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c00ae17b-b006-4b28-86e8-e82d1067e7d3@ti.com \
    --to=s-k6@ti.com \
    --cc=catalin.marinas@arm.com \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p-mantena@ti.com \
    --cc=vigneshr@ti.com \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®