From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Daniel Mack <zonque@gmail.com>
Cc: netdev@vger.kernel.org, nsekhar@ti.com, davem@davemloft.net,
ujhelyi.m@gmail.com, mugunthanvnm@ti.com, vaibhav.bedia@ti.com,
d-gerlach@ti.com, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/5] net: ethernet: cpsw: add optional third memory region for CONTROL module
Date: Fri, 23 Aug 2013 18:03:35 +0400 [thread overview]
Message-ID: <52176BB7.3000405@cogentembedded.com> (raw)
In-Reply-To: <1377247417-27386-3-git-send-email-zonque@gmail.com>
Hello.
On 23-08-2013 12:43, Daniel Mack wrote:
> At least the AM33xx SoC has a control module register to configure
> details such as the hardware ethernet interface mode.
> I'm not sure whether all SoCs which feature the cpsw block have such a
> register, so that third memory region is considered optional for now.
> Signed-off-by: Daniel Mack <zonque@gmail.com>
[...]
> diff --git a/drivers/net/ethernet/ti/cpsw.c b/drivers/net/ethernet/ti/cpsw.c
> index 1a91aac..bd0b664 100644
> --- a/drivers/net/ethernet/ti/cpsw.c
> +++ b/drivers/net/ethernet/ti/cpsw.c
[...]
> @@ -1999,6 +2000,21 @@ static int cpsw_probe(struct platform_device *pdev)
> goto clean_runtime_disable_ret;
> }
>
> + /* If the control memory region is unspecified, continue without it.
> + * If it is specified, but we're unable to reserve it, bail.
> + */
> + res = platform_get_resource(pdev, IORESOURCE_MEM, 2);
> + if (!res) {
> + dev_err(priv->dev, "error getting control i/o resource\n");
If the resource is optional, why use dev_err()?
> + goto no_gmii_sel;
> + }
> + priv->gmii_sel_reg = devm_ioremap_resource(&pdev->dev, res);
> + if (!priv->gmii_sel_reg) {
devm_ioremap_resource() doesn't return NULL, it returns error, so you
should check with IS_ERR() and propagate the error to the caller with PTR_ERR().
> + dev_err(priv->dev, "unable to map control i/o region\n");
devm_ioremap_resource() prints out the error messages itself, so you don't
have to.
> + goto clean_runtime_disable_ret;
> + }
> +
> +no_gmii_sel:
> memset(&dma_params, 0, sizeof(dma_params));
> memset(&ale_params, 0, sizeof(ale_params));
WBR, Sergei
next prev parent reply other threads:[~2013-08-23 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 8:43 [PATCH v2 0/5] cpsw: support for control module register Daniel Mack
2013-08-23 8:43 ` [PATCH v2 1/5] net: ethernet: cpsw: switch to devres allocations Daniel Mack
2013-08-23 8:43 ` [PATCH v2 2/5] net: ethernet: cpsw: add optional third memory region for CONTROL module Daniel Mack
2013-08-23 14:03 ` Sergei Shtylyov [this message]
2013-08-23 14:05 ` Daniel Mack
2013-08-23 8:43 ` [PATCH v2 3/5] net: ethernet: cpsw: introduce ti,am3352-cpsw compatible string Daniel Mack
2013-08-23 8:43 ` [PATCH v2 4/5] net: ethernet: cpsw: add support for hardware interface mode config Daniel Mack
2013-08-23 16:38 ` Mugunthan V N
2013-08-23 8:43 ` [PATCH v2 5/5] ARM: dts: am33xx: adopt to cpsw changes Daniel Mack
2013-08-23 9:28 ` Sekhar Nori
2013-08-23 9:34 ` Daniel Mack
2013-08-23 9:40 ` Sekhar Nori
2013-08-23 12:08 ` Daniel Mack
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=52176BB7.3000405@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=d-gerlach@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=ujhelyi.m@gmail.com \
--cc=vaibhav.bedia@ti.com \
--cc=zonque@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).