From: Jonathan Cameron <jic23@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Marco Felsch <m.felsch@pengutronix.de>,
lars@metafoo.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
hns@goldelico.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [PATCH] dt-bindings: iio: gyroscope: bosch,bmg160: add spi-max-frequency binding
Date: Tue, 27 Feb 2024 19:23:08 +0000 [thread overview]
Message-ID: <20240227192308.52fd3a57@jic23-huawei> (raw)
In-Reply-To: <29cc9d21-6fb5-40fc-abba-c0913cd175af@linaro.org>
On Mon, 26 Feb 2024 14:18:00 +0100
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> On 26/02/2024 13:40, Marco Felsch wrote:
> > On 24-02-26, Krzysztof Kozlowski wrote:
> >> On 21/02/2024 18:43, Marco Felsch wrote:
> >>> Make use of the common spi-peripheral-props.yaml to pull in the common
> >>> spi device properties and limit the spi-max-frequency to 10 MHz as this
> >>> is the max. frequency if VDDIO >= 1.62V.
> >>
> >> The example uses i2c, so I would expect to see in commit msg explanation
> >> which devices are SPI devices.
> >
> > All listed devices can either operate in I2C or in SPI mode.
>
> Such information in commit msg would be enough.
>
> with the changes:
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> Best regards,
> Krzysztof
>
Added the note whilst applying.
Applied to the togreg branch of iio.git and pushed out (briefly given
timing) as testing for 0-day to take a first look.
Thanks,
Jonathan
next prev parent reply other threads:[~2024-02-27 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 17:43 [PATCH] dt-bindings: iio: gyroscope: bosch,bmg160: add spi-max-frequency binding Marco Felsch
2024-02-26 9:01 ` Krzysztof Kozlowski
2024-02-26 12:40 ` Marco Felsch
2024-02-26 13:18 ` Krzysztof Kozlowski
2024-02-27 19:23 ` Jonathan Cameron [this message]
2024-02-27 21:51 ` Marco Felsch
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=20240227192308.52fd3a57@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=robh+dt@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