From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Andreas Kemnade <andreas@kemnade.info>,
j.neuschaefer@gmx.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mfd: ntxec: Support for EC in Tolino Shine 2 HD
Date: Mon, 22 Mar 2021 14:59:25 +0000 [thread overview]
Message-ID: <20210322145925.GY2916463@dell> (raw)
In-Reply-To: <20210311184033.GJ4962@sirena.org.uk>
On Thu, 11 Mar 2021, Mark Brown wrote:
> On Wed, Mar 10, 2021 at 09:48:21AM +0000, Lee Jones wrote:
>
> > Could you take a look at this for me please:
>
> > > +static int regmap_ignore_write(void *context,
> > > + unsigned int reg, unsigned int val)
> > > +
> > > +{
> > > + struct regmap *regmap = context;
> > > +
> > > + regmap_write(regmap, reg, val);
> > > +
> > > + return 0;
> > > +}
>
> If there were more users it'd be better to have this in the core so that
> problems we can detect like cache stuff if that's used but if it's just
> one broken device it's probably not worth it, this seems like something
> you'd have to try to end up with and which is going to cause timeout
> problems with a lot of I2C controllers which would tank performance
> enough that people would notice.
So Yoda, is this to go into the core, or stay where it is?
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2021-03-22 15:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 21:29 [PATCH v2] mfd: ntxec: Support for EC in Tolino Shine 2 HD Andreas Kemnade
2021-03-08 22:07 ` Jonathan Neuschäfer
2021-03-10 9:48 ` Lee Jones
2021-03-11 18:40 ` Mark Brown
2021-03-22 14:59 ` Lee Jones [this message]
2021-03-23 17:11 ` Mark Brown
2021-03-23 17:20 ` Lee Jones
2021-03-23 17:48 ` Mark Brown
2021-03-23 18:52 ` Lee Jones
2021-03-23 19:44 ` Mark Brown
2021-03-10 9:55 ` Lee Jones
2021-03-13 11:17 ` Jonathan Neuschäfer
2021-03-13 15:07 ` Andreas Kemnade
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=20210322145925.GY2916463@dell \
--to=lee.jones@linaro.org \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=j.neuschaefer@gmx.net \
--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