From: Mark Brown <broonie@kernel.org>
To: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Wolfram Sang <wsa@the-dreams.de>, Dave Airlie <airlied@linux.ie>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
Chris Paterson <Chris.Paterson2@renesas.com>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
Biju Das <biju.das@bp.renesas.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Peter Rosin <peda@axentia.se>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [RFC] drm/bridge/sii902x: Fix EDID readback
Date: Thu, 1 Nov 2018 11:21:17 +0000 [thread overview]
Message-ID: <20181101112117.GA6425@sirena.org.uk> (raw)
In-Reply-To: <TY1PR01MB177051AC6C2B556E32AC08AEC0CD0@TY1PR01MB1770.jpnprd01.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 819 bytes --]
On Wed, Oct 31, 2018 at 04:55:53PM +0000, Fabrizio Castro wrote:
> Having the option of using "unlocked" flavours of reads and writes
> is what we need here, but looking at drivers/base/regmap/regmap-i2c.c
> I couldn't find anything suitable for my case, maybe Mark could advise
> on this one? I am sure I overlooked something here, is there a better
> way to address this?
As Linus said you can go as far as writing your own read and write
functions if you want to. That seems to be the easiest thing, though I
am suspicous that you're having to use the I2C framework in this way -
it doesn't sound terribly clever. You could I guess also just have a
custom function for whatever register is doing all this stuff that just
ignores regmap and bodge things that way while using regmap as normal
for everything else.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-11-01 11:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 12:57 [RFC] drm/bridge/sii902x: Fix EDID readback Fabrizio Castro
2018-10-31 16:07 ` Linus Walleij
2018-10-31 16:55 ` Fabrizio Castro
2018-10-31 20:36 ` Peter Rosin
2018-11-01 11:04 ` Fabrizio Castro
2018-11-01 15:19 ` Peter Rosin
2018-11-01 16:04 ` Fabrizio Castro
2018-11-01 16:47 ` Peter Rosin
2018-11-01 17:32 ` Fabrizio Castro
2018-11-02 8:53 ` Peter Rosin
2018-11-02 12:07 ` Fabrizio Castro
2018-11-01 11:21 ` Mark Brown [this message]
2018-11-02 12:05 ` Fabrizio Castro
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=20181101112117.GA6425@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=biju.das@bp.renesas.com \
--cc=boris.brezillon@free-electrons.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=peda@axentia.se \
--cc=wsa@the-dreams.de \
/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