From: Mark Rutland <mark.rutland@arm.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"martinez.javier@gmail.com" <martinez.javier@gmail.com>,
"matthias.bgg@googlemail.com" <matthias.bgg@googlemail.com>,
"eballetbo@gmail.com" <eballetbo@gmail.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 3/3] arm: omap2: gpmc: add DT bindings for OneNAND
Date: Mon, 21 Jan 2013 12:30:20 +0000 [thread overview]
Message-ID: <20130121123020.GI15707@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1358634477-25868-3-git-send-email-ezequiel.garcia@free-electrons.com>
[...]
> diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
> index 01ce462..f7de9eb 100644
> --- a/arch/arm/mach-omap2/gpmc.c
> +++ b/arch/arm/mach-omap2/gpmc.c
> @@ -39,6 +39,7 @@
> #include "omap_device.h"
> #include "gpmc.h"
> #include "gpmc-nand.h"
> +#include "gpmc-onenand.h"
>
> #define DEVICE_NAME "omap-gpmc"
>
> @@ -1259,6 +1260,43 @@ static int gpmc_probe_nand_child(struct platform_device *pdev,
> }
> #endif
>
> +#ifdef CONFIG_MTD_ONENAND
> +static int gpmc_probe_onenand_child(struct platform_device *pdev,
> + struct device_node *child)
> +{
> + u32 val;
> + struct omap_onenand_platform_data *gpmc_onenand_data;
> +
> + if (of_property_read_u32(child, "reg", &val) < 0) {
> + dev_err(&pdev->dev, "%s has no 'reg' property\n",
> + child->full_name);
> + return -ENODEV;
> + }
> +
> + gpmc_onenand_data = devm_kzalloc(&pdev->dev, sizeof(*gpmc_onenand_data),
> + GFP_KERNEL);
> + if (!gpmc_onenand_data)
> + return -ENOMEM;
> +
> + gpmc_onenand_data->cs = val;
> + gpmc_onenand_data->of_node = child;
> + gpmc_onenand_data->dma_channel = -1;
> +
> + if (!of_property_read_u32(child, "dma-channel", &val))
> + gpmc_onenand_data->dma_channel = val;
> +
> + gpmc_onenand_init(gpmc_onenand_data);
> +
> + return 0;
> +}
> +#else
> +static int gpmc_probe_onenand_child(struct platform_device *pdev,
> + struct device_node *child)
> +{
> + return 0;
> +}
> +#endif
> +
> static int gpmc_probe_dt(struct platform_device *pdev)
> {
> int ret;
> @@ -1276,6 +1314,12 @@ static int gpmc_probe_dt(struct platform_device *pdev)
> return ret;
> }
>
This doesn't look right to me:
> + for_each_node_by_name(child, "onenand") {
> + ret = gpmc_probe_onenand_child(pdev, child);
> + of_node_put(child);
> + if (ret < 0)
> + return ret;
> + }
for_each_node_by_name automatically calls of_node_put on each node once passed,
and as far as I can tell, gpmc_probe_onenand_child doesn't do anything that'd
increment a node's refcount.
As far as I can see, you only need the of_node_put in the error case:
for_each_node_by_name(child, "onenand") {
ret = gpmc_probe_onenand_child(pdev, child);
if (ret < 0) {
of_node_put(child);
return ret;
}
}
Have I missed something here?
> return 0;
> }
> #else
> --
> 1.7.8.6
>
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
>
Thanks,
Mark.
next prev parent reply other threads:[~2013-01-21 12:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 22:27 [PATCH v2 1/3] mtd: omap-onenand: pass device_node in platform data Ezequiel Garcia
2013-01-19 22:27 ` [PATCH v2 2/3] arm: omap2: gpmc-onenand: drop __init annotation Ezequiel Garcia
2013-01-19 22:27 ` [PATCH v2 3/3] arm: omap2: gpmc: add DT bindings for OneNAND Ezequiel Garcia
2013-01-21 12:30 ` Mark Rutland [this message]
2013-01-21 16:57 ` Ezequiel Garcia
2013-01-21 18:33 ` Tony Lindgren
2013-01-22 1:32 ` Daniel Mack
2013-01-22 18:13 ` Ezequiel Garcia
2013-01-22 18:27 ` Tony Lindgren
2013-01-22 19:43 ` Ezequiel Garcia
2013-01-22 20:40 ` Tony Lindgren
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=20130121123020.GI15707@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=eballetbo@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=martinez.javier@gmail.com \
--cc=matthias.bgg@googlemail.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;
as well as URLs for NNTP newsgroup(s).