All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Shawn Lin <shawn.lin@rock-chips.com>,
	Bjorn Helgaas <bhelgaas@google.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
	Brian Norris <briannorris@chromium.org>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/2] Add new resets for pcie-rockchip
Date: Wed, 09 Nov 2016 01:05:15 +0100	[thread overview]
Message-ID: <3680897.9Plsy7nyC8@phil> (raw)
In-Reply-To: <1477017836-19317-1-git-send-email-shawn.lin@rock-chips.com>

Hi Björn,

Am Freitag, 21. Oktober 2016, 10:43:54 CET schrieb Shawn Lin:
> Hi Bjorn and Heiko,
> 
> Sorry for updating pcie-rockchip so frequently under this development
> cycle. This patch is going to fix a urgent issue of missing control for
> pm_rst, aclk_rst and pclk_rst. These three resets was controlled by rom code
> but now the driver will take over it in order to solve some weird issues
> found by MP test. Thanks to that it is still under MP test internally, so
> the backward compatibility of dtb won't be a big deal.

could you take a look at these patches and maybe think about including them 
still for 4.9?


Thanks
Heiko

      parent reply	other threads:[~2016-11-09  0:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21  2:43 [PATCH 0/2] Add new resets for pcie-rockchip Shawn Lin
2016-10-21  2:43 ` [PATCH 1/2] PCI: rockchip: Add three new resets as required properties Shawn Lin
2016-10-21  2:43   ` Shawn Lin
2016-10-21  7:56   ` Heiko Stuebner
2016-10-21  7:56     ` Heiko Stuebner
2016-10-27 14:54   ` Rob Herring
2016-10-27 14:54     ` Rob Herring
2016-10-21  2:43 ` [PATCH 2/2] arm64: dts: rockchip: add three new resets for rk3399 PCIe controller Shawn Lin
2016-10-21  7:58   ` Heiko Stuebner
2016-10-21  7:58     ` Heiko Stuebner
2016-11-09  0:05 ` Heiko Stuebner [this message]

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=3680897.9Plsy7nyC8@phil \
    --to=heiko@sntech.de \
    --cc=bhelgaas@google.com \
    --cc=briannorris@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.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.