From: Brian Norris <computersforpeace@gmail.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: 'Wei Yongjun' <weiyj.lk@gmail.com>,
'Artem Bityutskiy' <artem.bityutskiy@linux.intel.com>,
linux-kernel@vger.kernel.org,
'Wei Yongjun' <yongjun_wei@trendmicro.com.cn>,
'Bill Pemberton' <wfp5p@virginia.edu>,
linux-mtd@lists.infradead.org,
'David Woodhouse' <dwmw2@infradead.org>
Subject: Re: [PATCH] MIPS: Alchemy: add missing platform_set_drvdata() in au1550nd_probe()
Date: Tue, 26 Nov 2013 19:35:55 -0800 [thread overview]
Message-ID: <20131127033555.GY9468@ld-irv-0074.broadcom.com> (raw)
In-Reply-To: <004e01ceeb05$9d579690$d806c3b0$%han@samsung.com>
Hi Jingoo,
On Wed, Nov 27, 2013 at 09:14:18AM +0900, Jingoo Han wrote:
> On Wednesday, November 27, 2013 8:50 AM, Brian Norris wrote:
> > On Mon, Nov 11, 2013 at 02:18:29PM +0800, Wei Yongjun wrote:
> > > From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
> > >
> > > Add missing platform_set_drvdata() in au1550nd_probe(), otherwise
> > > calling platform_get_drvdata() in remove returns NULL.
> >
> > An alternative solution: just allocate ctx with devm_kzalloc().Then you
> > don't have to kfree() it at all.
>
> Even if devm_kzalloc() is used, missing platform_set_drvdata() will
> be still necessary.
>
> static int au1550nd_remove(struct platform_device *pdev)
> {
> struct au1550nd_ctx *ctx = platform_get_drvdata(pdev);
> .....
>
> nand_release(&ctx->info);
>
> 'ctx' is still used. Also, in order to use 'ctx',
> platform_get_drvdata(pdev) should be called.
Ah, I overlooked that. Thanks. In that case, you still have to do
something like this patch, and devm_kzalloc() can be left for another
day (or not done at all).
> >
> > I don't mind one solution over the other too much. Let me know which
> > you'd prefer.
> >
> > > Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
> > > ---
> > > drivers/mtd/nand/au1550nd.c | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/drivers/mtd/nand/au1550nd.c b/drivers/mtd/nand/au1550nd.c
> > > index ae8dd7c..909b673 100644
> > > --- a/drivers/mtd/nand/au1550nd.c
> > > +++ b/drivers/mtd/nand/au1550nd.c
> > > @@ -480,6 +480,8 @@ static int au1550nd_probe(struct platform_device *pdev)
> > >
> > > mtd_device_register(&ctx->info, pd->parts, pd->num_parts);
> > >
> > > + platform_set_drvdata(pdev, ctx);
> > > +
> >
> > Personally, I'd choose to call platform_set_drvdata() earlier in the
> > probe routine (e.g., immediately after its allocation), in case we end
> > up calling platform_get_drvdata() from some sub-routine in the future.
>
> Do you mean the following?
> But, most drivers calls platform_set_drvdata() later in the probe routine.
I wouldn't say "most." An unscientific survey seemed to show some
variation, with no clear pattern.
> static int au1550nd_probe(struct platform_device *pdev)
> {
> struct au1550nd_platdata *pd;
> struct au1550nd_ctx *ctx;
> struct nand_chip *this;
> struct resource *r;
> int ret, cs;
>
> pd = dev_get_platdata(&pdev->dev);
> if (!pd) {
> dev_err(&pdev->dev, "missing platform data\n");
> return -ENODEV;
> }
>
> ctx = kzalloc(sizeof(*ctx), GFP_KERNEL);
> if (!ctx) {
> dev_err(&pdev->dev, "no memory for NAND context\n");
> return -ENOMEM;
> }
>
> + platform_set_drvdata(pdev, ctx);
> +
Yes, that looks better to me.
Brian
next prev parent reply other threads:[~2013-11-27 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 6:18 [PATCH] MIPS: Alchemy: add missing platform_set_drvdata() in au1550nd_probe() Wei Yongjun
2013-11-26 23:50 ` Brian Norris
2013-11-27 0:14 ` Jingoo Han
2013-11-27 3:35 ` Brian Norris [this message]
2013-12-17 8:21 ` Brian Norris
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=20131127033555.GY9468@ld-irv-0074.broadcom.com \
--to=computersforpeace@gmail.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=weiyj.lk@gmail.com \
--cc=wfp5p@virginia.edu \
--cc=yongjun_wei@trendmicro.com.cn \
/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