From: Florian Fainelli <f.fainelli@gmail.com>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>,
jonas.gorski@gmail.com, "Andrew Lunn" <andrew@lunn.ch>,
"Vivien Didelot" <vivien.didelot@gmail.com>,
"Vladimir Oltean" <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: dsa: b53: mmap: Add device tree support
Date: Mon, 8 Mar 2021 10:29:52 -0800 [thread overview]
Message-ID: <06dab800-d554-e807-8a72-427c6e99e4de@gmail.com> (raw)
In-Reply-To: <20210308180715.18571-1-noltari@gmail.com>
On 3/8/21 10:07 AM, Álvaro Fernández Rojas wrote:
> Add device tree support to b53_mmap.c while keeping platform devices support.
>
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> ---
> drivers/net/dsa/b53/b53_mmap.c | 36 ++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
>
> diff --git a/drivers/net/dsa/b53/b53_mmap.c b/drivers/net/dsa/b53/b53_mmap.c
> index c628d0980c0b..b897b4263930 100644
> --- a/drivers/net/dsa/b53/b53_mmap.c
> +++ b/drivers/net/dsa/b53/b53_mmap.c
> @@ -228,12 +228,48 @@ static const struct b53_io_ops b53_mmap_ops = {
> .write64 = b53_mmap_write64,
> };
>
> +static int b53_mmap_probe_of(struct platform_device *pdev,
> + struct b53_platform_data **ppdata)
> +{
> + struct device *dev = &pdev->dev;
> + struct device_node *np = dev->of_node;
> + struct b53_platform_data *pdata;
> + void __iomem *mem;
> +
> + mem = devm_platform_ioremap_resource(pdev, 0);
> + if (IS_ERR(mem))
> + return PTR_ERR(mem);
> +
> + pdata = devm_kzalloc(dev, sizeof(struct b53_platform_data),
> + GFP_KERNEL);
> + if (!pdata)
> + return -ENOMEM;
> +
> + pdata->regs = mem;
> + pdata->chip_id = BCM63XX_DEVICE_ID;
> + pdata->big_endian = of_property_read_bool(np, "big-endian");
> + of_property_read_u16(np, "brcm,ports", &pdata->enabled_ports);
> +
> + *ppdata = pdata;
> +
> + return 0;
> +}
> +
> static int b53_mmap_probe(struct platform_device *pdev)
> {
> + struct device_node *np = pdev->dev.of_node;
> struct b53_platform_data *pdata = pdev->dev.platform_data;
> struct b53_mmap_priv *priv;
> struct b53_device *dev;
>
> + if (np) {
> + int ret = b53_mmap_probe_of(pdev, &pdata);
> + if (ret) {
> + dev_err(&pdev->dev, "OF probe error\n");
> + return ret;
> + }
> + }
I would be keen on making this less "OF-centric" and just have it happen
whenever pdata is NULL such that we have an easier transition path if we
wanted to migrate bcm63xx to passing down the switch base register
address a platform_device source in the future (not that I expect it to
happen though).
Other than that, the logic looks sound.
--
Florian
next prev parent reply other threads:[~2021-03-08 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 18:07 [PATCH] net: dsa: b53: mmap: Add device tree support Álvaro Fernández Rojas
2021-03-08 18:29 ` Florian Fainelli [this message]
2021-03-08 18:34 ` Álvaro Fernández Rojas
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=06dab800-d554-e807-8a72-427c6e99e4de@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.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).