Currently the fsp_table must be set manually within the 'struct
dram_timing_info'. Since the 'struct fsp_msg' already has all
information needed for the fsp_table we can use it to set it
automatically. This approach is less error-prone and avoids information
duplication.
Signed-off-by: Marco
Barebox now have the support to write the fsp_table entries
automatically based on fsp_msg.drata information. Remove the fsp_table
entry and let the common code do the rest for us.
Signed-off-by: Marco Felsch
---
arch/arm/boards/mnt-reform/lpddr4-timing.c | 1 -
Hi Sascha,
On 9/21/22 14:21, Sascha Hauer wrote:
> On Wed, Sep 21, 2022 at 01:57:25PM +0200, Michael Riesch wrote:
>> Hi Sascha,
>>
>> On 9/21/22 11:17, Sascha Hauer wrote:
>>> On Mon, Sep 19, 2022 at 01:39:47PM +0200, Michael Riesch wrote:
After the removal of the IO domain configuration
On Wed, Sep 21, 2022 at 01:57:25PM +0200, Michael Riesch wrote:
> Hi Sascha,
>
> On 9/21/22 11:17, Sascha Hauer wrote:
> > On Mon, Sep 19, 2022 at 01:39:47PM +0200, Michael Riesch wrote:
> >> After the removal of the IO domain configuration code, the low-level
> >> initialization is the same for
Hi Sascha,
On 9/21/22 11:17, Sascha Hauer wrote:
> On Mon, Sep 19, 2022 at 01:39:47PM +0200, Michael Riesch wrote:
>> After the removal of the IO domain configuration code, the low-level
>> initialization is the same for all RK356x boards. Add a common
>> method rk3568_start to remove this code
Hi Sascha,
On 9/21/22 11:46, Sascha Hauer wrote:
> On Mon, Sep 19, 2022 at 01:39:42PM +0200, Michael Riesch wrote:
>> The IO domains in Rockchip SoCs need to be configured to match the
>> corresponding bank voltage. In Linux this is achieved by means of a
>> platform driver that reads the voltage
On Mon, Sep 19, 2022 at 01:39:42PM +0200, Michael Riesch wrote:
> The IO domains in Rockchip SoCs need to be configured to match the
> corresponding bank voltage. In Linux this is achieved by means of a
> platform driver that reads the voltage value of the supplies and
> configures the bits in the
Hi Michael,
On 9/21/22 09:57, Michael Tretter wrote:
> On Wed, 21 Sep 2022 08:55:12 +0200, Michael Riesch wrote:
>> On 9/5/22 12:07, Michael Riesch wrote:
>>> Propagate any error from of_overlay_apply_symbols and let the user
>>> know if the provided overlay is not applicable.
>>>
>>>
On Mon, Sep 19, 2022 at 01:39:47PM +0200, Michael Riesch wrote:
> After the removal of the IO domain configuration code, the low-level
> initialization is the same for all RK356x boards. Add a common
> method rk3568_start to remove this code duplication.
>
> Signed-off-by: Michael Riesch
> ---
>
Global pointers may only be accessed after setup_c() has been called.
In pine-quartz64 and the Radxa Rock3 board the device tree pointer has
been initialized earlier. As a result the pointer points to the address
the device tree would be placed when the binary would run from 0x0. For
some reason
On Wed, 21 Sep 2022 08:55:12 +0200, Michael Riesch wrote:
> On 9/5/22 12:07, Michael Riesch wrote:
> > Propagate any error from of_overlay_apply_symbols and let the user
> > know if the provided overlay is not applicable.
> >
> > Signed-off-by: Michael Riesch
> > ---
> > drivers/of/overlay.c |
Hi all,
On 9/5/22 12:07, Michael Riesch wrote:
> Propagate any error from of_overlay_apply_symbols and let the user
> know if the provided overlay is not applicable.
>
> Signed-off-by: Michael Riesch
> ---
> drivers/of/overlay.c | 14 +-
> 1 file changed, 9 insertions(+), 5
12 matches
Mail list logo
