From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] dma: Reduce error level when DMA channel type does not exist
Date: Wed, 23 Sep 2020 08:58:41 +0200 [thread overview]
Message-ID: <81c03aad-9844-b091-8d90-31cb7f959921@denx.de> (raw)
In-Reply-To: <20200917112308.7736-2-vigneshr@ti.com>
On 17.09.20 13:23, Vignesh Raghavendra wrote:
> 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>
Reviewed-by: Stefan Roese <sr@denx.de>
Thanks,
Stefan
> ---
> 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;
> }
>
>
Viele Gr??e,
Stefan
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-51 Fax: (+49)-8142-66989-80 Email: sr at denx.de
next prev parent reply other threads:[~2020-09-23 6:58 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 ` [PATCH 1/2] dma: Reduce error level when DMA channel type does not exist Vignesh Raghavendra
2020-09-23 6:58 ` Stefan Roese [this message]
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=81c03aad-9844-b091-8d90-31cb7f959921@denx.de \
--to=sr@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.