From: gregory.clement@free-electrons•com (Gregory CLEMENT)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 3/6] gpio: dt-bindings: Add documentation for gpio controllers on Armada 7K/8K
Date: Wed, 31 May 2017 12:05:49 +0200 [thread overview]
Message-ID: <87fufltk76.fsf@free-electrons.com> (raw)
In-Reply-To: <20170530222907.ysx53p3efyxudyqp@rob-hp-laptop> (Rob Herring's message of "Tue, 30 May 2017 17:29:07 -0500")
Hi Rob,
On mer., mai 31 2017, Rob Herring <robh@kernel•org> wrote:
>>
>> Required properties:
>>
>> -- compatible : Should be "marvell,orion-gpio", "marvell,mv78200-gpio"
>> - or "marvell,armadaxp-gpio". "marvell,orion-gpio" should be used for
>> - Orion, Kirkwood, Dove, Discovery (except MV78200) and Armada
>> - 370. "marvell,mv78200-gpio" should be used for the Discovery
>> - MV78200. "marvel,armadaxp-gpio" should be used for all Armada XP
>> - SoCs (MV78230, MV78260, MV78460).
>> +- compatible : Should be "marvell,orion-gpio", "marvell,mv78200-gpio",
>> + "marvell,armadaxp-gpio" or "marvell,armada-8k-gpio".
>> +
>> + "marvell,orion-gpio" should be used for Orion, Kirkwood, Dove,
>> + Discovery (except MV78200) and Armada 370. "marvell,mv78200-gpio"
>> + should be used for the Discovery MV78200.
>> +
>> + "marvel,armadaxp-gpio" should be used for all Armada XP SoCs
>> + (MV78230, MV78260, MV78460).
>> +
>> + "marvell,armada-8k-gpio" should be used for the Armada 7K and 8K
>> + SoCs (either from AP or CP), see
>> + Documentation/devicetree/bindings/arm/marvell/cp110-system-controller0.txt
>> + and
>> + Documentation/devicetree/bindings/arm/marvell/ap806-system-controller.txt
>> + for specific details about the offset property.
>>
>> - reg: Address and length of the register set for the device. Only one
>> entry is expected, except for the "marvell,armadaxp-gpio" variant
>> for which two entries are expected: one for the general registers,
>> - one for the per-cpu registers.
>> + one for the per-cpu registers. Not used for marvell,armada-8k-gpio.
>
> Why can't use you use reg instead of offset?
I looked for how the other syscon user did, and I found the offset
usage. So I assumed it was the way to do it. But if you wan I can use a
reg property.
Gregory
>
> Rob
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2017-05-31 10:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 16:09 [PATCH 0/6] Extend mvebu gpio driver to support the controllers of the Marvell Armada 7K/8K Gregory CLEMENT
2017-05-19 16:09 ` [PATCH 1/6] gpio: mvebu: sort header include Gregory CLEMENT
2017-05-23 9:15 ` Linus Walleij
2017-05-19 16:09 ` [PATCH 2/6] gpio: mvebu: switch to regmap for register access Gregory CLEMENT
2017-05-23 9:16 ` Linus Walleij
2017-05-19 16:09 ` [PATCH 3/6] gpio: dt-bindings: Add documentation for gpio controllers on Armada 7K/8K Gregory CLEMENT
2017-05-23 9:20 ` Linus Walleij
2017-05-23 13:06 ` Gregory CLEMENT
2017-05-29 8:08 ` Linus Walleij
2017-05-30 22:23 ` Rob Herring
2017-05-31 10:02 ` Gregory CLEMENT
2017-05-31 10:43 ` Michael Turquette
2017-05-31 14:41 ` Gregory CLEMENT
2017-05-30 22:29 ` Rob Herring
2017-05-31 10:05 ` Gregory CLEMENT [this message]
2017-06-01 17:33 ` Gregory CLEMENT
2017-05-19 16:09 ` [PATCH 4/6] gpio: mvebu: allow building driver for " Gregory CLEMENT
2017-05-23 9:21 ` Linus Walleij
2017-05-19 16:09 ` [PATCH 5/6] gpio: mvebu: Add support for the Armada 7K/8K SoCs Gregory CLEMENT
2017-05-19 16:24 ` Russell King - ARM Linux
2017-05-19 16:27 ` Russell King - ARM Linux
2017-05-19 17:05 ` Thomas Petazzoni
2017-05-19 16:09 ` [PATCH 6/6] arm64: dts: marvell: add gpio support for Armada 7K/8K Gregory CLEMENT
2017-05-31 9:16 ` [PATCH 0/6] Extend mvebu gpio driver to support the controllers of the Marvell " Thomas Petazzoni
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=87fufltk76.fsf@free-electrons.com \
--to=gregory.clement@free-electrons$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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