All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: marex@denx.de, maxime@cerno.tech, robert.foss@linaro.org,
	dri-devel@lists.freedesktop.org, tzimmermann@suse.de,
	sam@ravnborg.org, jagan@amarulasolutions.com
Subject: Re: (subset) [PATCH 1/2] [RFC] regmap: Add bulk read/write callbacks into regmap_config
Date: Fri, 6 May 2022 13:42:37 +0100	[thread overview]
Message-ID: <YnUXvXmDgLccTRNP@sirena.org.uk> (raw)
In-Reply-To: <877d6zkjw5.fsf@intel.com>

[-- Attachment #1: Type: text/plain, Size: 997 bytes --]

On Fri, May 06, 2022 at 01:58:18PM +0300, Jani Nikula wrote:

> 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?

Not outside of the source.  I did a presentation at ELC-E ages
ago which you can probably find but I'm not sure how much it
would add.

> 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...

The bus code is generally very thin so you shouldn't need to
worry about what the core is up to much if you just want to
support some bus.  If this is a bus that has registers at
hardware level then looking at something like regmap-sdw.c should
be helpful, for something that's just a bit stream at the bus
level then something like regmap-i3c.c is a simple example.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-05-06 12:42 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
2022-05-06 12:42     ` Mark Brown [this message]
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=YnUXvXmDgLccTRNP@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jagan@amarulasolutions.com \
    --cc=jani.nikula@linux.intel.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.