From: Ilya Yanok <yanok@emcraft.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Igor Grinberg <grinberg@compulab.co.il>,
linux-omap@vger.kernel.org, wd@denx.de, dzu@denx.de,
sasha_d@emcraft.com, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH] am35xx-emac: move generic EMAC init to separate file
Date: Fri, 16 Dec 2011 01:42:26 +0400 [thread overview]
Message-ID: <4EEA69C2.4000503@emcraft.com> (raw)
In-Reply-To: <20111215184342.GT32251@atomide.com>
Hi Tony,
On 15.12.2011 22:43, Tony Lindgren wrote:
>>>> Should this be just called emac-common.c? Or is it so am35xx specific
>>>> that it won't work with others?
>>>
>>> Uh.. I'm not sure but I thought that EMAC is present only on am35xx SoCs...
>
> OK, maybe just do a quick check on that so we don't end up
> moving the platform init code around again in few months?
Well, according to TI site, EMAC can be also found on AM33x, AM387x and
AM389x... I'm not sure if it's completely compatible but probably though.
>>>>> + clk_add_alias(NULL, dev_name(&am35xx_emac_device.dev),
>>>>> + "emac_clk", &am35xx_emac_device.dev);
>>>>> + clk_add_alias(NULL, dev_name(&am35xx_mdio_device.dev),
>>>>> + "phy_clk", &am35xx_emac_device.dev);
>>>>
>>>> Hmm after moving the code and should be a separate patch, don't
>>>> we already have these clock aliases in cloc3xxx_data.c?
>>>
>>> No, we have
>>> CLK("davinci_emac", "emac_clk"...) and
>>> CLK("davinci_emac", "phy_clk"...)
>>> while drivers want ("davinci_emac", NULL) and ("davinci_mdio", NULL).
>>>
>>> Probably we have to fix the clock definitions instead of adding the aliases.
>>>
>>> So, should I post this as a separate patch?
>>
>> If it comes to that question, Cc Paul...
>
> Yes please do that as a separate patch.
Ok, let's wait for Paul's answer and then I'll prepare a separate patch.
Regards, Ilya.
next prev parent reply other threads:[~2011-12-15 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 0:36 [PATCH] am35xx-emac: move generic EMAC init to separate file Ilya Yanok
2011-12-08 0:15 ` Tony Lindgren
2011-12-14 23:46 ` Ilya Yanok
2011-12-15 9:39 ` Igor Grinberg
2011-12-15 18:43 ` Tony Lindgren
2011-12-15 21:42 ` Ilya Yanok [this message]
2011-12-16 6:13 ` Paul Walmsley
2011-12-20 22:31 ` Ilya Yanok
2011-12-21 1:38 ` Paul Walmsley
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=4EEA69C2.4000503@emcraft.com \
--to=yanok@emcraft.com \
--cc=dzu@denx.de \
--cc=grinberg@compulab.co.il \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=sasha_d@emcraft.com \
--cc=tony@atomide.com \
--cc=wd@denx.de \
/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).