public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: kishon@ti.com, linux-rockchip@lists.infradead.org,
	linux-kernel@vger.kernel.org, shawn.lin@rock-chips.com,
	ykk@rock-chips.com, devicetree@vger.kernel.org,
	pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org
Subject: Re: [PATCH v2 2/3] phy: rockchip-emmc: should be a child device of the GRF
Date: Fri, 25 Mar 2016 09:51:52 -0500	[thread overview]
Message-ID: <20160325145152.GA32438@rob-hp-laptop> (raw)
In-Reply-To: <1458854943-17388-2-git-send-email-heiko@sntech.de>

On Thu, Mar 24, 2016 at 10:29:02PM +0100, Heiko Stuebner wrote:
> The emmc-phy is fully enclosed in the general register files (GRF).
> Therefore as seen from the device-tree it shouldn't be a separate platform-
> device but instead a sub-device of the GRF - using the simply-mfd mechanism.
> 
> The driver entered the kernel in the current merge-window, so we can still
> adapt the binding without needing a fallback, as the binding hasn't been
> released with a full kernel yet.
> 
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---
> Hi Shawn, Kishon,
> 
> I didn't see this new phy driver until now, so I'd really like to get
> this sorted before the old binding solidifies :-).
> 
> I'll convert the usbphy as well, but that has to have the fallback for
> the old binding, so is not as urgent as these two.
> 
> As mentioned in the patch description above, this is meant as a fixup for
> kernel 4.6.
> 
> 
> changes in v2: drop forgotten rockchip,grf from example
> 
> 
>  .../devicetree/bindings/phy/rockchip-emmc-phy.txt     | 19 ++++++++++++-------
>  drivers/phy/phy-rockchip-emmc.c                       |  5 ++++-
>  2 files changed, 16 insertions(+), 8 deletions(-)

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2016-03-25 14:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 21:29 [PATCH v2 1/3] phy: rockchip-dp: should be a child device of the GRF Heiko Stuebner
2016-03-24 21:29 ` [PATCH v2 2/3] phy: rockchip-emmc: " Heiko Stuebner
2016-03-25 14:51   ` Rob Herring [this message]
2016-03-29  1:53   ` Shawn Lin
2016-03-28 11:31 ` [PATCH v2 1/3] phy: rockchip-dp: " Yakir Yang
     [not found] ` <1458854943-17388-1-git-send-email-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2016-03-24 21:29   ` [PATCH v2 3/3] phy: rockchip-emmc: adapt binding to specifiy register offset and length Heiko Stuebner
     [not found]     ` <1458854943-17388-3-git-send-email-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2016-03-25 14:53       ` Rob Herring
2016-04-13 13:01       ` Kishon Vijay Abraham I
     [not found]         ` <570E4328.4050501-l0cyMroinI0@public.gmane.org>
2016-04-13 13:02           ` Kishon Vijay Abraham I
2016-03-25 14:51   ` [PATCH v2 1/3] phy: rockchip-dp: should be a child device of the GRF Rob Herring
2016-04-06 20:38   ` 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=20160325145152.GA32438@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=heiko@sntech.de \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=shawn.lin@rock-chips.com \
    --cc=ykk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox