All of lore.kernel.org
 help / color / mirror / Atom feed
From: "shenjian (K)" <shenjian15@huawei.com>
To: "Wang, Dongsheng" <dongsheng.wang@hxt-semitech.com>,
	Andrew Lunn <andrew@lunn.ch>
Cc: Andrew Lunn <andrew@lun>, David Miller <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Zhuangyuzeng (Yisen)" <yisen.zhuang@huawei.com>,
	Salil Mehta <salil.mehta@huawei.com>,
	"lipeng (Y)" <lipeng321@huawei.com>,
	Yunsheng Lin <linyunsheng@huawei.com>,
	Dengweiwei <dengweiwei@huawei.com>
Subject: Re: Question about default m88e1510 LED configuration of marvell phy
Date: Thu, 17 Jan 2019 11:06:17 +0800	[thread overview]
Message-ID: <74ed40b7-d644-4725-f5ec-0a9c97e441ad@huawei.com> (raw)
In-Reply-To: <3b4b16139b974dcf8a8d6d5223e0b901@HXTBJIDCEMVIW02.hxtcorp.net>



在 2019/1/15 17:08, Wang, Dongsheng 写道:
> On 2019/1/15 14:41, shenjian (K) wrote:
>>
>> 在 2019/1/15 11:39, Andrew Lunn 写道:
>>> On Tue, Jan 15, 2019 at 11:07:17AM +0800, shenjian (K) wrote:
>>>> Hi, all
>>>> 	We encounted a problem when using the marvel 88e151x phy driver, the
>>>> link(LED[0])/ack(LED[1]) leds worked abnormally since we updated our kernel to v4.19.
>>>> The act led kept on and never blink.  It works well when we use genphy driver, aslo
>>>> works well when use marvell phy in kernel v4.18.
>>>>
>>>> 	I found that the default led configuration had been changed to 0x1177
>>>> by commit commit 077772468ec1(net: phy: marvell: change default m88e1510 LED configuration).
>>> It is a difficult job deciding what the driver should configure. I
>>> would actually prefer to keeps with the reset default, which would be
>>> 0x101e according to the datasheet.
>>>
>>> If you are using device tree, you have the option of poking values
>>> into registers, using marvell,reg-init. There are a few examples you
>>> can copy. Doing that guarantees you have the configuration you want.
>>>
>>>     Andrew
>>>
>>> .
>>>
>> Thanks, Andrew.
>>
>> But we are using acpi mode, is there any ohter way to poke values into registers ?
> 
> You can describe property in ACPI _DSD. And parse then in
> marvell_config_init just like of.
> 
> Cheers
> Dongsheng
> 
> 
> 
> .
> 
I will check is this supported by our bios.

Thanks, Dongsheng.




  reply	other threads:[~2019-01-17  3:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15  3:07 Question about default m88e1510 LED configuration of marvell phy shenjian (K)
2019-01-15  3:39 ` Andrew Lunn
2019-01-15  6:41   ` shenjian (K)
2019-01-15  9:08     ` Wang, Dongsheng
2019-01-17  3:06       ` shenjian (K) [this message]
2019-01-16 16:04     ` Andrew Lunn
2019-01-17  2:58       ` shenjian (K)
2019-01-17 12:41         ` Andrew Lunn
2019-01-17 14:57           ` shenjian (K)

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=74ed40b7-d644-4725-f5ec-0a9c97e441ad@huawei.com \
    --to=shenjian15@huawei.com \
    --cc=andrew@lun \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dengweiwei@huawei.com \
    --cc=dongsheng.wang@hxt-semitech.com \
    --cc=linyunsheng@huawei.com \
    --cc=lipeng321@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=salil.mehta@huawei.com \
    --cc=yisen.zhuang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.