On Sun, Mar 24, 2019 at 10:32:03PM +0200, Vladimir Oltean wrote:
> I didn't want to pollute LKML with the entire driver patchset from the
> get-go, just receive some initial feedback from netdev first (hence the
> RFC).
> How should I proceed? Should I resend just this patch to LKML, or a v2
> patc
On 3/24/19 9:02 PM, Richard Cochran wrote:
On Sun, Mar 24, 2019 at 05:23:34AM +0200, Vladimir Oltean wrote:
This provides an unified API for accessing register bit fields
regardless of memory layout. The basic unit of data for these API
functions is the u64. The process of transforming an u64 fr
On Sun, Mar 24, 2019 at 05:23:34AM +0200, Vladimir Oltean wrote:
> This provides an unified API for accessing register bit fields
> regardless of memory layout. The basic unit of data for these API
> functions is the u64. The process of transforming an u64 from native CPU
> encoding into the periph
This provides an unified API for accessing register bit fields
regardless of memory layout. The basic unit of data for these API
functions is the u64. The process of transforming an u64 from native CPU
encoding into the peripheral's encoding is called 'pack', and
transforming it from peripheral to
