From: Heiko Stuebner <heiko@sntech.de>
To: David Wu <david.wu@rock-chips.com>
Cc: khilman@baylibre.com, rafael.j.wysocki@intel.com, nm@ti.com,
huangtao@rock-chips.com, linux-rockchip@lists.infradead.org,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM / AVS: rockchip-io: add io selectors and supplies for rk3228
Date: Fri, 09 Jun 2017 12:45:46 +0200 [thread overview]
Message-ID: <8439045.hRh8SXquWF@phil> (raw)
In-Reply-To: <1497000974-12696-1-git-send-email-david.wu@rock-chips.com>
Am Freitag, 9. Juni 2017, 17:36:14 CEST schrieb David Wu:
> This adds the necessary data for handling io voltage domains on the rk3228.
>
> Signed-off-by: David Wu <david.wu@rock-chips.com>
matches the manual, so
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PM / AVS: rockchip-io: add io selectors and supplies for rk3228
Date: Fri, 09 Jun 2017 12:45:46 +0200 [thread overview]
Message-ID: <8439045.hRh8SXquWF@phil> (raw)
In-Reply-To: <1497000974-12696-1-git-send-email-david.wu@rock-chips.com>
Am Freitag, 9. Juni 2017, 17:36:14 CEST schrieb David Wu:
> This adds the necessary data for handling io voltage domains on the rk3228.
>
> Signed-off-by: David Wu <david.wu@rock-chips.com>
matches the manual, so
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Heiko
next prev parent reply other threads:[~2017-06-09 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 9:36 [PATCH] PM / AVS: rockchip-io: add io selectors and supplies for rk3228 David Wu
2017-06-09 9:36 ` David Wu
2017-06-09 10:45 ` Heiko Stuebner [this message]
2017-06-09 10:45 ` Heiko Stuebner
2017-06-30 22:02 ` Heiko Stuebner
2017-06-30 22:02 ` Heiko Stuebner
2017-07-01 16:17 ` Rafael J. Wysocki
2017-07-01 16:17 ` Rafael J. Wysocki
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=8439045.hRh8SXquWF@phil \
--to=heiko@sntech.de \
--cc=david.wu@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nm@ti.com \
--cc=rafael.j.wysocki@intel.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.