mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eddie James <eajames@linux.ibm.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-fsi@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	gregkh@linuxfoundation.org, rafael@kernel.org, jk@ozlabs.org,
	joel@jms.id.au, alistair@popple.id.au
Subject: Re: [PATCH v2 1/5] regmap: Add FSI bus support
Date: Thu, 3 Nov 2022 09:59:39 -0500	[thread overview]
Message-ID: <814737a6-384b-23ec-1f5c-ddeb08f3758e@linux.ibm.com> (raw)
In-Reply-To: <Y2PWNYfu9l5rRznX@sirena.org.uk>


On 11/3/22 09:54, Mark Brown wrote:
> On Wed, Nov 02, 2022 at 03:51:44PM -0500, Eddie James wrote:
>> Add regmap support for the FSI bus.
>>
>> Signed-off-by: Eddie James <eajames@linux.ibm.com>
>> ---
>>   drivers/base/regmap/Kconfig      |   6 +-
>>   drivers/base/regmap/Makefile     |   1 +
>>   drivers/base/regmap/regmap-fsi.c | 231 +++++++++++++++++++++++++++++++
>>   include/linux/regmap.h           |  37 +++++
> I thought the plan was to put this in the MFD since that's the only
> user?


For the I2C responder regmap, yes, that's what I've done. The FSI regmap 
could be used anywhere in the future. We could switch a number of 
drivers to use the FSI regmap if desired, so I feel it's worth it to put 
it in the regmap properly.


Thanks,

Eddie



  reply	other threads:[~2022-11-03 15:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 20:51 [PATCH v2 0/5] fsi: Add regmap and refactor sbefifo Eddie James
2022-11-02 20:51 ` [PATCH v2 1/5] regmap: Add FSI bus support Eddie James
2022-11-03 14:54   ` Mark Brown
2022-11-03 14:59     ` Eddie James [this message]
2022-11-02 20:51 ` [PATCH v2 2/5] drivers: fsi: Add I2C Responder driver Eddie James
2022-11-02 20:51 ` [PATCH v2 3/5] drivers: fsi: Rename sbefifo and occ sources Eddie James
2022-11-02 20:51 ` [PATCH v2 4/5] drivers: fsi: separate char device code for occ and sbefifo Eddie James
2022-11-02 20:51 ` [PATCH v2 5/5] drivers: fsi: occ and sbefifo refactor Eddie James
2022-11-25 21:28 ` (subset) [PATCH v2 0/5] fsi: Add regmap and refactor sbefifo Mark Brown
2023-01-19 17:48 ` Eddie James

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=814737a6-384b-23ec-1f5c-ddeb08f3758e@linux.ibm.com \
    --to=eajames@linux.ibm.com \
    --cc=alistair@popple.id.au \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jk@ozlabs.org \
    --cc=joel@jms.id.au \
    --cc=linux-fsi@lists.ozlabs.org \
    --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
Powered by JetHome