mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: ziniu.wang_1@nxp.com
Cc: pratyush@kernel.org,  tudor.ambarus@linaro.org,
	 mwalle@kernel.org, miquel.raynal@bootlin.com,  richard@nod.at,
	 vigneshr@ti.com, linux-mtd@lists.infradead.org,
	 linux-kernel@vger.kernel.org, haibo.chen@nxp.com,
	 han.xu@nxp.com
Subject: Re: [PATCH v3 1/2] mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode
Date: Mon, 01 Sep 2025 16:19:49 +0200	[thread overview]
Message-ID: <mafs0tt1mw8ze.fsf@kernel.org> (raw)
In-Reply-To: <20250708091646.292-1-ziniu.wang_1@nxp.com>

Hi,

On Tue, Jul 08 2025, ziniu.wang_1@nxp.com wrote:

> From: Pratyush Yadav <p.yadav@ti.com>
>
> On Octal DTR capable flashes like Micron Xcella reads cannot start or
> end at an odd address in Octal DTR mode. Extra bytes need to be read at
> the start or end to make sure both the start address and length remain
> even.
>
> To avoid allocating too much extra memory, thereby putting unnecessary
> memory pressure on the system, the temporary buffer containing the extra
> padding bytes is capped at PAGE_SIZE bytes. The rest of the 2-byte
> aligned part should be read directly in the main buffer.
>
> Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
> Reviewed-by: Michael Walle <michael@walle.cc>
> Signed-off-by: Luke Wang <ziniu.wang_1@nxp.com>

Series applied to spi-nor/next. Thanks!

[...]

-- 
Regards,
Pratyush Yadav

      parent reply	other threads:[~2025-09-01 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08  9:16 ziniu.wang_1
2025-07-08  9:16 ` [PATCH v3 2/2] mtd: spi-nor: core: avoid odd length/address writes in " ziniu.wang_1
2025-08-13  2:49   ` Luke Wang
2025-08-13 12:46     ` Pratyush Yadav
2025-09-01 14:19 ` Pratyush Yadav [this message]

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=mafs0tt1mw8ze.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=haibo.chen@nxp.com \
    --cc=han.xu@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=mwalle@kernel.org \
    --cc=richard@nod.at \
    --cc=tudor.ambarus@linaro.org \
    --cc=vigneshr@ti.com \
    --cc=ziniu.wang_1@nxp.com \
    /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®