From: Mark Brown <broonie@kernel.org>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: linux-iio@vger.kernel.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
jic23@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
Michael Hennerich <michael.hennerich@analog.com>
Subject: Re: [PATCH 1/4][V2] drivers: spi: core: Add optional delay between cs_change transfers
Date: Thu, 18 Jul 2019 13:50:08 +0100 [thread overview]
Message-ID: <20190718125008.GD5761@sirena.org.uk> (raw)
In-Reply-To: <20190717115109.15168-2-alexandru.ardelean@analog.com>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
On Wed, Jul 17, 2019 at 02:51:06PM +0300, Alexandru Ardelean wrote:
> Some devices like the ADIS16460 IMU require a stall period between
> transfers, i.e. between when the CS is de-asserted and re-asserted. The
> default value of 10us is not enough. This change makes the delay
> configurable for when the next CS change goes active.
To repeat my previous feedback:
| This looks like cs_change_delay.
Please use subject lines matching the style for the subsystem. This
makes it easier for people to identify relevant patches.
Please don't ignore review comments, people are generally making them
for a reason and are likely to have the same concerns if issues remain
unaddressed. Having to repeat the same comments can get repetitive and
make people question the value of time spent reviewing. If you disagree
with the review comments that's fine but you need to reply and discuss
your concerns so that the reviewer can understand your decisions.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-18 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 11:51 [PATCH 0/4][V2] iio: imu: Add support for the ADIS16460 IMU Alexandru Ardelean
2019-07-17 11:51 ` [PATCH 1/4][V2] drivers: spi: core: Add optional delay between cs_change transfers Alexandru Ardelean
2019-07-18 12:50 ` Mark Brown [this message]
2019-07-18 13:36 ` Ardelean, Alexandru
2019-07-17 11:51 ` [PATCH 2/4][V2] iio: imu: adis: Add support for SPI transfer cs_change_delay_usecs Alexandru Ardelean
2019-07-17 11:51 ` [PATCH 3/4][V2] iio: imu: Add support for the ADIS16460 IMU Alexandru Ardelean
2019-07-17 11:51 ` [PATCH 4/4][V2] dt-bindings: iio: imu: add bindings for ADIS16460 Alexandru Ardelean
2019-07-19 22:49 ` Rob Herring
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=20190718125008.GD5761@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandru.ardelean@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michael.hennerich@analog.com \
--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;
as well as URLs for NNTP newsgroup(s).