public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Johan Jonker <jbx6244@gmail.com>
To: kever.yang@rock-chips.com
Cc: sjg@chromium.org, philipp.tomsich@vrull.eu,
	dario.binacchi@amarulasolutions.com,
	michael@amarulasolutions.com, u-boot@lists.denx.de
Subject: [PATCH v3 4/7] rockchip: block: blk-uclass: disable bounce buffer support for rkmtd
Date: Thu, 12 Oct 2023 22:51:52 +0200	[thread overview]
Message-ID: <4050eaef-b4c7-3f18-6bd0-a89ac03ba4bb@gmail.com> (raw)
In-Reply-To: <9fffc997-fd13-eba2-3a73-a8e86816667c@gmail.com>

Disable bounce buffer support for rkmtd.

Signed-off-by: Johan Jonker <jbx6244@gmail.com>
---

Changed V3:
  New patch
---
 drivers/block/blk-uclass.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/block/blk-uclass.c b/drivers/block/blk-uclass.c
index 30ad5bbb0024..ac1b43d757d8 100644
--- a/drivers/block/blk-uclass.c
+++ b/drivers/block/blk-uclass.c
@@ -415,7 +415,7 @@ struct blk_bounce_buffer {

 static int blk_buffer_aligned(struct bounce_buffer *state)
 {
-#if IS_ENABLED(CONFIG_BOUNCE_BUFFER)
+#if IS_ENABLED(CONFIG_BOUNCE_BUFFER) && !IS_ENABLED(CONFIG_RKMTD)
 	struct blk_bounce_buffer *bbstate =
 		container_of(state, struct blk_bounce_buffer, state);
 	struct udevice *dev = bbstate->dev;
@@ -441,7 +441,7 @@ long blk_read(struct udevice *dev, lbaint_t start, lbaint_t blkcnt, void *buf)
 			  start, blkcnt, desc->blksz, buf))
 		return blkcnt;

-	if (IS_ENABLED(CONFIG_BOUNCE_BUFFER)) {
+	if (IS_ENABLED(CONFIG_BOUNCE_BUFFER) && !IS_ENABLED(CONFIG_RKMTD)) {
 		struct blk_bounce_buffer bbstate = { .dev = dev };
 		int ret;

@@ -478,7 +478,7 @@ long blk_write(struct udevice *dev, lbaint_t start, lbaint_t blkcnt,

 	blkcache_invalidate(desc->uclass_id, desc->devnum);

-	if (IS_ENABLED(CONFIG_BOUNCE_BUFFER)) {
+	if (IS_ENABLED(CONFIG_BOUNCE_BUFFER) && !IS_ENABLED(CONFIG_RKMTD)) {
 		struct blk_bounce_buffer bbstate = { .dev = dev };
 		int ret;

--
2.39.2


  parent reply	other threads:[~2023-10-12 20:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 20:49 [PATCH v3 0/7] Add rkmtd command Johan Jonker
2023-10-12 20:51 ` [PATCH v3 2/7] rockchip: dm: prepare rkmtd UCLASS Johan Jonker
2023-10-13 16:57   ` Simon Glass
2023-10-13 17:27     ` Johan Jonker
2023-10-12 20:51 ` [PATCH v3 3/7] rockchip: block: add rkmtd class and drivers Johan Jonker
2023-10-13  7:15   ` Kever Yang
2023-10-12 20:51 ` Johan Jonker [this message]
2023-10-13  7:15   ` [PATCH v3 4/7] rockchip: block: blk-uclass: disable bounce buffer support for rkmtd Kever Yang
2023-10-12 20:52 ` [PATCH v3 5/7] rockchip: cmd: add rkmtd command Johan Jonker
2023-10-13 15:14   ` Simon Glass
2023-10-12 20:52 ` [PATCH v3 6/7] rockchip: test: dm: add rkmtd test Johan Jonker
2023-10-13  7:15   ` Kever Yang
2023-10-14 18:19     ` Simon Glass
2023-10-12 20:52 ` [PATCH v3 7/7] rockchip: doc: add rkmtd.rst Johan Jonker
2023-10-13  7:16   ` Kever Yang
2023-10-13 15:15   ` Simon Glass
2023-10-14  4:21 ` [PATCH v3] rockchip: configs: sandbox: enable rkmtd command Johan Jonker
2023-10-14 18:20   ` Simon Glass

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=4050eaef-b4c7-3f18-6bd0-a89ac03ba4bb@gmail.com \
    --to=jbx6244@gmail.com \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=kever.yang@rock-chips.com \
    --cc=michael@amarulasolutions.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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