From: Daniel Mack <zonque@gmail.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: netdev@vger.kernel.org, bcousson@baylibre.com, 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 v5 2/5] net: ethernet: cpsw: add optional third memory region for CONTROL module
Date: Fri, 23 Aug 2013 21:14:32 +0200 [thread overview]
Message-ID: <5217B498.9010706@gmail.com> (raw)
In-Reply-To: <5217B3BE.8020003@cogentembedded.com>
On 23.08.2013 21:10, Sergei Shtylyov wrote:
> Hello.
>
> On 08/23/2013 10:53 PM, 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>
>> ---
>> Documentation/devicetree/bindings/net/cpsw.txt | 5 ++++-
>> drivers/net/ethernet/ti/cpsw.c | 5 +++++
>> 2 files changed, 9 insertions(+), 1 deletion(-)
>
>> diff --git a/drivers/net/ethernet/ti/cpsw.c b/drivers/net/ethernet/ti/cpsw.c
>> index fc3263f..4feba2f 100644
>> --- a/drivers/net/ethernet/ti/cpsw.c
>> +++ b/drivers/net/ethernet/ti/cpsw.c
> [...]
>> @@ -1989,6 +1990,10 @@ static int cpsw_probe(struct platform_device *pdev)
>> goto clean_runtime_disable_ret;
>> }
>>
>> + /* Don't fail hard if the optional control memory region is missing */
>> + res = platform_get_resource(pdev, IORESOURCE_MEM, 2);
>> + priv->gmii_sel_reg = devm_ioremap_resource(&pdev->dev, res);
>
> Hm, but why now you don't fail if devm_ioremap_resource() fails?
Well, because I thought maybe we should just ignore failures of that
kind altogether for this optional resource. There will still be a
warning in that case. Did you like the old approach better?
Daniel
next prev parent reply other threads:[~2013-08-23 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 18:53 [PATCH v5 0/5] cpsw: support for control module register Daniel Mack
2013-08-23 18:53 ` [PATCH v5 1/5] net: ethernet: cpsw: switch to devres allocations Daniel Mack
2013-08-23 18:53 ` [PATCH v5 2/5] net: ethernet: cpsw: add optional third memory region for CONTROL module Daniel Mack
2013-08-23 19:10 ` Sergei Shtylyov
2013-08-23 19:14 ` Daniel Mack [this message]
2013-08-23 18:53 ` [PATCH v5 3/5] net: ethernet: cpsw: introduce ti,am3352-cpsw compatible string Daniel Mack
2013-08-23 18:53 ` [PATCH v5 4/5] net: ethernet: cpsw: add support for hardware interface mode config Daniel Mack
2013-08-23 19:18 ` Sergei Shtylyov
2013-08-23 18:53 ` [PATCH v5 5/5] ARM: dts: am33xx: adopt to cpsw changes Daniel Mack
2013-08-23 19:13 ` [PATCH v5 0/5] cpsw: support for control module register Mugunthan V N
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=5217B498.9010706@gmail.com \
--to=zonque@gmail.com \
--cc=bcousson@baylibre.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=sergei.shtylyov@cogentembedded.com \
--cc=ujhelyi.m@gmail.com \
--cc=vaibhav.bedia@ti.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).