On 28.05.20 08:12, Kuldeep Singh wrote:
> Current PFE firmware access spi-nor memory directly. New spi-mem
> framework does not support direct memory access. So, let's use
> spi_flash_read API to access memory instead of directly using it.
>
> Signed-off-by: Kuldeep Singh
> Reviewed-by: Frieder S
On 09.04.20 10:44, Ye Li wrote:
> The FIT config node has reversed ATF and u-boot: ATF is set to
> firmware but u-boot is set to loadable.
> This script can work previously because spl fit driver wrongly
> appends fdt to all loadable images. With the issue fixed, the u-boot
> in loadable does not h
On 17.04.20 17:42, Joel Johnson wrote:
> Two nearly concurrent commits (d4d65e112 and bcee8d676) added a
> SPL_DM_GPIO symbol. Resolve the duplication in favor of the version
> in drivers/gpio/Kconfig.
>
> Signed-off-by: Joel Johnson
Reviewed-by: Frieder Schrempf
>
> ---
>
> common/spl/Kco
On 08.04.20 17:31, Tim Harvey wrote:
[...]
>>
>> In my case I'm loading a FIT image, so things are a bit different.
>> Where are you loading the image to?
>>
>> I have the following line in mx8mm_usb_sdp_spl.conf to load my FIT image
>> to DDR and jump to it:
>>
>> /path/to/image/u-boot.itb:load 0x
Hi Tim,
On 07.04.20 19:06, Tim Harvey wrote:
> On Mon, Apr 6, 2020 at 2:43 AM Schrempf Frieder
> wrote:
>>
>> Hi Tim,
>>
>> On 01.04.20 19:55, Tim Harvey wrote:
>>> Peng,
>>>
>>> It looks like IMX8MM USB support hasn't made it up
Hi Tim,
On 01.04.20 19:55, Tim Harvey wrote:
> Peng,
>
> It looks like IMX8MM USB support hasn't made it upstream yet. Is this
> something your working on?
>
> I'm interested in booting an IMX8MM via SDP.
If I remember correctly, the main issue is that the ci_udc driver is
missing DM support.
On 12.02.20 11:37, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> In order to make it possible to auto select a default entry by
> matching the data of the menu entries by an external matching
> function, we add some helpers and expose the
> menu_set_default_by_item_dat
From: Frieder Schrempf
In order to make it possible to auto select a default entry by
matching the data of the menu entries by an external matching
function, we add some helpers and expose the
menu_set_default_by_item_data_match() function.
Signed-off-by: Frieder Schrempf
---
Changes in v4:
* U
From: Frieder Schrempf
In order to auto-select an option from the pxe boot menu, that
matches the detected board, we check the board model string in the
devicetree and set the default menu selection, if it matches the
label of the menu entry and there is no default selection already
set.
This is
On 06.02.20 18:46, Simon Glass wrote:
> Hi Schrempf,
>
> On Thu, 6 Feb 2020 at 02:09, Schrempf Frieder
> wrote:
>>
>> From: Frieder Schrempf
>>
>> In order to make it possible to auto select a default entry by
>> matching the data of the menu entries b
On 06.02.20 18:46, Simon Glass wrote:
> Hi Schrempf,
>
> On Thu, 6 Feb 2020 at 02:09, Schrempf Frieder
> wrote:
>>
>> From: Frieder Schrempf
>>
>> In order to auto-select an option from the pxe boot menu, that
>> matches the detected board, we check t
From: Frieder Schrempf
In order to auto-select an option from the pxe boot menu, that
matches the detected board, we check the board model string in the
devicetree and set the default menu selection, if it matches the
label of the menu entry and there is no default selection already
set.
This is
From: Frieder Schrempf
In order to make it possible to auto select a default entry by
matching the data of the menu entries by an external matching
function, we add some helpers and expose the
menu_set_default_by_item_data_match() function.
Signed-off-by: Frieder Schrempf
---
Changes in v3:
* A
From: Frieder Schrempf
In order to make it possible to auto select a default entry by
matching the data of the menu entries by an external matching
function, we add some helpers and expose the
menu_set_default_by_item_data_match() function.
Signed-off-by: Frieder Schrempf
---
Changes in v2:
* K
From: Frieder Schrempf
In order to auto-select an option from the pxe boot menu, that
matches the detected board, we check the board model string in the
devicetree and set the default menu selection, if it matches the
label of the menu entry and there is no default selection already
set.
This is
On 05.02.20 14:44, Frieder Schrempf wrote:
> Hi Simon,
>
> On 30.12.19 02:21, Simon Glass wrote:
>> Hi Schrempf,
>>
>> On Tue, 10 Dec 2019 at 08:47, Schrempf Frieder
>> wrote:
>>>
>>> From: Frieder Schrempf
>>>
>>> In order
Hi Simon,
On 30.12.19 02:21, Simon Glass wrote:
> Hi Schrempf,
>
> On Tue, 10 Dec 2019 at 08:47, Schrempf Frieder
> wrote:
>>
>> From: Frieder Schrempf
>>
>> In order to iterate over the menu entries and match for a specific
>> name in the pxe b
From: Frieder Schrempf
The current implementation in arch/arm/mach-imx/cpu.c uses non-DM
code to retrieve the core clock frequency. As the root clock is not
listed we currently get:
CPU: Freescale i.MX8MMQ rev1.0 at 0 MHz
Fix this by adding the missing entry, which results in:
CPU: Freesca
On 28.01.20 13:38, Marcel Ziswiler wrote:
> Hi Frieder
>
> On Mon, 2020-01-27 at 09:10 +, Schrempf Frieder wrote:
>> Hi,
>>
>> On 26.01.20 04:55, Marcel Ziswiler wrote:
>>> From: Max Krummenacher
>>>
>>> Add alternative UART m
Hi,
On 27.01.20 10:20, Kuldeep Singh wrote:
> Hi Jagan,
>
>> -Original Message-
>> From: Jagan Teki
>> Sent: Monday, January 27, 2020 12:50 PM
>> To: Kuldeep Singh
>> Cc: U-Boot-Denx ; Priyanka Jain
>> ; Ashish Kumar ; Stefan
>> Roese ; S
Hi,
On 26.01.20 04:55, Marcel Ziswiler wrote:
> From: Max Krummenacher
>
> Add alternative UART muxing defines.
>
> Signed-off-by: Max Krummenacher
Patch 1/8 and 2/8 in this series change the pin definitions for the
i.MX8MM so that they deviate from the definitions in the Linux kernel.
As F
On 21.01.20 11:58, Sébastien Szymanski wrote:
> When a firmware file is missing the warning message doesn't indicate the
> firmware file name because '$tmp' var doesn't exist.
> Fix the warning message and while at it reduce the if/else statement.
>
> Signed-off-by: Sébastien Szymanski
Thanks fo
On 13.01.20 10:23, Kuldeep Singh wrote:
> Current PFE firmware access spi-nor memory directly. New spi-mem
> framework does not support direct memory access. So, let's use
> spi_flash_read API to access memory instead of directly using it.
>
> Signed-off-by: Kuldeep Singh
Reviewed-by: Frieder Sc
On 10.01.20 11:58, Kuldeep Singh wrote:
> Hi Frieder,
>
>> -Original Message-----
>> From: Schrempf Frieder
>> Sent: Wednesday, January 8, 2020 2:52 PM
>> To: Kuldeep Singh ; u-boot@lists.denx.de
>> Cc: Joe Hershberger ; Thomas Hebb
>> ; Patrick Dela
On 08.01.20 10:08, Kuldeep Singh wrote:
> Current PFE firmware access spi-nor memory directly. New spi-mem
> framework does not support direct memory access. So, let's use
> spi_flash_read API to access memory instead of directly using it.
>
> Signed-off-by: Kuldeep Singh
> ---
> v3:
> -Replace r
On 08.01.20 05:50, Kuldeep Singh wrote:
> Current PFE firmware access spi-nor memory directly. New spi-mem
> framework does not support direct memory access. So, let's use
> spi_flash_read API to access memory instead of directly using it.
>
> Signed-off-by: Kuldeep Singh
> ---
> v2:
> Add return
Hi Xiaowei,
On 24.12.19 04:01, Xiaowei Bao wrote:
>
>
>> -Original Message-
>> From: Xiaowei Bao
>> Sent: 2019年10月23日 11:26
>> To: Schrempf Frieder ; Lukasz Majewski
>> ; u-boot@lists.denx.de
>> Subject: RE: [U-Boot] [PATCH v5 1/5] spl:
Hi Kuldeep,
On 06.01.20 11:56, Kuldeep Singh wrote:
> Hi Jagan and Vignesh,
>
> Could you please review this driver. Actually, I don't want to miss this
> merge window.
> Moreover, Frieder's suggestions are already incorporated and this version of
> driver is almost identical to linux version a
On 12.12.19 10:16, Kuldeep Singh wrote:
> Enable the config for ls1012ardb as the entry got missed earlier.
>
> Fixes: 8d8ee47e03 ("env: Add CONFIG_SYS_RELOC_GD_ENV_ADDR symbol")
> Signed-off-by: Kuldeep Singh
As far as I know this should have been in v2020.01 as it fixes a
regression introduce
On 11.12.19 12:53, Kuldeep Singh wrote:
> Current PFE firmware access spi-nor memory directly. New spi-mem
> framework does not support direct memory access. So, let's use
> spi_flash_read API to access memory instead of directly using it.
>
> Signed-off-by: Kuldeep Singh
> ---
> drivers/net/pf
On 11.12.19 15:05, Fabio Estevam wrote:
> Hi Peng,
>
> On Wed, Dec 11, 2019 at 11:00 AM Peng Fan wrote:
>
>> We might need to switch upstream ATF, or stick to NXP vendor release one?
>
> I don't have much background about the ATF upstream status on i.MX8 to
> provide an opinion.
>
> Does upstr
Hi Baruch,
On 11.12.19 11:49, Baruch Siach wrote:
> Hi Frieder Schrempf,
>
> On Wed, Dec 11 2019, Schrempf Frieder wrote:
>
>> From: Frieder Schrempf
>>
>> The DDR firmware binaries are not part of the U-Boot source code, so
>> we should look for them in the
Hi Kuldeep,
On 11.12.19 13:23, Kuldeep Singh wrote:
> Hi Frieder,
[...]
>>> Patch 2 adds new qspi driver incorporating spi-mem framework which
>>> is ported version of linux qspi driver. Initial port was done by
>>> Frieder.
>>> Now, no more direct access to spi-nor memory is poss
On 11.10.19 01:00, Soeren Moch wrote:
> Using a MAC address from ROM storage is the normal case for most
> ethernet hardware. Why should we warn about this?
>
> Signed-off-by: Soeren Moch
Some months ago I came up with the very same patch and I currently have
it in my local fork with the descri
From: Frieder Schrempf
The DDR firmware binaries are not part of the U-Boot source code, so
we should look for them in the build directory, where they need to be
copied to before building U-Boot.
The ATF binary is already fetched from the build directory, but the
README files for the i.MX8M EVKs
From: Frieder Schrempf
In cases when the same SPL should run on boards with i.MX8MM, that
differ in DDR configuration, it is necessary to try different
parameters and check if the training done by the firmware suceeds or
not.
Therefore we return the DDR training/initialization success to the
upp
On 10.12.19 16:45, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> In order to auto-select an option from the pxe boot menu, that
> matches the detected board, we check the board model string in the
> devicetree and set the default menu selection, if it matches the
> label
From: Frieder Schrempf
In order to iterate over the menu entries and match for a specific
name in the pxe boot, we need to properly export the needed structs
and functions.
Signed-off-by: Frieder Schrempf
---
common/menu.c | 31 +--
include/menu.h | 34
From: Frieder Schrempf
In order to auto-select an option from the pxe boot menu, that
matches the detected board, we check the board model string in the
devicetree and set the default menu selection, if it matches the
label of the menu entry and there is no default selection already
set.
This is
On 03.12.19 11:56, Kuldeep Singh wrote:
> Hi Frieder,
>
>> -Original Message-----
>> From: Schrempf Frieder
>> Sent: Tuesday, December 3, 2019 2:27 PM
>> To: Kuldeep Singh ; u-boot@lists.denx.de
>> Cc: Priyanka Jain ; ja...@amarulasolutions.com;
&
Hi Ashish,
On 03.12.19 10:44, Frieder Schrempf wrote:
> On 03.12.19 10:33, Ashish Kumar wrote:
>> Hi Frieder,
>>
>>> -Original Message-
>>> From: Schrempf Frieder
>>> Sent: Tuesday, December 3, 2019 2:27 PM
>>> To: Kuldeep Sing
On 03.12.19 10:33, Ashish Kumar wrote:
> Hi Frieder,
>
>> -Original Message-----
>> From: Schrempf Frieder
>> Sent: Tuesday, December 3, 2019 2:27 PM
>> To: Kuldeep Singh ; u-boot@lists.denx.de
>> Cc: Priyanka Jain ; ja...@amarulasolutions.com;
&
On 03.12.19 07:30, Kuldeep Singh wrote:
> Hi Frieder,
>
>> -Original Message-----
>> From: Schrempf Frieder
>> Sent: Monday, December 2, 2019 5:35 PM
>> To: Kuldeep Singh ; u-boot@lists.denx.de
>> Cc: Priyanka Jain ; ja...@amarulasolutions.com;
>> s.
+ Ashish
Hi Kuldeep,
On 29.11.19 06:54, Kuldeep Singh wrote:
> This entire patch series migrate freescale qspi driver to spi-mem framework.
First, thanks for working on this. I have this on my list for quite a
long time, but struggled to find enough time to actually get it done.
>
> Patch 1 r
Hi Simon,
On 07.11.19 17:23, Simon Glass wrote:
> Hi Schrempf,
>
> On Thu, 7 Nov 2019 at 08:15, Schrempf Frieder
> wrote:
>>
>> On 07.11.19 15:02, Bin Meng wrote:
>>> Hi Frieder,
>>>
>>> On Thu, Nov 7, 2019 at 9:28 PM Schrempf Frieder
>&g
On 07.11.19 15:02, Bin Meng wrote:
> Hi Frieder,
>
> On Thu, Nov 7, 2019 at 9:28 PM Schrempf Frieder
> wrote:
>>
>> Hi Bin,
>>
>> On 07.11.19 13:41, Bin Meng wrote:
>>> Hi Schrempf,
>>>
>>> On Thu, Nov 7, 2019 at 12:17 AM Schre
Hi Bin,
On 07.11.19 13:41, Bin Meng wrote:
> Hi Schrempf,
>
> On Thu, Nov 7, 2019 at 12:17 AM Schrempf Frieder
> wrote:
>>
>> Hi,
>>
>> I'm having some trouble using buildman to test the impact of some
>> Kconfig cleanup patches ([1]).
>>
>
On 06.11.19 17:16, Frieder Schrempf wrote:
> Hi,
>
> I'm having some trouble using buildman to test the impact of some
> Kconfig cleanup patches ([1]).
>
> The patches introduce a new CONFIG_SPL_* option and I try to find out
> which defconfigs need to be fixed, by comparing build sizes.
>
> N
Hi,
I'm having some trouble using buildman to test the impact of some
Kconfig cleanup patches ([1]).
The patches introduce a new CONFIG_SPL_* option and I try to find out
which defconfigs need to be fixed, by comparing build sizes.
Now when I added a patch to fix a defconfig I noticed that bui
On 31.10.19 08:57, Jagan Teki wrote:
> Hi Schrempf,
>
> On Thu, Oct 31, 2019 at 1:24 PM Schrempf Frieder
> wrote:
>>
>> Hi Jagan,
>>
>> On 28.10.19 01:46, Tom Rini wrote:
>>> On Sun, Oct 27, 2019 at 05:20:22PM +0530, Jagan Teki wrote:
>>>&g
Hi Jagan,
On 28.10.19 01:46, Tom Rini wrote:
> On Sun, Oct 27, 2019 at 05:20:22PM +0530, Jagan Teki wrote:
>> Hi Tom,
>>
>> On Fri, Oct 25, 2019 at 11:19 PM Tom Rini wrote:
>>>
>>> On Fri, Oct 25, 2019 at 02:08:12PM +0530, Jagan Teki wrote:
>>>
Hi Tom,
Please pull this PR.
>>>
Hi Robert,
On 23.10.19 20:22, Robert Beckett wrote:
> From: Martin Fuzzey
>
> Add a driver for the regulators in the the DA9063 PMIC.
>
> Robert Beckett: move regulator modes to header so board code can set
> modes. Correct mode mask used in ldo_set_mode.
>
> Signed-off-by: Martin Fuzzey
> Si
Hi Robert,
On 23.10.19 20:22, Robert Beckett wrote:
> From: Martin Fuzzey
>
> This adds the basic register access operations and child regulator
> binding (if a regulator driver exists).
>
> Robert Beckett: simplify accesses by using bottom bit of address as
> offset overflow. This avoids the n
On 23.10.19 20:21, Robert Beckett wrote:
> From: Martin Fuzzey
>
> Some PMICs (such as the DA9063) have non-contiguous register maps.
> Attempting to read the non implemented registers returns an error
> rather than a dummy value which causes 'pmic dump' to terminate
> prematurely.
>
> Fix this
On 24.10.19 11:33, Peng Fan wrote:
> Add more clks for fec_mxc according to Linux Kernel 5.4.0-rc1
> drivers/net/ethernet/freescale/fec_main.c.
>
> Since i.MX8MQ not support CLK_CCF, so add a check to restrict
> the code only effect when CONFIG_IMX8M and CONFIG_CLK_CCF both defined.
>
> Signed-of
On 24.10.19 03:09, Peng Fan wrote:
>> Subject: Re: [U-Boot] [PATCH V1 5/6] net: fec_mxc: support i.MX8M with
>> CLK_CCF
>>
>> On 22.10.19 05:30, Peng Fan wrote:
>>> Add more clks for fec_mxc according to Linux Kernel 5.4.0-rc1
>>> drivers/net/ethernet/freescale/fec_main.c.
>>>
>>> Since i.MX8MQ not
On 23.10.19 18:36, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> The 24MHz oscillator clock is referenced by "clock-osc-24m" and not
> "osc_24m".
>
> Signed-off-by: Frieder Schrempf
Just for completeness:
Fixes: f62ec5c4bba2 ("clk: imx: add
From: Frieder Schrempf
The 24MHz oscillator clock is referenced by "clock-osc-24m" and not
"osc_24m".
Signed-off-by: Frieder Schrempf
---
drivers/clk/imx/clk-imx8mm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/imx/clk-imx8mm.c b/drivers/clk/imx/clk-imx8mm.c
On 22.10.19 05:30, Peng Fan wrote:
> Add more clks for fec_mxc according to Linux Kernel 5.4.0-rc1
> drivers/net/ethernet/freescale/fec_main.c.
>
> Since i.MX8MQ not support CLK_CCF, so add a check to restrict
> the code only effect when CONFIG_IMX8M and CONFIG_CLK_CCF both defined.
>
> Signed-of
On 22.10.19 05:29, Peng Fan wrote:
> Make FEC driver could be used by i.MX8M when CONFIG_FEC_MXC defined
> in defconfig.
>
> Signed-off-by: Peng Fan
Reviewed-by: Frieder Schrempf
Tested-by: Frieder Schrempf
> ---
> drivers/net/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
On 22.10.19 05:29, Peng Fan wrote:
> Add set_parent callback, then assigned-clock-parents in dts could
> be work.
>
> Signed-off-by: Peng Fan
Reviewed-by: Frieder Schrempf
Tested-by: Frieder Schrempf
> ---
> drivers/clk/imx/clk-imx8mm.c | 19 +++
> 1 file changed, 19 insert
On 22.10.19 05:29, Peng Fan wrote:
> Add enet ref/timer/PHY_REF/root clk which are required to make enet
> function well.
>
> Signed-off-by: Peng Fan
Reviewed-by: Frieder Schrempf
Tested-by: Frieder Schrempf
> ---
> drivers/clk/imx/clk-imx8mm.c | 27 +++
> 1 file ch
Hi Ashish,
On 22.10.19 18:11, Ashish Kumar wrote:
>
>
>> -Original Message-
>> From: Stefan Roese
>> Sent: Tuesday, October 22, 2019 9:12 PM
>> To: Schrempf Frieder ; Ashish Kumar
>> ; Ye Li ;
>> ja...@amarulasolutions.com
>> Cc: Fabio
From: Frieder Schrempf
Most boards currently use SPI_FLASH_MTD only in U-Boot proper, not in
SPL. They often rely on hacks in the board header files to include
this option conditionally. To be able to fix this, we previously
introduced a separate option SPL_SPI_FLASH_MTD.
Therefore we can now ad
From: Frieder Schrempf
Most boards currently use SPI_FLASH_MTD only in U-Boot proper, not in
SPL. They often rely on hacks in the board header files to include
this option conditionally. To be able to fix this, we previously
introduced a separate option SPL_SPI_FLASH_MTD.
Therefore we can now ad
On 23.10.19 09:09, Jagan Teki wrote:
> On Wed, Oct 23, 2019 at 12:35 PM Schrempf Frieder
> wrote:
>>
>> Hi Jagan,
>>
>> On 22.10.19 20:16, Jagan Teki wrote:
>>> On Sat, Sep 14, 2019 at 4:14 AM Schrempf Frieder
>>> wrote:
>>>>
>
Hi Jagan,
On 22.10.19 20:16, Jagan Teki wrote:
> On Sat, Sep 14, 2019 at 4:14 AM Schrempf Frieder
> wrote:
>>
>> From: Frieder Schrempf
>>
>> Most boards currently use SPI_FLASH_MTD only in U-Boot proper, not in
>> SPL. They often rely on hacks in the b
Hi Jagan,
On 22.10.19 20:10, Jagan Teki wrote:
> On Tue, Oct 22, 2019 at 6:23 PM Schrempf Frieder
> wrote:
>>
>> Hi Jagan,
>>
>> On 17.10.19 08:42, Frieder Schrempf wrote:
>>> Hi Jagan,
>>>
>>> On 16.10.19 18:34, Jagan Teki wrote:
>>
On 22.10.19 15:55, Frieder Schrempf wrote:
> Hi Stefan,
>
> On 22.10.19 15:18, Stefan Roese wrote:
>> Hi Frieder,
>> Hi Ashish,
>> Hi Ye Li,
>> Hi Fabio,
>>
>> On 18.09.19 09:42, Stefan Roese wrote:
>>> Hi Frieder,
>>>
>>> O
Hi Stefan,
On 22.10.19 15:18, Stefan Roese wrote:
> Hi Frieder,
> Hi Ashish,
> Hi Ye Li,
> Hi Fabio,
>
> On 18.09.19 09:42, Stefan Roese wrote:
>> Hi Frieder,
>>
>> On 18.09.19 09:08, Schrempf Frieder wrote:
>>
>>
>>
>>>> O
Hi Lukasz, hi Xiaowei,
On 22.10.19 14:20, Lukasz Majewski wrote:
> Hi Xiaowei,
>
>> Hi Lukasz,
>>
>> My patches depends on your patches
>> https://patchwork.ozlabs.org/project/uboot/list/?series=129069, do
>> you have plan to update it? I saw that the status is "changes
>> required", any comments
Hi Jagan,
On 17.10.19 08:42, Frieder Schrempf wrote:
> Hi Jagan,
>
> On 16.10.19 18:34, Jagan Teki wrote:
>> On Sat, Sep 14, 2019 at 4:18 AM Schrempf Frieder
>> wrote:
>>>
>>> From: Frieder Schrempf
>>>
>>> As SPI_FLASH_MTD is used
Hi Jagan,
On 16.10.19 18:34, Jagan Teki wrote:
> On Sat, Sep 14, 2019 at 4:18 AM Schrempf Frieder
> wrote:
>>
>> From: Frieder Schrempf
>>
>> As SPI_FLASH_MTD is used in SPL and U-Boot proper, we enable both,
>> now that a separate option for SPL was intr
Hi Robert,
On 15.10.19 17:53, Robert Beckett wrote:
> Add DM driver to support Dialog DA9063.
> Currently it support binding regulator children.
>
> Signed-off-by: Robert Beckett
I also have a board with DA9063 and was looking for support in U-Boot. I
found patches from Martin Fuzzey [1] and p
On 14.09.19 00:44, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> Most boards currently use SPI_FLASH_MTD only in U-Boot proper, not in
> SPL. They often rely on hacks in the board header files to include
> this option conditionally. To be able to fix this, we previously
Hi Stefan,
On 18.09.19 06:51, Stefan Roese wrote:
> Hi Ashish,
>
> On 13.09.19 15:11, Stefan Roese wrote:
>> On 12.09.19 14:36, Stefan Roese wrote:
>>
>>
>>
The spi-mem version is still under debug, I could make it working
for ls1088rdb, ls1046rdb, but it is failing for
ls1012ardb
Hi Peng,
I tried to get Ethernet running on i.MX8MM with mainline U-Boot and your
latest patches for SoC-support.
I added the missing clocks, but something still seems to be wrong. It
seems like the clock parents are not set correctly.
If I run "dm tree", I see that the enet_axi is a child of c
From: Frieder Schrempf
Most boards currently use SPI_FLASH_MTD only in U-Boot proper, not in
SPL. They often rely on hacks in the board header files to include
this option conditionally. To be able to fix this, we previously
introduced a separate option SPL_SPI_FLASH_MTD.
Therefore we can now ad
From: Frieder Schrempf
As SPI_FLASH_MTD is used in SPL and U-Boot proper, we enable both,
now that a separate option for SPL was introduced.
Signed-off-by: Frieder Schrempf
---
configs/stm32mp15_basic_defconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/configs/stm32
From: Frieder Schrempf
To allow SPI_FLASH_MTD being enabled separately in SPL we add a new
option. The only user currently is the stm32mp15_basic board.
Signed-off-by: Frieder Schrempf
---
drivers/mtd/spi/Kconfig | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/mtd/spi/Kconf
On 12.09.19 11:03, Lukasz Majewski wrote:
> Hi Frieder,
>
>> Hi Lukasz,
>>
>> On 10.09.19 12:22, Lukasz Majewski wrote:
>>> Hi Frieder,
>>>
>>>> On Mon, 9 Sep 2019 11:11:50 +
>>>> Schrempf Frieder wrote:
>>>>
Hi Lukasz,
On 10.09.19 12:22, Lukasz Majewski wrote:
> Hi Frieder,
>
>> On Mon, 9 Sep 2019 11:11:50 +
>> Schrempf Frieder wrote:
>>
>>> Hi Lukasz,
>>>
>>> On 05.09.19 20:09, Tom Rini wrote:
>>>> On Thu, Sep 05, 2019 at 12:
Hi Lukasz,
On 05.09.19 20:09, Tom Rini wrote:
> On Thu, Sep 05, 2019 at 12:16:36AM +0200, Lukasz Majewski wrote:
>> This patch series introduces new SPL and TPL specific Kconfig entries for
>> DM_SPI* options. Such change allows using the spi driver in SPL/TPL or
>> U-Boot proper.
>>
>> First two
Hi Ashish,
On 27.08.19 11:56, Ashish Kumar wrote:
>
>
>> -Original Message-----
>> From: Schrempf Frieder
>> Sent: Wednesday, August 14, 2019 5:41 PM
>> To: Ashish Kumar ; Ye Li ;
>> ja...@amarulasolutions.com
>> Cc: Fabio Estevam ; u-boot@lists
Hi Eugeniy,
On 04.09.19 20:07, Eugeniy Paltsev wrote:
> We faced with regressions caused by
> commit c4e8862308d4 (mtd: spi: Switch to new SPI NOR framework)
> This switch was performed by removing entire u-boot spi-flash
> core implementation and copying it from another project.
> However the swi
On 29.08.19 03:21, Peng Fan wrote:
> Hi Frieder,
>
>> Subject: Re: [PATCH V3 24/27] imx8m: soc: probe clock device in
>> arch_cpu_init_dm
>>
>> Hi Peng,
>>
>> On 27.08.19 08:25, Peng Fan wrote:
>>> Because we need to get cpu freq in print_cpuinfo at very early stage,
>>> so we need to make sure th
Hi Peng,
On 27.08.19 08:25, Peng Fan wrote:
> Because we need to get cpu freq in print_cpuinfo at very early stage,
> so we need to make sure the ccm be probed.
>
> Signed-off-by: Peng Fan
> ---
> arch/arm/mach-imx/imx8m/soc.c | 17 +
> 1 file changed, 17 insertions(+)
>
> di
On 15.08.19 02:57, Peng Fan wrote:
>> Subject: Re: [PATCH 22/22] imx: Add i.MX8MM EVK board support.
>>
>> On 09.08.19 06:15, Peng Fan wrote:
>>> Add board and SoC dts
>>> Add ddr training code
>>> support SD/MMC/GPIO/PINCTRL/UART
>>>
>>> Signed-off-by: Peng Fan
>>> ---
>>>arch/arm/dts/Makefil
On 19.08.19 11:42, Peng Fan wrote:
> V2:
> Fixed comments from Lukasz and Frieder
This set has 26 patches, while the previous version had 22. You should
document all changes here, so one can easily figure out which patches
were added/removed/merged/split.
>
> V1:
> https://patchwork.ozlabs.org
On 15.08.19 03:01, Peng Fan wrote:
>> Subject: Re: [PATCH 09/22] imx8m: update imx-regs for i.MX8MM
>>
>> On 09.08.19 06:15, Peng Fan wrote:
>>> i.MX8MM has similar architecture with i.MX8MQ, but it has totally
>>> different PLL design and some register layout change.
>>>
>>> Note: Some registers i
On 19.08.19 11:42, Peng Fan wrote:
> The loader for the DDR firmware in drivers/ddr/imx/imx8m/helper.c uses a
> 4-byte-aligned address to load the firmware. In cases where OF is
> enabled in SPL the dtb will be appended to the SPL binary and can result
> in a binary that is not aligned correctly. I
On 19.08.19 11:42, Peng Fan wrote:
> With CONFIG_SPL_OF_CONTROL, the device tree will be padded to
> end of the u-boot-spl-nodtb.bin, however we also put
> the ddr firmware file to this location, so need to adapt
> the code with SPL OF and align to 4bytes to ease copy firmware.
Please add a space
Hi Peng,
On 09.08.19 06:14, Peng Fan wrote:
> This is a splitted and updated patch from
> https://patchwork.ozlabs.org/cover/1128799/ which is to support both
> i.MX8MM and i.MX8MN.
I have sent you feedback for some of the patches. My own board is
working, but there are still a few things to fix
On 09.08.19 06:15, Peng Fan wrote:
> Add board and SoC dts
> Add ddr training code
> support SD/MMC/GPIO/PINCTRL/UART
>
> Signed-off-by: Peng Fan
> ---
> arch/arm/dts/Makefile |3 +-
> arch/arm/dts/imx8mm-evk-u-boot.dtsi| 92 ++
> arch/arm/dts/imx8mm-evk.dts
On 09.08.19 06:15, Peng Fan wrote:
> i.MX8MM has similar architecture with i.MX8MQ, but it has totally
> different PLL design and some register layout change.
>
> Note: Some registers in this file are not updated because not used now.
I think this is a bad idea. There seem to be many differences
Sorry, I hit the "Send" button too early ;)
On 14.08.19 14:07, Frieder Schrempf wrote:
> Hi Ashish,
>
> On 14.08.19 14:02, Ashish Kumar wrote:
>>
>>
>>> -Original Message-
>>> From: U-Boot On Behalf Of Schrempf
>>> Frieder
>&
Hi Ashish,
On 14.08.19 14:02, Ashish Kumar wrote:
>
>
>> -Original Message-
>> From: U-Boot On Behalf Of Schrempf Frieder
>> Sent: Wednesday, August 14, 2019 5:07 PM
>> To: Ye Li ; ja...@amarulasolutions.com
>> Cc: Fabio Estevam ; u-boot@lists.d
Hi Ye,
On 14.08.19 12:08, Ye Li wrote:
> On latest iMX platforms like iMX7D/iMX6UL/iMX8MQ, the QSPI controller
> is updated to have TDH field in FLSHCR register. According to reference
> manual, this TDH must be set to 1 when DDR_EN is set. Otherwise, the TX
> DDR delay logic won't be enabled.
Th
On 09.08.19 06:15, Peng Fan wrote:
> Import i.MX8MM dtsi from Linux Kernel,
> commit <0a8ad0ffa4d8> ("Merge tag 'for-linus-5.3-ofs1' of
> git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux")
>
> Signed-off-by: Peng Fan
> ---
> arch/arm/dts/imx8mm.dtsi | 733
> +
On 13.08.19 10:05, Peng Fan wrote:
> Hi Frieder
>
>> Subject: [PATCH v2] i2c: mxc: add CONFIG_CLK support
>>
>> When CONFIG_CLK enabled, use CLK UCLASS for clk related settings.
>
> Are you fine with this patch?
Yes!
Reviewed-by: Frieder Schrempf
Tested-by: Frieder Schrempf
>
> Thanks,
> Pe
1 - 100 of 144 matches
Mail list logo
