From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"brgl@bgdev.pl" <brgl@bgdev.pl>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>,
"lee.jones@linaro.org" <lee.jones@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: gpio: gpio-mvebu: convert txt binding to YAML
Date: Tue, 10 May 2022 20:55:19 +0000 [thread overview]
Message-ID: <eaea4c27-05b3-d26f-d091-99e07d14aae6@alliedtelesis.co.nz> (raw)
In-Reply-To: <6db35313-5dcd-c9f2-724c-d157a835c9fc@linaro.org>
(sigh resend, Thunderbird decided that this needed html)
On 11/05/22 01:40, Krzysztof Kozlowski wrote:
>> + marvell,pwm-offset:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description: Offset in the register map for the pwm registers (in bytes)
> It's the same as offset. Why allowing both? Isn't one deprecated?
>
This one is in addition to offset. The "offset" is for the gpio
registers "marvell,pwm-offset" is for a separate pwm related register
that is not in the same contiguous block.
next prev parent reply other threads:[~2022-05-10 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 9:44 [PATCH] dt-bindings: gpio: gpio-mvebu: convert txt binding to YAML Chris Packham
2022-05-10 13:40 ` Krzysztof Kozlowski
2022-05-10 20:55 ` Chris Packham [this message]
2022-05-11 7:23 ` Krzysztof Kozlowski
2022-05-10 23:34 ` Chris Packham
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=eaea4c27-05b3-d26f-d091-99e07d14aae6@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).