From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: "'Kukjin Kim'" <kgene@kernel.org>
Cc: "'Byungho An'" <bh74.an@samsung.com>,
netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-next] stmmac: added device tree support for fixed_phy and phy_addr
Date: Fri, 14 Jun 2013 08:29:24 +0200 [thread overview]
Message-ID: <51BAB844.4020102@st.com> (raw)
In-Reply-To: <150a01ce682e$a9e95ab0$fdbc1010$@org>
On 6/13/2013 2:08 PM, 'Kukjin Kim' wrote:
> Byungho An wrote:
>>
>>
>> On 6/13/2013 7:04 PM, Giuseppe CAVALLARO wrote:
>>> On 6/13/2013 3:25 AM, Byungho An wrote:
>>>>
>>>> This patch adds device tree support for fixed_phy and phy_addr it
>> means
>>>> fixed_phy and phy_addr can be set in device tree file. "fixed_phy" and
>>>> "phy_addr" can be added in the device tree blob.
>>>
>>> concerning this, we had added some work to pass from the platform
>>> the fixed bus name.
>>>
>>> http://git.stlinux.com/?p=stm/linux-
>>>
>> stm.git;a=blob;f=drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c;h=2
>> d540e1d2151e4412a5af5356d24d
>>> 5c6b66cf72e;hb=HEAD
>>>
> Looks good.
>
>>> I wanted to also do a clean-up and update the DT support because
>>> the binding documentation remains obsolete etc.
>>>
> Yeah, I see...
>
>>
>> I think your previous work for DT support can cover my patch.
>> Do you have a plan to update and clean-up for DT support?
>>
> Same here, would be nice if the patch could be seen in upcoming kernel.
for sure, I'll plan to send this work asasp
>
> If any help is required, let us know. Byungho will help you.
ok, thx
peppe
>
> Thanks,
> - Kukjin
>
>
>
prev parent reply other threads:[~2013-06-14 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 1:25 [PATCH net-next] stmmac: added device tree support for fixed_phy and phy_addr Byungho An
2013-06-13 9:31 ` David Miller
2013-06-13 10:02 ` Giuseppe CAVALLARO
2013-06-13 10:25 ` Byungho An
2013-06-13 12:08 ` 'Kukjin Kim'
2013-06-14 6:29 ` Giuseppe CAVALLARO [this message]
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=51BAB844.4020102@st.com \
--to=peppe.cavallaro@st.com \
--cc=bh74.an@samsung.com \
--cc=davem@davemloft.net \
--cc=kgene@kernel.org \
--cc=netdev@vger.kernel.org \
/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).