public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jon Ringle <jon@ringle.org>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] regmap: Allow installing custom reg_update_bits function
Date: Fri, 2 Oct 2015 18:19:08 +0100	[thread overview]
Message-ID: <20151002171908.GY12635@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.10.1510010826450.21737@jring-w510-7m3g.gridpoint.com>

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

On Thu, Oct 01, 2015 at 08:29:19AM -0400, Jon Ringle wrote:
> On Thu, 1 Oct 2015, Mark Brown wrote:

> > This completely bypasses and therefore breaks the cache infrastructure.

> Right after sending the v2 patch, I realized that calling the 
> custom reg_update_bits would only be applicable for registers that are 
> marked as volatile. Would the following solution be acceptable (it would 

Well, it should still *work* with a cache, though it's certainly true
that it's unlikely to have any performance benefit with cached register
since the read part of the read/modify/write cycle is essentially free 
with the cache.

> also simplify the regmap_update_bits in the encx24j600 driver):

> 	if (regmap_volatile(map, reg) && map->reg_update_bits) {
> 		return map->reg_update_bits(map->bus_context, reg, mask, 
> 		                            val, change, force_write);

> The cache state should not matter for volatile registers, right?

Right.  I see you've sent a new patch already, I'll reply to that after
I've thought about it a little.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2015-10-02 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01  6:33 [PATCH 1/2] regmap: Allow installing custom reg_update_bits function jon
2015-10-01  6:33 ` [PATCH 2/2] net: Microchip encx24j600 driver jon
2015-10-01  6:48   ` kbuild test robot
2015-10-01  7:36   ` kbuild test robot
2015-10-01  7:36   ` [RFC PATCH] net: encx24j600_open() can be static kbuild test robot
2015-10-01  7:40   ` [PATCH 2/2] net: Microchip encx24j600 driver kbuild test robot
2015-10-01  9:44 ` [PATCH 1/2] regmap: Allow installing custom reg_update_bits function Mark Brown
2015-10-01 12:29   ` Jon Ringle
2015-10-02 17:19     ` Mark Brown [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=20151002171908.GY12635@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jon@ringle.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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