All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Shawn Lin <shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Brian Norris
	<briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: add aspm-no-l0s for rk3399
Date: Fri, 13 Jan 2017 12:05:17 +0100	[thread overview]
Message-ID: <47885028.4qY5GHWHE7@phil> (raw)
In-Reply-To: <1481881357-1793-2-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>

Am Freitag, 16. Dezember 2016, 17:42:37 CET schrieb Shawn Lin:
> Per the discussion of bug fix[1], we now actually
> leaves the default clock choice for pcie phy is
> derived from 24MHz OSC to guarantee the least BER.
> So let's add aspm-no-l0s here and folks could delete
> this property from their dts.
> 
> [1] https://patchwork.kernel.org/patch/9470519/
> Signed-off-by: Shawn Lin <shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>

applied for 4.11

Thanks
Heiko

  parent reply	other threads:[~2017-01-13 11:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16  9:42 [PATCH 1/2] arm64: dts: rockchip: add max-link-speed for rk3399 Shawn Lin
     [not found] ` <1481881357-1793-1-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-12-16  9:42   ` [PATCH 2/2] arm64: dts: rockchip: add aspm-no-l0s " Shawn Lin
     [not found]     ` <1481881357-1793-2-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-01-06  9:13       ` Heiko Stuebner
2017-01-13  1:43         ` Shawn Lin
2017-01-13 11:05       ` Heiko Stuebner [this message]
2017-01-06  9:11   ` [PATCH 1/2] arm64: dts: rockchip: add max-link-speed " 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=47885028.4qY5GHWHE7@phil \
    --to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
    --cc=briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
    /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.