linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Randy Li <ayaka@soulik.info>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk,
	mark.rutland@arm.com
Subject: Re: [PATCH 2/2] ARM: dts: rockchip: add missing regulators for firefly reload board
Date: Thu, 18 Aug 2016 18:47:08 +0200	[thread overview]
Message-ID: <2277495.ctQ1BYPEEl@diego> (raw)
In-Reply-To: <1471453391-10267-3-git-send-email-ayaka@soulik.info>

Am Donnerstag, 18. August 2016, 01:03:11 schrieb Randy Li:
> There are many regulators are missed in previous commit, this
> commit complete most of them. It also fix some mistakes in the
> regulator properties. The VDD_10(REG10) and VCC_18(REG11) had better
> to keep in always-on state, as it is used as the USB PHY supply,
> corretly we have no way to assign power supply to a USB PHY.
> The VCCA_33(REG8) should be enabled or the GMAC won't work.
> 
> It also fix the wrong properties for audio in io-domains, the supply
> connected to APIO4_VDD is different to firefly release version.
> 
> Signed-off-by: Randy Li <ayaka@soulik.info>

applied to my dts32 branch for 4.9


Thanks
Heiko

  reply	other threads:[~2016-08-19  4:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1549971.ctkvOGm2xW@diego>
2016-07-18 15:32 ` [PATCH v2] ARM: dts: add rk3288-firefly-reload Randy Li
2016-07-18 15:32   ` [PATCH] " Randy Li
2016-07-18 19:46     ` Heiko Stübner
2016-08-07  3:40       ` Shawn Lin
2016-08-07 14:44         ` Heiko Stuebner
2016-08-08  2:29           ` Shawn Lin
2016-08-09  9:28           ` 陈豪
2016-08-09 10:02             ` 陈豪
2016-08-09 10:06               ` Randy Li
2016-08-09 10:58                 ` Heiko Stübner
2016-08-10  1:12                   ` Randy Li
2016-08-14 11:27                     ` [PATCH 0/2] ARM: dts: rockchip: correct the regulators in firefly reload Randy Li
2016-08-14 11:27                       ` [PATCH 1/2] ARM: dts: rockchip: remove excess sd properties for " Randy Li
2016-08-14 12:30                         ` Heiko Stuebner
2016-08-14 12:38                           ` ayaka
2016-08-17 14:10                             ` Heiko Stübner
2016-08-17 17:03                               ` [PATCH 0/2 v2] ARM: dts: rockchip: correct the regulators in " Randy Li
2016-08-17 17:03                                 ` [PATCH 1/2] ARM: dts: rockchip: remove excess sd properties for " Randy Li
2016-08-18 13:35                                   ` Heiko Stübner
2016-08-18 14:20                                     ` ayaka
2016-08-17 17:03                                 ` [PATCH 2/2] ARM: dts: rockchip: add missing regulators for firefly reload board Randy Li
2016-08-18 16:47                                   ` Heiko Stübner [this message]
2016-08-14 11:27                       ` Randy Li

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=2277495.ctQ1BYPEEl@diego \
    --to=heiko@sntech.de \
    --cc=ayaka@soulik.info \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).