public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] dma: Reduce error level when DMA channel type does not exist
Date: Thu, 17 Sep 2020 16:53:07 +0530	[thread overview]
Message-ID: <20200917112308.7736-2-vigneshr@ti.com> (raw)
In-Reply-To: <20200917112308.7736-1-vigneshr@ti.com>

Caller would need gracefully handle failures of dma_get_device(),
therefore reduce pr_err() to pr_debug() when DMA device is not found.

Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
---
 drivers/dma/dma-uclass.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/dma/dma-uclass.c b/drivers/dma/dma-uclass.c
index 8cbb364042..50403148d6 100644
--- a/drivers/dma/dma-uclass.c
+++ b/drivers/dma/dma-uclass.c
@@ -219,8 +219,8 @@ int dma_get_device(u32 transfer_type, struct udevice **devp)
 	}
 
 	if (!dev) {
-		pr_err("No DMA device found that supports %x type\n",
-		      transfer_type);
+		pr_debug("No DMA device found that supports %x type\n",
+			 transfer_type);
 		return -EPROTONOSUPPORT;
 	}
 
-- 
2.28.0

  reply	other threads:[~2020-09-17 11:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 11:23 [PATCH 0/2] mtd: cfi_mtd: Add DMA support for reads Vignesh Raghavendra
2020-09-17 11:23 ` Vignesh Raghavendra [this message]
2020-09-23  6:58   ` [PATCH 1/2] dma: Reduce error level when DMA channel type does not exist Stefan Roese
2020-10-08  7:08   ` Stefan Roese
2020-09-17 11:23 ` [PATCH 2/2] mtd: cfi_mtd: Use DMA for reads Vignesh Raghavendra
2020-09-23  6:59   ` Stefan Roese
2020-10-08  7:08   ` Stefan Roese
2020-10-05 18:42 ` [PATCH 0/2] mtd: cfi_mtd: Add DMA support " Vignesh Raghavendra
2020-10-07  4:55   ` Stefan Roese

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=20200917112308.7736-2-vigneshr@ti.com \
    --to=vigneshr@ti.com \
    --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