public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: lee.jones@linaro.org, linux-kernel@vger.kernel.org,
	Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH -next] mfd: ntxec: Support for EC in Tolino Shine 2 HD
Date: Sat, 6 Mar 2021 23:06:19 +0100	[thread overview]
Message-ID: <20210306230619.15ae787f@aktux> (raw)
In-Reply-To: <YEPj2ss13w5p+R4C@latitude>

On Sat, 6 Mar 2021 21:19:38 +0100
Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:

[...]
> > > > +	case NTXEC_VERSION_TOLINO_SHINE2:
> > > > +		has_rtc = false;
> > > > +		ec->regmap = devm_regmap_init(ec->dev, NULL,
> > > > +					      ec->regmap,
> > > > +					      &regmap_config_noack);    
> > > 
> > > Ah— A custom regmap stacked on top of the old regmap… I think this
> > > deserves a comment.
> > >   
> > Yes, devm_regmap_init_i2c() sets a different set of callbacks depending
> > on circumstances. Seems to be the easiest way to avoid duplicating too
> > much code. I really hope that there are not so much devices requiring
> > such a dirty stuff that adding such thing to the generic regmap code
> > would be justified.  
> 
> Ok, please add a short comment here or extend the one above the repmap
> config struct, to save interested readers a bit of trouble. I guess "add
> a wrapper" goes in right direction, but it didn't make the stacking
> obvious to me when I first read it.
>

I will wait for some days to see whether anybody chokes on that stack.

Regards,
Andreas

      reply	other threads:[~2021-03-06 22:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06 18:13 [PATCH -next] mfd: ntxec: Support for EC in Tolino Shine 2 HD Andreas Kemnade
2021-03-06 19:14 ` Jonathan Neuschäfer
2021-03-06 19:42   ` Andreas Kemnade
2021-03-06 20:19     ` Jonathan Neuschäfer
2021-03-06 22:06       ` Andreas Kemnade [this message]

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=20210306230619.15ae787f@aktux \
    --to=andreas@kemnade.info \
    --cc=broonie@kernel.org \
    --cc=j.neuschaefer@gmx.net \
    --cc=lee.jones@linaro.org \
    --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