Re: [PATCH v6 15/22] drivers: use dev_read_addr_index_ptr when cast to pointer

Hi Johan, On Fri, 10 Mar 2023 at 17:37, Simon Glass wrote: > > Hi Johan, > > On Mon, 6 Mar 2023 at 12:32, Johan Jonker wrote: > > > > > > > > On 3/6/23 19:20, Simon Glass wrote: > > > Hi Johan, > > > > > > On Thu, 2 Mar 2023 at 17:15, Johan Jonker wrote: > > >> > > >> The fdt_addr_t and phys_ad

Re: [PATCH v6 15/22] drivers: use dev_read_addr_index_ptr when cast to pointer

Hi Johan, On Mon, 6 Mar 2023 at 12:32, Johan Jonker wrote: > > > > On 3/6/23 19:20, Simon Glass wrote: > > Hi Johan, > > > > On Thu, 2 Mar 2023 at 17:15, Johan Jonker wrote: > >> > >> The fdt_addr_t and phys_addr_t size have been decoupled. A 32bit CPU > >> can expect 64-bit data from the device

Re: [PATCH v6 15/22] drivers: use dev_read_addr_index_ptr when cast to pointer

On 3/6/23 19:20, Simon Glass wrote: > Hi Johan, > > On Thu, 2 Mar 2023 at 17:15, Johan Jonker wrote: >> >> The fdt_addr_t and phys_addr_t size have been decoupled. A 32bit CPU >> can expect 64-bit data from the device tree parser, so use > > Why is that? It seems quite inefficient. 1: === Bec

Re: [PATCH v6 15/22] drivers: use dev_read_addr_index_ptr when cast to pointer

Hi Johan, On Thu, 2 Mar 2023 at 17:15, Johan Jonker wrote: > > The fdt_addr_t and phys_addr_t size have been decoupled. A 32bit CPU > can expect 64-bit data from the device tree parser, so use Why is that? It seems quite inefficient. > dev_read_addr_index_ptr instead of the dev_read_addr_index

[PATCH v6 15/22] drivers: use dev_read_addr_index_ptr when cast to pointer

The fdt_addr_t and phys_addr_t size have been decoupled. A 32bit CPU can expect 64-bit data from the device tree parser, so use dev_read_addr_index_ptr instead of the dev_read_addr_index function in the various files in the drivers directory that cast to a pointer. Signed-off-by: Johan Jonker Rev