From: Vinod Koul <vinod.koul@intel.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Arnd Bergmann <arnd@arndb.de>, Jon Hunter <jon-hunter@ti.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dma: of: Remove restriction that #dma-cells can't be 0
Date: Thu, 23 May 2013 16:00:03 +0530 [thread overview]
Message-ID: <20130523103003.GD30200@intel.com> (raw)
In-Reply-To: <1366619613-30639-1-git-send-email-lars@metafoo.de>
On Mon, Apr 22, 2013 at 10:33:32AM +0200, Lars-Peter Clausen wrote:
> There is no sensible reason why #dma-cells shouldn't be allowed to be 0. It is
> completely up to the DMA controller how many additional parameters, besides the
> phandle, it needs to identify a channel. E.g. for DMA controller with only one
> channel or for DMA controllers which don't have a restriction on which channel
> can be used for which peripheral it completely legitimate to not require any
> additional parameters.
>
> Also fixes the following warning:
> drivers/dma/of-dma.c: In function 'of_dma_controller_register':
> drivers/dma/of-dma.c:67:7: warning: 'nbcells' may be used uninitialized in this function
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Applied, both thanks
Sorry looks like I missed applying them earlier...
--
~Vinod
> ---
> drivers/dma/of-dma.c | 11 ++++-------
> 1 file changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/dma/of-dma.c b/drivers/dma/of-dma.c
> index 7aa0864..268cc8a 100644
> --- a/drivers/dma/of-dma.c
> +++ b/drivers/dma/of-dma.c
> @@ -64,7 +64,6 @@ int of_dma_controller_register(struct device_node *np,
> void *data)
> {
> struct of_dma *ofdma;
> - int nbcells;
> const __be32 *prop;
>
> if (!np || !of_dma_xlate) {
> @@ -77,18 +76,16 @@ int of_dma_controller_register(struct device_node *np,
> return -ENOMEM;
>
> prop = of_get_property(np, "#dma-cells", NULL);
> - if (prop)
> - nbcells = be32_to_cpup(prop);
> -
> - if (!prop || !nbcells) {
> - pr_err("%s: #dma-cells property is missing or invalid\n",
> + if (!prop) {
> + pr_err("%s: #dma-cells property is missing\n",
> __func__);
> kfree(ofdma);
> return -EINVAL;
> }
>
> +
> ofdma->of_node = np;
> - ofdma->of_dma_nbcells = nbcells;
> + ofdma->of_dma_nbcells = be32_to_cpup(prop);
> ofdma->of_dma_xlate = of_dma_xlate;
> ofdma->of_dma_data = data;
>
> --
> 1.8.0
>
prev parent reply other threads:[~2013-05-23 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 8:33 [PATCH 1/2] dma: of: Remove restriction that #dma-cells can't be 0 Lars-Peter Clausen
2013-04-22 8:33 ` [PATCH 2/2] dma: of: Remove check on always true condition Lars-Peter Clausen
2013-04-22 12:38 ` Arnd Bergmann
2013-04-22 20:52 ` Jon Hunter
2013-04-22 21:00 ` Lars-Peter Clausen
2013-04-22 22:13 ` Jon Hunter
2013-04-22 12:38 ` [PATCH 1/2] dma: of: Remove restriction that #dma-cells can't be 0 Arnd Bergmann
2013-04-22 12:47 ` Lars-Peter Clausen
2013-04-22 14:54 ` Arnd Bergmann
2013-05-23 10:30 ` Vinod Koul [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=20130523103003.GD30200@intel.com \
--to=vinod.koul@intel.com \
--cc=arnd@arndb.de \
--cc=jon-hunter@ti.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.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