From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
marex@denx.de, dri-devel@lists.freedesktop.org
Cc: tzimmermann@suse.de, sam@ravnborg.org,
jagan@amarulasolutions.com, robert.foss@linaro.org,
maxime@cerno.tech
Subject: Re: (subset) [PATCH 1/2] [RFC] regmap: Add bulk read/write callbacks into regmap_config
Date: Fri, 06 May 2022 13:58:18 +0300 [thread overview]
Message-ID: <877d6zkjw5.fsf@intel.com> (raw)
In-Reply-To: <165176353878.543269.16463883419414078766.b4-ty@kernel.org>
On Thu, 05 May 2022, Mark Brown <broonie@kernel.org> wrote:
> On Sat, 30 Apr 2022 04:51:44 +0200, Marek Vasut wrote:
>> Currently the regmap_config structure only allows the user to implement
>> single element register read/write using .reg_read/.reg_write callbacks.
>> The regmap_bus already implements bulk counterparts of both, and is being
>> misused as a workaround for the missing bulk read/write callbacks in
>> regmap_config by a couple of drivers. To stop this misuse, add the bulk
>> read/write callbacks to regmap_config and call them from the regmap core
>> code.
>>
>> [...]
Hey Mark, sorry for hijacking the thread a bit. regmap.h seems to have
comprehensive API documentation, but there's very little in terms of
higher level documentation that I could find. Is there any?
I've been toying with the idea of adding a regmap based interface for
accessing Display Port DPCD registers, with caching, and regmap seems
like it's got the kitchen sink but I find it a bit difficult to
navigate...
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-05-06 10:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 2:51 [PATCH 1/2] [RFC] regmap: Add bulk read/write callbacks into regmap_config Marek Vasut
2022-04-30 2:51 ` [PATCH 2/2] [RFC] drm: bridge: icn6211: Convert to regmap_config bulk read/write Marek Vasut
2022-05-05 15:12 ` (subset) [PATCH 1/2] [RFC] regmap: Add bulk read/write callbacks into regmap_config Mark Brown
2022-05-05 17:32 ` Marek Vasut
2022-05-05 21:08 ` Mark Brown
2022-05-05 23:55 ` Marek Vasut
2022-05-06 12:48 ` Mark Brown
2022-05-06 10:58 ` Jani Nikula [this message]
2022-05-06 12:42 ` Mark Brown
2022-05-09 13:54 ` Daniel Vetter
2022-05-09 15:26 ` 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=877d6zkjw5.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jagan@amarulasolutions.com \
--cc=marex@denx.de \
--cc=maxime@cerno.tech \
--cc=robert.foss@linaro.org \
--cc=sam@ravnborg.org \
--cc=tzimmermann@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.