mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wadim Egorov <w.egorov@phytec.de>
To: Elaine Zhang <zhangqing@rock-chips.com>,
	lee.jones@linaro.org, lgirdwood@gmail.com, broonie@kernel.org
Cc: huangtao@rock-chips.com, xxx@rock-chips.com,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	chenjh@rock-chips.com
Subject: Re: [PATCH v1 0/4] rk808: Add RK805 support
Date: Thu, 9 Mar 2017 11:03:24 +0100	[thread overview]
Message-ID: <0e08f79f-e475-ef1e-5139-4527ca352fe9@phytec.de> (raw)
In-Reply-To: <1489049402-15791-1-git-send-email-zhangqing@rock-chips.com>

Hi Elaine,

you should also add the RK805 to the device tree bindings documentation in

Documentation/devicetree/bindings/mfd/rk808.txt

Regards,
Wadim


Am 09.03.2017 um 09:49 schrieb Elaine Zhang:
> Elaine Zhang (4):
>   mfd: rk808: fix up the chip id get failed
>   linux: mfd: rk808: add rk805 regs addr and ID
>   regulator: rk808: Add regulator driver for RK805
>   mfd: rk808: Add RK805 support
>
>  drivers/clk/Kconfig                 |   4 +-
>  drivers/mfd/Kconfig                 |   4 +-
>  drivers/mfd/rk808.c                 | 130 ++++++++++++++++++++++++++++++++++--
>  drivers/regulator/Kconfig           |   4 +-
>  drivers/regulator/rk808-regulator.c |  66 ++++++++++++++++++
>  drivers/rtc/Kconfig                 |   4 +-
>  include/linux/mfd/rk808.h           |  92 +++++++++++++++++++++++++
>  7 files changed, 290 insertions(+), 14 deletions(-)
>

      parent reply	other threads:[~2017-03-09 10:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09  8:49 Elaine Zhang
2017-03-09  8:49 ` [PATCH v1 1/4] mfd: rk808: fix up the chip id get failed Elaine Zhang
2017-03-09  8:50 ` [PATCH v1 2/4] linux: mfd: rk808: add rk805 regs addr and ID Elaine Zhang
2017-03-09  8:50 ` [PATCH v1 3/4] regulator: rk808: Add regulator driver for RK805 Elaine Zhang
2017-03-09  8:50 ` [PATCH v1 4/4] mfd: rk808: Add RK805 support Elaine Zhang
2017-03-09 10:03 ` Wadim Egorov [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=0e08f79f-e475-ef1e-5139-4527ca352fe9@phytec.de \
    --to=w.egorov@phytec.de \
    --cc=broonie@kernel.org \
    --cc=chenjh@rock-chips.com \
    --cc=huangtao@rock-chips.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=xxx@rock-chips.com \
    --cc=zhangqing@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

all inboxes | Powered by JetHome®