From: Marek Vasut <marex@denx.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Brown <broonie@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH 1/3] regmap: Re-introduce bulk read support check in regmap_bulk_read()
Date: Sun, 19 Jun 2022 00:58:02 +0200 [thread overview]
Message-ID: <ddbb74c0-6a28-7a1a-83a7-ed8e39d0259e@denx.de> (raw)
In-Reply-To: <20220616073435.1988219-2-javierm@redhat.com>
On 6/16/22 09:34, Javier Martinez Canillas wrote:
> Support for drivers to define bulk read/write callbacks in regmap_config
> was introduced by the commit d77e74561368 ("regmap: Add bulk read/write
> callbacks into regmap_config"), but this commit wrongly dropped a check
> in regmap_bulk_read() to determine whether bulk reads can be done or not.
>
> Before that commit, it was checked if map->bus was set. Now has to check
> if a map->read callback has been set.
>
> Fixes: d77e74561368 ("regmap: Add bulk read/write callbacks into regmap_config")
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
Reviewed-by: Marek Vasut <marex@denx.de>
next prev parent reply other threads:[~2022-06-18 23:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 7:34 [PATCH 0/3] remap: Some fixes for bulk read/write callbacks in regmap_config support Javier Martinez Canillas
2022-06-16 7:34 ` [PATCH 1/3] regmap: Re-introduce bulk read support check in regmap_bulk_read() Javier Martinez Canillas
2022-06-18 22:58 ` Marek Vasut [this message]
2022-06-16 7:34 ` [PATCH 2/3] regmap: Make regmap_noinc_read() return -ENOTSUPP if map->read isn't set Javier Martinez Canillas
2022-06-18 22:58 ` Marek Vasut
2022-06-16 7:34 ` [PATCH 3/3] regmap: Wire up regmap_config provided bulk write in missed functions Javier Martinez Canillas
2022-06-18 23:02 ` Marek Vasut
2022-06-20 15:40 ` [PATCH 0/3] remap: Some fixes for bulk read/write callbacks in regmap_config support 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=ddbb74c0-6a28-7a1a-83a7-ed8e39d0259e@denx.de \
--to=marex@denx.de \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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
all inboxes | Powered by JetHome®