From: Mark Brown <broonie@kernel.org>
To: Markus Pargmann <mpa@pengutronix.de>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
Irina Tirdea <irina.tirdea@intel.com>
Subject: Re: [PATCH v2 1/4] regmap: Introduce max_raw_read/write for regmap_bulk_read/write
Date: Fri, 21 Aug 2015 09:47:09 -0700 [thread overview]
Message-ID: <20150821164709.GF12027@sirena.org.uk> (raw)
In-Reply-To: <1440064807-26346-2-git-send-email-mpa@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
On Thu, Aug 20, 2015 at 12:00:04PM +0200, Markus Pargmann wrote:
> There are some buses which have a limit on the maximum number of bytes
> that can be send/received. An example for this is
> I2C_FUNC_SMBUS_I2C_BLOCK which does not support any reads/writes of more
> than 32 bytes. The regmap_bulk operations should still be able to
> utilize the full 32 bytes in this case.
This doesn't seem to apply against current code, can you please check
and resend?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-08-21 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 10:00 [PATCH v2 0/4] regmap: i2c block support Markus Pargmann
2015-08-20 10:00 ` [PATCH v2 1/4] regmap: Introduce max_raw_read/write for regmap_bulk_read/write Markus Pargmann
2015-08-21 16:47 ` Mark Brown [this message]
2015-08-20 10:00 ` [PATCH v2 2/4] regmap: regmap max_raw_read/write getter functions Markus Pargmann
2015-08-20 10:00 ` [PATCH v2 3/4] regmap: Add raw_write/read checks for max_raw_write/read sizes Markus Pargmann
2015-08-20 10:00 ` [PATCH v2 4/4] regmap-i2c: Add smbus i2c block support Markus Pargmann
2015-08-20 23:46 ` [PATCH v2 0/4] regmap: " Mark Brown
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=20150821164709.GF12027@sirena.org.uk \
--to=broonie@kernel.org \
--cc=irina.tirdea@intel.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpa@pengutronix.de \
--cc=wsa@the-dreams.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
all inboxes | Powered by JetHome®