All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Shawn Lin <shawn.lin@rock-chips.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Heiko Stuebner <heiko@sntech.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Brian Norris <computersforpeace@gmail.com>
Subject: Re: [PATCH 2/4] phy: rockchip-emmc: configure frequency range and drive impedance
Date: Fri, 13 May 2016 14:04:40 -0700	[thread overview]
Message-ID: <20160513210440.GA99074@google.com> (raw)
In-Reply-To: <CAD=FV=UwocUy_bOUrJZB47taHWdV1KGkvi5CyZf74Y8cvGgVmw@mail.gmail.com>

On Fri, May 13, 2016 at 11:46:33AM -0700, Doug Anderson wrote:
> On Thu, May 12, 2016 at 6:02 PM, Shawn Lin <shawn.lin@rock-chips.com> wrote:
> > On 2016/5/13 6:43, Brian Norris wrote:
> >> @@ -154,6 +167,20 @@ static int rockchip_emmc_phy_power_on(struct phy
> >> *phy)
> >>         struct rockchip_emmc_phy *rk_phy = phy_get_drvdata(phy);
> >>         int ret = 0;
> >>
> >> +       /* DLL operation: 170 to 200 MHz */
> >
> >
> > What is 170 here? Should we expose them to dt instead of hardcoding
> > them?
> 
> This was probably my fault.  I did some searching and found
> <https://arasan.com/wp-content/media/eMMC-5-1-Total-Solution_Rev-1-3.pdf>.
> It appears to be docs for a similar (but not identical) PHY.  We were
> looking at it to try to get more clarity on some bits that were hard
> to understand in the docs we had.
> 
> In that doc there appear to be 3 bits for selecting the DLL operation
> and they have ranges defined.  In Rockchip's PHY there are only 2
> bits.  Thus things don't map totally properly.
> 
> Anyway, comment should probably be removed.

[...]

> So overall:
> 
> * Should re-spin and remove the comment about 170 MHz.
> 
> * I think this could land as-is other than the comment.

Right, will fix the first bullet point.

Brian

WARNING: multiple messages have this Message-ID (diff)
From: briannorris@chromium.org (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] phy: rockchip-emmc: configure frequency range and drive impedance
Date: Fri, 13 May 2016 14:04:40 -0700	[thread overview]
Message-ID: <20160513210440.GA99074@google.com> (raw)
In-Reply-To: <CAD=FV=UwocUy_bOUrJZB47taHWdV1KGkvi5CyZf74Y8cvGgVmw@mail.gmail.com>

On Fri, May 13, 2016 at 11:46:33AM -0700, Doug Anderson wrote:
> On Thu, May 12, 2016 at 6:02 PM, Shawn Lin <shawn.lin@rock-chips.com> wrote:
> > On 2016/5/13 6:43, Brian Norris wrote:
> >> @@ -154,6 +167,20 @@ static int rockchip_emmc_phy_power_on(struct phy
> >> *phy)
> >>         struct rockchip_emmc_phy *rk_phy = phy_get_drvdata(phy);
> >>         int ret = 0;
> >>
> >> +       /* DLL operation: 170 to 200 MHz */
> >
> >
> > What is 170 here? Should we expose them to dt instead of hardcoding
> > them?
> 
> This was probably my fault.  I did some searching and found
> <https://arasan.com/wp-content/media/eMMC-5-1-Total-Solution_Rev-1-3.pdf>.
> It appears to be docs for a similar (but not identical) PHY.  We were
> looking at it to try to get more clarity on some bits that were hard
> to understand in the docs we had.
> 
> In that doc there appear to be 3 bits for selecting the DLL operation
> and they have ranges defined.  In Rockchip's PHY there are only 2
> bits.  Thus things don't map totally properly.
> 
> Anyway, comment should probably be removed.

[...]

> So overall:
> 
> * Should re-spin and remove the comment about 170 MHz.
> 
> * I think this could land as-is other than the comment.

Right, will fix the first bullet point.

Brian

  reply	other threads:[~2016-05-13 21:04 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 22:43 [PATCH 1/4] phy: rockchip-emmc: give DLL some extra time to be ready Brian Norris
2016-05-12 22:43 ` Brian Norris
2016-05-12 22:43 ` Brian Norris
     [not found] ` <1463092986-61777-1-git-send-email-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-05-12 22:43   ` [PATCH 2/4] phy: rockchip-emmc: configure frequency range and drive impedance Brian Norris
2016-05-12 22:43     ` Brian Norris
2016-05-12 22:43     ` Brian Norris
2016-05-13  1:02     ` Shawn Lin
2016-05-13  1:02       ` Shawn Lin
2016-05-13 18:46       ` Doug Anderson
2016-05-13 18:46         ` Doug Anderson
2016-05-13 21:04         ` Brian Norris [this message]
2016-05-13 21:04           ` Brian Norris
2016-05-24  4:51         ` Doug Anderson
2016-05-24  4:51           ` Doug Anderson
2016-05-13 21:09     ` [PATCH v2 " Brian Norris
2016-05-13 21:09       ` Brian Norris
2016-05-13 22:04       ` Doug Anderson
2016-05-13 22:04         ` Doug Anderson
2016-06-16 23:36       ` Heiko Stuebner
2016-06-16 23:36         ` Heiko Stuebner
2016-06-20 13:11     ` [PATCH " Kishon Vijay Abraham I
2016-06-20 13:11       ` Kishon Vijay Abraham I
2016-06-20 13:11       ` Kishon Vijay Abraham I
2016-06-20 13:11   ` [PATCH 1/4] phy: rockchip-emmc: give DLL some extra time to be ready Kishon Vijay Abraham I
2016-06-20 13:11     ` Kishon Vijay Abraham I
2016-06-20 13:11     ` Kishon Vijay Abraham I
2016-06-20 16:19     ` Brian Norris
2016-06-20 16:19       ` Brian Norris
2016-06-20 16:19       ` Brian Norris
2016-06-20 16:25       ` Doug Anderson
2016-06-20 16:25         ` Doug Anderson
2016-06-20 16:50         ` Brian Norris
2016-06-20 16:50           ` Brian Norris
2016-05-12 22:43 ` [PATCH 3/4] phy: rockchip-emmc: configure default output tap delay Brian Norris
2016-05-12 22:43   ` Brian Norris
2016-05-12 22:43   ` Brian Norris
2016-05-13 22:25   ` Doug Anderson
2016-05-13 22:25     ` Doug Anderson
2016-05-16  4:15     ` Shawn Lin
2016-05-16  4:15       ` Shawn Lin
     [not found]       ` <52567d92-d1d3-f089-65c2-a30f3a00386b-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-05-16 15:12         ` Doug Anderson
2016-05-16 15:12           ` Doug Anderson
2016-05-16 15:12           ` Doug Anderson
2016-06-16 23:36   ` Heiko Stuebner
2016-06-16 23:36     ` Heiko Stuebner
     [not found]   ` <1463092986-61777-3-git-send-email-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-06-20 13:11     ` Kishon Vijay Abraham I
2016-06-20 13:11       ` Kishon Vijay Abraham I
2016-06-20 13:11       ` Kishon Vijay Abraham I
2016-05-12 22:43 ` [PATCH 4/4] phy: rockchip-emmc: reindent the register definitions Brian Norris
2016-05-12 22:43   ` Brian Norris
2016-05-12 22:43   ` Brian Norris
2016-05-13 22:26   ` Doug Anderson
2016-05-13 22:26     ` Doug Anderson
2016-06-16 23:37   ` Heiko Stuebner
2016-06-16 23:37     ` Heiko Stuebner
     [not found]   ` <1463092986-61777-4-git-send-email-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-06-20 13:12     ` Kishon Vijay Abraham I
2016-06-20 13:12       ` Kishon Vijay Abraham I
2016-06-20 13:12       ` Kishon Vijay Abraham I
2016-05-13 22:01 ` [PATCH 1/4] phy: rockchip-emmc: give DLL some extra time to be ready Doug Anderson
2016-05-13 22:01   ` Doug Anderson
2016-06-16 23:35 ` Heiko Stuebner
2016-06-16 23:35   ` Heiko Stuebner

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=20160513210440.GA99074@google.com \
    --to=briannorris@chromium.org \
    --cc=computersforpeace@gmail.com \
    --cc=dianders@chromium.org \
    --cc=heiko@sntech.de \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=shawn.lin@rock-chips.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.