From: Damien Riegel <damien.riegel@savoirfairelinux.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-can@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Wolfgang Grandegger <wg@grandegger.com>,
kernel@savoirfairelinux.com
Subject: Re: [PATCH v2 1/3] can: sja1000: of: add per-compatible init hook
Date: Tue, 12 Jan 2016 10:53:30 -0500 [thread overview]
Message-ID: <20160112155329.GB6050@localhost> (raw)
In-Reply-To: <5694B0A6.8070200@pengutronix.de>
On Tue, Jan 12, 2016 at 08:52:06AM +0100, Marc Kleine-Budde wrote:
> On 12/24/2015 06:42 PM, Damien Riegel wrote:
> > This commit adds the capability to allocate and init private data
> > embedded in the sja1000_priv structure on a per-compatible basis. The
> > device node is passed as a parameter of the init callback to allow
> > parsing of custom device tree properties.
> >
> > Signed-off-by: Damien Riegel <damien.riegel@savoirfairelinux.com>
> > ---
> > drivers/net/can/sja1000/sja1000_platform.c | 39 ++++++++++++++++++++++++++++--
> > 1 file changed, 37 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/net/can/sja1000/sja1000_platform.c b/drivers/net/can/sja1000/sja1000_platform.c
> > index 0552ed4..e0572d0 100644
> > --- a/drivers/net/can/sja1000/sja1000_platform.c
> > +++ b/drivers/net/can/sja1000/sja1000_platform.c
> > @@ -40,6 +40,11 @@ MODULE_DESCRIPTION("Socket-CAN driver for SJA1000 on the platform bus");
> > MODULE_ALIAS("platform:" DRV_NAME);
> > MODULE_LICENSE("GPL v2");
> >
> > +struct sja1000_of_data {
> > + size_t priv_sz;
> > + int (*init)(struct sja1000_priv *priv, struct device_node *of);
> > +};
> > +
> > static u8 sp_read_reg8(const struct sja1000_priv *priv, int reg)
> > {
> > return ioread8(priv->reg_base + reg);
> > @@ -154,7 +159,8 @@ static void sp_populate_of(struct sja1000_priv *priv, struct device_node *of)
> > priv->cdr |= CDR_CBP; /* default */
> > }
> >
> > -static int sp_probe(struct platform_device *pdev)
> > +static int __sp_probe(struct platform_device *pdev,
> > + const struct sja1000_of_data *of_data)
> > {
> > int err, irq = 0;
> > void __iomem *addr;
> > @@ -163,6 +169,7 @@ static int sp_probe(struct platform_device *pdev)
> > struct resource *res_mem, *res_irq = NULL;
> > struct sja1000_platform_data *pdata;
> > struct device_node *of = pdev->dev.of_node;
> > + size_t priv_sz = of_data ? of_data->priv_sz : 0;
> >
> > pdata = dev_get_platdata(&pdev->dev);
> > if (!pdata && !of) {
> > @@ -191,7 +198,7 @@ static int sp_probe(struct platform_device *pdev)
> > if (!irq && !res_irq)
> > return -ENODEV;
> >
> > - dev = alloc_sja1000dev(0);
> > + dev = alloc_sja1000dev(priv_sz);
> > if (!dev)
> > return -ENOMEM;
> > priv = netdev_priv(dev);
> > @@ -213,6 +220,12 @@ static int sp_probe(struct platform_device *pdev)
> > else
> > sp_populate(priv, pdata, res_mem->flags);
> >
> > + if (of_data && of_data->init) {
> > + err = of_data->init(priv, of);
> > + if (err)
> > + goto exit_free;
> > + }
> > +
> > platform_set_drvdata(pdev, dev);
> > SET_NETDEV_DEV(dev, &pdev->dev);
> >
> > @@ -248,6 +261,28 @@ static const struct of_device_id sp_of_table[] = {
> > };
> > MODULE_DEVICE_TABLE(of, sp_of_table);
> >
> > +static const struct sja1000_of_data *sp_get_of_data(struct device_node *of)
> > +{
> > + const struct of_device_id *id;
> > +
> > + if (!of)
> > + return NULL;
> > +
> > + id = of_match_node(sp_of_table, of);
> > + if (!id)
> > + return NULL;
> > +
> > + return id->data;
> > +}
> > +
> > +static int sp_probe(struct platform_device *pdev)
> > +{
> > + struct device_node *of = pdev->dev.of_node;
> > + const struct sja1000_of_data *of_data = sp_get_of_data(of);
> > +
> > + return __sp_probe(pdev, of_data);
> > +}
>
> Please merge these two into the original sp_probe function, as there
> already is a test for pdev->dev.of_node.
Ok. sp_get_of_data makes use of sp_of_table, so either I move sp_probe
below sp_of_table, or I use a forward declaration. Which one do you
prefer?
Damien
next prev parent reply other threads:[~2016-01-12 15:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 17:42 [PATCH v2 0/3] can: sja1000: support for technologic version Damien Riegel
2015-12-24 17:42 ` [PATCH v2 1/3] can: sja1000: of: add per-compatible init hook Damien Riegel
2016-01-12 7:52 ` Marc Kleine-Budde
2016-01-12 15:53 ` Damien Riegel [this message]
2016-01-12 16:24 ` Marc Kleine-Budde
2015-12-24 17:42 ` [PATCH v2 2/3] can: sja1000: add documentation for Technologic Systems version Damien Riegel
2015-12-24 17:42 ` [PATCH v2 3/3] can: sja1000: of: add compatibility with " Damien Riegel
2016-01-12 7:55 ` Marc Kleine-Budde
2016-01-12 15:51 ` Damien Riegel
2016-01-11 16:58 ` [PATCH v2 0/3] can: sja1000: support for technologic version Damien Riegel
2016-01-12 7:56 ` Marc Kleine-Budde
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=20160112155329.GB6050@localhost \
--to=damien.riegel@savoirfairelinux.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@savoirfairelinux.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=wg@grandegger.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).