All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: broonie@kernel.org, lee.jones@linaro.org, cw00.choi@samsung.com
Cc: myungjoo.ham@samsung.com, lgirdwood@gmail.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@opensource.wolfsonmicro.com
Subject: [PATCH 0/3] Split Arizona DT bindings between subsystems
Date: Wed, 14 Oct 2015 15:12:21 +0100	[thread overview]
Message-ID: <1444831944-4655-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> (raw)

As discussed the Arizona device tree bindings documentation
will be split up into a seperate document holding properties
specific to each subsystem.

This series factors out the regulator and extcon
bindings. It will probably make sense to split out a GPIO
binding document as well but at the moment the only property
here is the gpio-defaults which are still handled in the MFD
driver and probably require significantly more thought to
split out.

Thanks,
Charles

Charles Keepax (3):
  extcon: arizona: Add extcon specific device tree binding document
  regulator: arizona: Add regulator specific device tree binding
    document
  mfd: arizona: Remove bindings covered in new subsystem specific docs

 .../devicetree/bindings/extcon/extcon-arizona.txt  |   15 +++++++++
 Documentation/devicetree/bindings/mfd/arizona.txt  |   30 ++---------------
 .../bindings/regulator/arizona-regulator.txt       |   34 ++++++++++++++++++++
 MAINTAINERS                                        |    3 ++
 4 files changed, 55 insertions(+), 27 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/extcon/extcon-arizona.txt
 create mode 100644 Documentation/devicetree/bindings/regulator/arizona-regulator.txt

-- 
1.7.2.5

WARNING: multiple messages have this Message-ID (diff)
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: <broonie@kernel.org>, <lee.jones@linaro.org>, <cw00.choi@samsung.com>
Cc: <myungjoo.ham@samsung.com>, <lgirdwood@gmail.com>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<patches@opensource.wolfsonmicro.com>
Subject: [PATCH 0/3] Split Arizona DT bindings between subsystems
Date: Wed, 14 Oct 2015 15:12:21 +0100	[thread overview]
Message-ID: <1444831944-4655-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> (raw)

As discussed the Arizona device tree bindings documentation
will be split up into a seperate document holding properties
specific to each subsystem.

This series factors out the regulator and extcon
bindings. It will probably make sense to split out a GPIO
binding document as well but at the moment the only property
here is the gpio-defaults which are still handled in the MFD
driver and probably require significantly more thought to
split out.

Thanks,
Charles

Charles Keepax (3):
  extcon: arizona: Add extcon specific device tree binding document
  regulator: arizona: Add regulator specific device tree binding
    document
  mfd: arizona: Remove bindings covered in new subsystem specific docs

 .../devicetree/bindings/extcon/extcon-arizona.txt  |   15 +++++++++
 Documentation/devicetree/bindings/mfd/arizona.txt  |   30 ++---------------
 .../bindings/regulator/arizona-regulator.txt       |   34 ++++++++++++++++++++
 MAINTAINERS                                        |    3 ++
 4 files changed, 55 insertions(+), 27 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/extcon/extcon-arizona.txt
 create mode 100644 Documentation/devicetree/bindings/regulator/arizona-regulator.txt

-- 
1.7.2.5


             reply	other threads:[~2015-10-14 14:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 14:12 Charles Keepax [this message]
2015-10-14 14:12 ` [PATCH 0/3] Split Arizona DT bindings between subsystems Charles Keepax
2015-10-14 14:12 ` [PATCH 1/3] extcon: arizona: Add extcon specific device tree binding document Charles Keepax
2015-10-14 14:12   ` Charles Keepax
     [not found]   ` <1444831944-4655-2-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2015-10-15  8:39     ` Chanwoo Choi
2015-10-15  8:39       ` Chanwoo Choi
2015-10-14 14:12 ` [PATCH 2/3] regulator: arizona: Add regulator " Charles Keepax
2015-10-14 14:12   ` Charles Keepax
2015-10-14 14:12 ` [PATCH 3/3] mfd: arizona: Remove bindings covered in new subsystem specific docs Charles Keepax
2015-10-14 14:12   ` Charles Keepax
     [not found]   ` <1444831944-4655-4-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2015-10-15  8:08     ` Lee Jones
2015-10-15  8:08       ` Lee Jones

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=1444831944-4655-1-git-send-email-ckeepax@opensource.wolfsonmicro.com \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=broonie@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=patches@opensource.wolfsonmicro.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.