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-prev] [day] [month] [year] [list]
Message-ID: <CAEqHmAtD+LUwjxAi23vv1iwrs7pQLPE6SNsAS2OPa6=9HNdYCA@mail.gmail.com>
Date:	Fri, 11 May 2012 16:33:45 +0100
From:	dd diasemi <dd.diasemi@...il.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org,
	Anthony Olech <Anthony.Olech@...semi.com>, gg@...mlogic.co.uk,
	Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH] regmap: Add support for register paging

On Fri, May 11, 2012 at 3:10 PM, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:
> On Fri, May 11, 2012 at 03:55:54PM +0200, dd diasemi wrote:
>> I have more advanced solution, which actually makes register mapping
>> split into virtual address ranges. This may solve many problems,
>> including giving capability to support several indirect register
>> ranges at once.
>> Let me know, what you think about this API?
>
> I think that sounds roughly like what I was thinking of so it's probably
> sensible but obviously it'll depend on the implementation.
I will use current work and add traversing of regmap_range table to
get proper range definition, then use it to do the indirect access,
like paging. Most of the drivers probably will just have one
regmap_range defined for paging or indirect registers to be accessed.
If an accessed register is not matched by any range from the table, it
will be accessed directly (without any paging).

If this is better alternative, I can continue with it. In other case,
I may send you the cleaned-up patch of current solution.

Best Regards,
Krystian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ