Hi Simon,
On Thu, Aug 2, 2018 at 2:20 PM, Simon Glass wrote:
> Hi Mario,
>
> On 31 July 2018 at 04:01, Mario Six wrote:
>> The regmap functions currently assume that all register map accesses
>> have a data width of 32 bits, but there are maps that have different
>> widths.
>>
>> To rectify this
Hi Anatolij,
On Thu, Aug 2, 2018 at 12:01 AM, Anatolij Gustschin wrote:
> Hi Mario,
>
> On Tue, 31 Jul 2018 12:01:04 +0200
> Mario Six mario@gdsys.cc wrote:
>
>> The regmap functions currently assume that all register map accesses
>> have a data width of 32 bits, but there are maps that have
Hi Mario,
On 31 July 2018 at 04:01, Mario Six wrote:
> The regmap functions currently assume that all register map accesses
> have a data width of 32 bits, but there are maps that have different
> widths.
>
> To rectify this, implement the regmap_raw_read and regmap_raw_write
> functions from the
Hi Mario,
On Tue, 31 Jul 2018 12:01:04 +0200
Mario Six mario@gdsys.cc wrote:
> The regmap functions currently assume that all register map accesses
> have a data width of 32 bits, but there are maps that have different
> widths.
>
> To rectify this, implement the regmap_raw_read and regmap_r
The regmap functions currently assume that all register map accesses
have a data width of 32 bits, but there are maps that have different
widths.
To rectify this, implement the regmap_raw_read and regmap_raw_write
functions from the Linux kernel API that specify the width of a desired
read or writ
5 matches
Mail list logo