mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrey.smirnov@convergeddevices.net>
To: <broonie@opensource.wolfsonmicro.com>
Cc: Andrey Smirnov <andrey.smirnov@convergeddevices.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [RFC] regmap: Add no-"bus" configuration possibility
Date: Tue, 13 Nov 2012 16:37:20 -0800	[thread overview]
Message-ID: <50A2E7C0.6080501@convergeddevices.net> (raw)
In-Reply-To: <1351988297-16145-1-git-send-email-andrey.smirnov@convergeddevices.net>

On 11/03/2012 05:18 PM, Andrey Smirnov wrote:
> This patch proposes extension to the API that was suggested by Mark in
> the following thread:
> http://article.gmane.org/gmane.linux.kernel/1383734
>
> The idea behind extensions is to allow the devices that expose some
> register-like interface but whose protocol for reading or writing
> those registers could not be simplified to serialized bytestream
> writes to be used within 'regmap' framework
>
> This patch adds two callbacks to the 'regmap' configuration which user
> is expected to set with their implementation of read and write
> functionality for the device.
>
> I am not very well versed with the code of the remap framework so I
> apologize if my proposal has some glaring mistakes and I would
> welcome any suggestion or criticism on how to either improve the code
> or implement the proposal in a better way.
>
> This commit has only purpose of illustrating the proposed extension of
> the 'regmap' API. It has never been compiled or tested.

Mark, did you by any chance had a time to look at this RFC?



  reply	other threads:[~2012-11-14  0:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-04  0:18 Andrey Smirnov
2012-11-14  0:37 ` Andrey Smirnov [this message]
2012-11-14  2:19   ` Mark Brown
2012-11-20 11:08 ` 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=50A2E7C0.6080501@convergeddevices.net \
    --to=andrey.smirnov@convergeddevices.net \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.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

Powered by JetHome