[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=VyzaPEQvY57AF65VGzv600uBZT9jQy4N=s4Z_YPzphxw@mail.gmail.com>
Date: Fri, 13 May 2016 15:04:53 -0700
From: Doug Anderson <dianders@...omium.org>
To: Brian Norris <briannorris@...omium.org>
Cc: Kishon Vijay Abraham I <kishon@...com>,
Heiko Stuebner <heiko@...ech.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Shawn Lin <shawn.lin@...k-chips.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Brian Norris <computersforpeace@...il.com>
Subject: Re: [PATCH v2 2/4] phy: rockchip-emmc: configure frequency range and
drive impedance
Hi,
On Fri, May 13, 2016 at 2:09 PM, Brian Norris <briannorris@...omium.org> wrote:
> From: Shawn Lin <shawn.lin@...k-chips.com>
>
> Signal integrity analysis has suggested we set these values. Do this in
> power_on(), so that they get reconfigured after suspend/resume.
>
> Signed-off-by: Shawn Lin <shawn.lin@...k-chips.com>
> Signed-off-by: Brian Norris <briannorris@...omium.org>
> ---
> v2:
> * Sent only patch 2/4 with version 2, to avoid spamming; will move on to v3
> for all patches if I need to send another
> * Drop 170 MHz comment; this was only applicable to a subtly different Arasan
> PHY
>
> drivers/phy/phy-rockchip-emmc.c | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
As per my comments on v1, this is a sane starting point and seems like
a good idea to land. Hopefully someone at Rockchip can pick things up
and continue making this more configurable.
Reviewed-by: Douglas Anderson <dianders@...omium.org>
Powered by blists - more mailing lists