From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
- <patches@opensource.cirrus.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH] dt-bindings: mfd: wlf,arizona: Add spi-max-frequency
Date: Wed, 27 Apr 2022 12:58:01 +0000 [thread overview]
Message-ID: <20220427125801.GC38351@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <20220427122143.GB38351@ediswmail.ad.cirrus.com>
On Wed, Apr 27, 2022 at 12:21:43PM +0000, Charles Keepax wrote:
> On Wed, Apr 27, 2022 at 08:51:02AM +0200, Krzysztof Kozlowski wrote:
> > The Wolfson Microelectronics Arizona audio can be connected via SPI bus
> > (e.g. WM5110 on Exynos5433 TM2 board), so allow spi-max-frequency
> > property.
> >
> > Reported-by: Rob Herring <robh@kernel.org>
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > ---
>
> Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
>
Apologies but looking at this again I can't quite see why this is
necessary. The Arizona schema should allow properties that arn't
specified. Do you have an example of what failed to warrant this?
Thanks,
Charles
next prev parent reply other threads:[~2022-04-27 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 6:51 [PATCH] dt-bindings: mfd: wlf,arizona: Add spi-max-frequency Krzysztof Kozlowski
2022-04-27 12:21 ` Charles Keepax
2022-04-27 12:58 ` Charles Keepax [this message]
2022-04-27 13:49 ` Krzysztof Kozlowski
2022-04-27 14:48 ` Charles Keepax
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=20220427125801.GC38351@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
/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).