linux-kernel - regmap for i2c pages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJ+vNU1TOOSf-PoXw1oGTVhGNp2w=X2KAmpYtT8c32GRju2kEQ@mail.gmail.com>
Date:   Thu, 1 Jun 2017 23:37:43 -0700
From:   Tim Harvey <tharvey@...eworks.com>
To:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        linux-media <linux-media@...r.kernel.org>,
        Mark Brown <broonie@...nel.org>
Subject: regmap for i2c pages

I'm working on a driver for an i2c based media controller device that
uses pages. By that I mean there are several pages of 8bit registers
and a page-select register that holds the current page. Multiple
accesses to the same page can occur without writing to this page
register but if you want to access another page you need to update it.

I believe this is a very common i2c register mechanism but I'm not
clear what the best way to use i2c regmap for this is. I'm reading
that regmap 'handles register pages' but I'm not clear if that's the
same thing I'm looking for. If so, are there any examples of this? I
see several i2c drivers that reference pages but it looks to me that
each page is a different i2c slave address which is something
different.

Regards,

Tim