From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/5] spi: i.MX: Move to coredevice_initcall
Date: Mon, 12 May 2014 12:38:50 +0200 [thread overview]
Message-ID: <20140512103850.GF5858@pengutronix.de> (raw)
In-Reply-To: <1399834166.925793804@f410.i.mail.ru>
On Sun, May 11, 2014 at 10:49:26PM +0400, Alexander Shiyan wrote:
> Thu, 8 May 2014 09:31:36 +0200 от Sascha Hauer <s.hauer@pengutronix.de>:
> > SPI is often used by other devices, so make sure it's initialized
> > early.
> >
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > ---
> > drivers/spi/imx_spi.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/spi/imx_spi.c b/drivers/spi/imx_spi.c
> > index e07cf1a..3146339 100644
> > --- a/drivers/spi/imx_spi.c
> > +++ b/drivers/spi/imx_spi.c
> > @@ -586,4 +586,4 @@ static struct driver_d imx_spi_driver = {
> > .of_compatible = DRV_OF_COMPAT(imx_spi_dt_ids),
> > .id_table = imx_spi_ids,
> > };
> > -device_platform_driver(imx_spi_driver);
> > +coredevice_platform_driver(imx_spi_driver);
> > --
>
> Maybe we should put all drivers in a single runlevel and implement
> handle of EPROBE_DEFER?
I think about EPROBE_DEFER for longer now. What has hold me back was
that we would have to release all resources before returning
EPROBE_DEFER. Most drivers don't have proper error pathes implemented
and I don't see much gain in fixing this. For a bootloader the error
release pathes are unnecessary overhead, because nobody will ever
use the same resources again (at least without EPROBE_DEFER).
My recent idea to work around that issue is this:
- put the drivers private data into dev->priv
- when returning an error from probe, instead of freeing the data
keep it.
- when probing again re-use the data.
With this drivers could be written like:
priv = dev->priv;
if (!priv) {
priv = xzalloc(sizeof(priv));
dev->priv = priv;
}
if (!priv->clk) {
clk = clk_get(dev, NULL);
if (IS_ERR(clk))
return PTR_ERR(clk);
priv->clk = clk;
clk_enable(priv->clk);
}
if (!priv->regulator) {
regulator = regulator_get(dev, "vmmc");
if (IS_ERR(regulator))
return PTR_ERR(regulator);
priv->regulator = regulator;
}
This way drivers could allocate the missing resources as needed without
freeing them between different calls to probe().
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-05-12 10:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 7:31 [PATCH] fix i.MX51 babbage ethernet Sascha Hauer
2014-05-08 7:31 ` [PATCH 1/5] mfd: mc13xxx: Allow to set callback for mc13xxx Sascha Hauer
2014-05-18 23:14 ` Marc Reilly
2014-05-19 6:40 ` Sascha Hauer
2014-05-08 7:31 ` [PATCH 2/5] spi: i.MX: Move to coredevice_initcall Sascha Hauer
2014-05-11 18:49 ` Alexander Shiyan
2014-05-12 10:38 ` Sascha Hauer [this message]
2014-05-14 17:57 ` Alexander Shiyan
2014-05-19 8:47 ` Sascha Hauer
2014-05-08 7:31 ` [PATCH 3/5] mfd: mc13xxx: move " Sascha Hauer
2014-05-08 7:31 ` [PATCH 4/5] ARM: i.MX51 babbage: use mc13xxx_register_callback to initialize PMIC Sascha Hauer
2014-05-08 7:31 ` [PATCH 5/5] ARM: dts: i.MX51 babbage: overwrite upstream FEC iomux settings Sascha Hauer
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=20140512103850.GF5858@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=shc_work@mail.ru \
/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