From: Nicolas Ferre <nicolas.ferre@atmel•com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft•com>
Cc: Ludovic Desroches <ludovic.desroches@atmel•com>,
Baruch Siach <baruch@tkos•co.il>,
netdev@vger•kernel.org, linux-arm-kernel@lists•infradead.org
Subject: Re: How to deal with a PHY configuration related to the board?
Date: Tue, 14 Feb 2012 15:01:09 +0100 [thread overview]
Message-ID: <4F3A6925.2060601@atmel.com> (raw)
In-Reply-To: <20120214112248.GA20876@game.jcrosoft.org>
On 02/14/2012 12:22 PM, Jean-Christophe PLAGNIOL-VILLARD :
> On 11:33 Tue 14 Feb , Ludovic Desroches wrote:
>> Hi Baruch,
>>
>> On Tue, Feb 14, 2012 at 11:43:39AM +0200, Baruch Siach wrote:
>>> Hi Ludovic,
>>>
>>> On Tue, Feb 14, 2012 at 10:26:06AM +0100, Ludovic Desroches wrote:
>>>> I am using a Micrel KSZ9021RN PHY and I would like to configure some
>>>> registers
>>>> as 'RGMII Clock and Control Pad Skew' and 'RGMII RX Data Pad Skew'.
>>>> So the values of these registers are board dependant and I wondering what is
>>>> the proper way to set them.
>>>> It seems there is no platform data usable for this case. Having a quick look
>>>> to other PHYs, the situation seems the same.
>>>>
>>>> Can you give me some clues about how to do this? Did I miss anything which
>>>> allow to do this?
>>>
>>> See ksz9021rn_phy_fixup() in arch/arm/mach-imx/mach-imx6q.c.
>>>
>>
>> Thanks for your help.
>>
>> So the solution is to use phy_register_fixup function.
> dts
?
Can you please build sentences?
(even if I suspect to know what you are talking about ;-))
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2012-02-14 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 9:26 How to deal with a PHY configuration related to the board? Ludovic Desroches
2012-02-14 9:43 ` Baruch Siach
2012-02-14 10:33 ` Ludovic Desroches
2012-02-14 11:22 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-14 14:01 ` Nicolas Ferre [this message]
2012-02-16 9:51 ` Andy Fleming
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=4F3A6925.2060601@atmel.com \
--to=nicolas.ferre@atmel$(echo .)com \
--cc=baruch@tkos$(echo .)co.il \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=ludovic.desroches@atmel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=plagnioj@jcrosoft$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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