ClearFog Base static variant support
Subsystems (3)
v2 cover ClearFog Base static variant support
This patch series adds support for ClearFog Base static configuration, as well as updating and fixing the ClearFog support for MMC and SPI booting.
V2 changes:
- updated against, and dependent on, https://patchwork.ozlabs.org/cover/1200324
Joel Johnson (10):
arm: mvebu: fix SerDes table alignment
arm: mvebu: solidrun: remove hardcoded DTS MAC address
arm: mvebu: clearfog: initial ClearFog Base variant
arm: mvebu: clearfog: Use Pro DT by default
arm: mvebu: clearfog: Add SATA mode flags
arm: mvebu: clearfog: Add option for 2.5 Gbps SFP
arm: mvebu: clearfog: add SPI offsets
arm: mvebu: enable working default boot support
arm: mvebu: clearfog: move ENV params to Kconfig
arm: mvebu: clearfog: reduce MMC boot assumptions
.../arm/dts/armada-38x-solidrun-microsom.dtsi | 1 - arch/arm/mach-mvebu/Kconfig | 13 ++++ .../serdes/a38x/high_speed_env_spec.c | 6 +- board/solidrun/clearfog/Kconfig | 62 +++++++++++++++++++ board/solidrun/clearfog/clearfog.c | 26 +++++++- configs/clearfog_defconfig | 5 -- include/configs/clearfog.h | 1 - 7 files changed, 103 insertions(+), 11 deletions(-) create mode 100644 board/solidrun/clearfog/Kconfig
Signature · 1 line
2.20.1
PATCH v2 1/10 arm: mvebu: fix SerDes table alignment
Tested on Solidrun ClearFog Base. Table alignment was:
| Lane # | Speed | Type |
--------------------------------
| 0 | 3 | SATA0 | | 1 | 0 | SGMII1 | | 2 | 3 | SATA1 | | 3 | 5 | USB3 HOST1 | | 4 | 5 | USB3 HOST0 | | 5 | 4 | SGMII2 |
--------------------------------
After the change, it's correctly aligned as:
| Lane # | Speed | Type |
--------------------------------
| 0 | 3 | SATA0 | | 1 | 0 | SGMII1 | | 2 | 5 | PCIe1 | | 3 | 5 | USB3 HOST1 | | 4 | 5 | PCIe2 | | 5 | 0 | SGMII2 |
--------------------------------
---
v2 changes
- none
--- arch/arm/mach-mvebu/serdes/a38x/high_speed_env_spec.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/arm/mach-mvebu/serdes/a38x/high_speed_env_spec.c +3 -3
@@ -1366,16 +1366,16 @@ static void print_topology_details(const struct serdes_map *serdes_map,DEBUG_INIT_S ("board SerDes lanes topology details:\n" ); -DEBUG_INIT_S (" | Lane # | Speed | Type |\n" ); +DEBUG_INIT_S (" | Lane # | Speed | Type |\n" );DEBUG_INIT_S (" --------------------------------\n" );for (lane_num =0 ; lane_num < count; lane_num++) {if (serdes_map[lane_num].serdes_type ==DEFAULT_SERDES )continue ;DEBUG_INIT_S (" | " );DEBUG_INIT_D (hws_get_physical_serdes_num (lane_num),1 ); -DEBUG_INIT_S (" | " ); +DEBUG_INIT_S (" | " );DEBUG_INIT_D (serdes_map[lane_num].serdes_speed,2 ); -DEBUG_INIT_S (" | " ); +DEBUG_INIT_S (" | " );DEBUG_INIT_S ((char *) serdes_type_to_string[serdes_map[lane_num]. serdes_type]);
Signature · 1 line
2.20.1
PATCH v2 2/10 arm: mvebu: solidrun: remove hardcoded DTS MAC address
In reply to Joel JohnsonUsing a consistent hardcoded MAC address from the DTS file causes issues when using multiple devices on the same network segment. Instead rely on environment configuration or random generation.
---
v2 changes:
- none
--- arch/arm/dts/armada-38x-solidrun-microsom.dtsi | 1 - 1 file changed, 1 deletion(-)
arch/arm/dts/armada-38x-solidrun-microsom.dtsi +0 -1
@@ -39,7 +39,6 @@ ð0 { /* ethernet at 70000 */ - mac-address = [00 50 43 02 02 01]; pinctrl-0 = <&ge0_rgmii_pins>; pinctrl-names = "default"; phy = <&phy_dedicated>;
Signature · 1 line
2.20.1
PATCH v2 3/10 arm: mvebu: clearfog: initial ClearFog Base variant
In reply to Joel JohnsonAdd a unique entry for ClearFog Base variant, reflected in the board name and adjusted SerDes topology.
---
v2 changes:
- reworked based on Baruch's run-time TLV EEPROM detection series
--- arch/arm/mach-mvebu/Kconfig | 2 ++ board/solidrun/clearfog/Kconfig | 18 ++++++++++++++++++ board/solidrun/clearfog/clearfog.c | 12 ++++++++++++ 3 files changed, 32 insertions(+) create mode 100644 board/solidrun/clearfog/Kconfig
arch/arm/mach-mvebu/Kconfig +2 -0
@@ -280,4 +280,6 @@ config SECURED_MODE_CSK_INDEX default 0 depends on SECURED_MODE_IMAGE +source "board/solidrun/clearfog/Kconfig" + endif
board/solidrun/clearfog/Kconfig new file +18 -0
@@ -0,0 +1,18 @@ +menu "ClearFog configuration" + depends on TARGET_CLEARFOG + +config TARGET_CLEARFOG_BASE + bool "Use ClearFog Base static configuration" + help + Use the ClearFog Base as the static configuration instead of the + default which uses the ClearFog Pro. + + Runtime board detection is always attempted and used if available. The + static configuration is used as a fallback in cases where runtime + detection is not available. + + Only newer revisions of the ClearFog product line support runtime + detection via additional EEPROM hardware. This option enables selecting + the Base variant for older hardware revisions. + +endmenu
board/solidrun/clearfog/clearfog.c +12 -0
@@ -44,7 +44,11 @@ static struct serdes_map board_serdes_map[] = { {SGMII1, SERDES_SPEED_1_25_GBPS, SERDES_DEFAULT_MODE, 0, 0}, {PEX1, SERDES_SPEED_5_GBPS, PEX_ROOT_COMPLEX_X1, 0, 0}, {USB3_HOST1, SERDES_SPEED_5_GBPS, SERDES_DEFAULT_MODE, 0, 0}, +#if defined (CONFIG_TARGET_CLEARFOG_BASE) + {USB3_HOST0 ,SERDES_SPEED_5_GBPS ,SERDES_DEFAULT_MODE ,0 ,0 }, +#else {PEX2, SERDES_SPEED_5_GBPS, PEX_ROOT_COMPLEX_X1, 0, 0}, +#endif {SGMII2, SERDES_SPEED_1_25_GBPS, SERDES_DEFAULT_MODE, 0, 0}, };
@@ -262,7 +266,11 @@ int board_init(void)int checkboard (void ) { +#if defined (CONFIG_TARGET_CLEARFOG_BASE ) +char *board ="ClearFog Base" ; +#else char *board ="ClearFog" ; +#endif read_tlv_data ();if (strlen (tlv_product_name[0 ]) >0 )
@@ -292,6 +300,10 @@ int board_late_init(void)env_set ("fdtfile" ,"armada-385-clearfog-gtr-s4.dtb" ); else if (sr_product_is("Clearfog GTR L8")) env_set("fdtfile", "armada-385-clearfog-gtr-l8.dtb"); +#if defined (CONFIG_TARGET_CLEARFOG_BASE ) + else + env_set("fdtfile", "armada-388-clearfog-base.dtb"); +#endif return 0 ; }
Signature · 1 line
2.20.1
PATCH v2 4/10 arm: mvebu: clearfog: Use Pro DT by default
In reply to Joel JohnsonSwitch to explicitly using the Pro variant DT, which has been available since Linux 4.11. Also unify the location of DT selection in board_late_init instead of split between detection and static configuration paths.
---
v2 changes
- newly added in V2 series based on run-time rebasing
--- board/solidrun/clearfog/clearfog.c | 6 ++++-- include/configs/clearfog.h | 1 - 2 files changed, 4 insertions(+), 3 deletions(-)
board/solidrun/clearfog/clearfog.c +4 -2
@@ -269,7 +269,7 @@ int checkboard(void)#if defined (CONFIG_TARGET_CLEARFOG_BASE )char *board ="ClearFog Base" ;#else -char *board ="ClearFog" ; +char *board ="ClearFog Pro" ;#endif read_tlv_data ();
@@ -300,9 +300,11 @@ int board_late_init(void)env_set ("fdtfile" ,"armada-385-clearfog-gtr-s4.dtb" ); else if (sr_product_is("Clearfog GTR L8")) env_set("fdtfile", "armada-385-clearfog-gtr-l8.dtb"); -#if defined (CONFIG_TARGET_CLEARFOG_BASE ) else +#if defined (CONFIG_TARGET_CLEARFOG_BASE )env_set ("fdtfile" ,"armada-388-clearfog-base.dtb" ); +#else +env_set ("fdtfile" ,"armada-388-clearfog-pro.dtb" );#endif return 0 ;
include/configs/clearfog.h +0 -1
@@ -134,7 +134,6 @@#define CONFIG_EXTRA_ENV_SETTINGS \ RELOCATION_LIMITS_ENV_SETTINGS \ LOAD_ADDRESS_ENV_SETTINGS \ - "fdtfile=" CONFIG_DEFAULT_DEVICE_TREE ".dtb\0" \ "console=ttyS0,115200\0" \ BOOTENV
Signature · 1 line
2.20.1
PATCH v2 5/10 arm: mvebu: clearfog: Add SATA mode flags
In reply to Joel JohnsonThe mPCIe slots on ClearFog Pro and ClearFog Base may be alternately configured for SATA usage.
---
v2 changes:
- fixed help indentation
--- board/solidrun/clearfog/Kconfig | 17 +++++++++++++++++ board/solidrun/clearfog/clearfog.c | 6 ++++++ 2 files changed, 23 insertions(+)
board/solidrun/clearfog/Kconfig +17 -0
@@ -15,4 +15,21 @@ config TARGET_CLEARFOG_BASE detection via additional EEPROM hardware. This option enables selecting the Base variant for older hardware revisions. +config CLEARFOG_CON3_SATA + bool "Use CON3 slot in SATA mode" + help + Use the CON3 port with SATA protocol instead of the default PCIe. + The ClearFog port allows usage of either mSATA or miniPCIe + modules, but the desired protocol must be configured at build + time since it affects the SerDes topology layout. + +config CLEARFOG_CON2_SATA + bool "Use CON2 slot in SATA mode" + depends on !TARGET_CLEARFOG_BASE + help + Use the CON2 port with SATA protocol instead of the default PCIe. + The ClearFog port allows usage of either mSATA or miniPCIe + modules, but the desired protocol must be configured at build + time since it affects the SerDes topology layout. + endmenu
board/solidrun/clearfog/clearfog.c +6 -0
@@ -42,10 +42,16 @@ static void read_tlv_data(void);static struct serdes_map board_serdes_map[] = { {SATA0 ,SERDES_SPEED_3_GBPS ,SERDES_DEFAULT_MODE ,0 ,0 }, {SGMII1 ,SERDES_SPEED_1_25_GBPS ,SERDES_DEFAULT_MODE ,0 ,0 }, +#if defined (CONFIG_CLEARFOG_CON3_SATA) + {SATA1 ,SERDES_SPEED_3_GBPS ,SERDES_DEFAULT_MODE ,0 ,0 }, +#else {PEX1 ,SERDES_SPEED_5_GBPS ,PEX_ROOT_COMPLEX_X1 ,0 ,0 }, +#endif {USB3_HOST1 ,SERDES_SPEED_5_GBPS ,SERDES_DEFAULT_MODE ,0 ,0 }, #if defined (CONFIG_TARGET_CLEARFOG_BASE) {USB3_HOST0 ,SERDES_SPEED_5_GBPS ,SERDES_DEFAULT_MODE ,0 ,0 }, +#elif defined(CONFIG_CLEARFOG_CON2_SATA) + {SATA2 ,SERDES_SPEED_3_GBPS ,SERDES_DEFAULT_MODE ,0 ,0 }, #else {PEX2 ,SERDES_SPEED_5_GBPS ,PEX_ROOT_COMPLEX_X1 ,0 ,0 }, #endif
Signature · 1 line
2.20.1
PATCH v2 6/10 arm: mvebu: clearfog: Add option for 2.5 Gbps SFP
In reply to Joel Johnson---
v2 changes:
- fixed help indentation
--- board/solidrun/clearfog/Kconfig | 7 +++++++ board/solidrun/clearfog/clearfog.c | 4 ++++ 2 files changed, 11 insertions(+)
board/solidrun/clearfog/Kconfig +7 -0
@@ -32,4 +32,11 @@ config CLEARFOG_CON2_SATA modules, but the desired protocol must be configured at build time since it affects the SerDes topology layout. +config CLEARFOG_SFP_25GB + bool "Enable 2.5 Gbps mode for SFP" + help + Set the SFP module connection to support 2.5 Gbps transfer speed for the + SGMII connection (requires a supporting SFP). By default, transfer speed + of 1.25 Gbps is used, suitable for a more common 1 Gbps SFP module. + endmenu
board/solidrun/clearfog/clearfog.c +4 -0
@@ -55,7 +55,11 @@ static struct serdes_map board_serdes_map[] = { #else {PEX2, SERDES_SPEED_5_GBPS, PEX_ROOT_COMPLEX_X1, 0, 0}, #endif +#if defined (CONFIG_CLEARFOG_SFP_25GB) + {SGMII2, SERDES_SPEED_3_125_GBPS, SERDES_DEFAULT_MODE, 0, 0}, +#else {SGMII2, SERDES_SPEED_1_25_GBPS, SERDES_DEFAULT_MODE, 0, 0}, +#endif }; int hws_board_topology_load(struct serdes_map **serdes_map_array, u8 *count)
Signature · 1 line
2.20.1
PATCH v2 7/10 arm: mvebu: clearfog: add SPI offsets
In reply to Joel JohnsonAdd reasonable default SPI offsets and ENV size when configured to boot from SPI flash.
---
v2 changes:
- none
There was some reasonable concern raised about duplicating config entries within a board specific config file rather than making board specific configurations within defconfig. This seems to offer a more board localized mechanism to provide platform defaults for core values. As mentioned in the review, this usage seems to match the Kconfig documented intended usage. As noted at
https://www.kernel.org/doc/html/latest/kbuild/kconfig-language.html:
"Default values are not limited to the menu entry where
they are defined. This means the default can be defined somewhere else or be overridden by an earlier definition."
Given that there is some dependency variability with these values I prefer keeping them as Kconfig values, but defer to maintainers. Notably, for the ENV values in this and a later commit, I'm using a pattern already in used several other board configs.
--- board/solidrun/clearfog/Kconfig | 12 ++++++++++++ 1 file changed, 12 insertions(+)
board/solidrun/clearfog/Kconfig +12 -0
@@ -39,4 +39,16 @@ config CLEARFOG_SFP_25GB SGMII connection (requires a supporting SFP). By default, transfer speed of 1.25 Gbps is used, suitable for a more common 1 Gbps SFP module. +config ENV_SECT_SIZE + hex "Environment Sector-Size" + # Use SPI flash erase block size of 4 KiB + default 0x1000 if MVEBU_SPL_BOOT_DEVICE_SPI + # Use optimistic 64 KiB erase block, will vary between actual media + default 0x10000 if MVEBU_SPL_BOOT_DEVICE_MMC + +config SYS_SPI_U_BOOT_OFFS + hex "address of u-boot payload in SPI flash" + default 0x20000 + depends on MVEBU_SPL_BOOT_DEVICE_SPI + endmenu
Signature · 1 line
2.20.1
PATCH v2 8/10 arm: mvebu: enable working default boot support
In reply to Joel JohnsonWith the move to driver model usage, ensure that the required driver support for SPI and MMC booting is available in SPL.
Tested on SolidRun ClearFog devices.
---
v2 changes:
- change "select" for ENV_IS_IN_X to "imply" to allow disabling the default env location and configuring a different one if desired
- remove SPL_DM_GPIO from defconfig, only include if needed for MMC booting
--- arch/arm/mach-mvebu/Kconfig | 10 ++++++++++ configs/clearfog_defconfig | 1 - 2 files changed, 10 insertions(+), 1 deletion(-)
arch/arm/mach-mvebu/Kconfig +10 -0
@@ -235,9 +235,19 @@ choice config MVEBU_SPL_BOOT_DEVICE_SPI bool "SPI NOR flash" + imply ENV_IS_IN_SPI_FLASH + select SPL_DM_SPI + select SPL_MTD_SUPPORT + select SPL_SPI_FLASH_SUPPORT + select SPL_SPI_LOAD + select SPL_SPI_SUPPORT config MVEBU_SPL_BOOT_DEVICE_MMC bool "SDIO/MMC card" + imply ENV_IS_IN_MMC + # GPIO required for SD card presence detection line + select SPL_DM_GPIO + select SPL_DM_MMC select SPL_LIBDISK_SUPPORT config MVEBU_SPL_BOOT_DEVICE_SATA
configs/clearfog_defconfig +0 -1
@@ -28,7 +28,6 @@ CONFIG_SYS_CONSOLE_INFO_QUIET=y # CONFIG_DISPLAY_BOARDINFO is not set CONFIG_DISPLAY_BOARDINFO_LATE=y CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET=0x1 -CONFIG_SPL_DM_GPIO=y CONFIG_SPL_I2C_SUPPORT=y CONFIG_CMD_SYS_EEPROM=y CONFIG_SPL_CMD_SYS_EEPROM=y
Signature · 1 line
2.20.1
PATCH v2 9/10 arm: mvebu: clearfog: move ENV params to Kconfig
In reply to Joel JohnsonMigrate the values for ENV_SIZE and ENV_OFFSET into board specific Kconfig defaults so they're more accessible for configuration.
---
v2 changes:
- none
--- board/solidrun/clearfog/Kconfig | 8 ++++++++ configs/clearfog_defconfig | 2 -- 2 files changed, 8 insertions(+), 2 deletions(-)
board/solidrun/clearfog/Kconfig +8 -0
@@ -39,6 +39,14 @@ config CLEARFOG_SFP_25GB SGMII connection (requires a supporting SFP). By default, transfer speed of 1.25 Gbps is used, suitable for a more common 1 Gbps SFP module. +config ENV_SIZE + hex "Environment Size" + default 0x10000 + +config ENV_OFFSET + hex "Environment offset" + default 0xF0000 + config ENV_SECT_SIZE hex "Environment Sector-Size" # Use SPI flash erase block size of 4 KiB
configs/clearfog_defconfig +0 -2
@@ -11,8 +11,6 @@ CONFIG_TARGET_CLEARFOG=y CONFIG_MVEBU_SPL_BOOT_DEVICE_MMC=y CONFIG_SPL_MMC_SUPPORT=y CONFIG_SPL_SERIAL_SUPPORT=y -CONFIG_ENV_SIZE=0x10000 -CONFIG_ENV_OFFSET=0xF0000 CONFIG_SPL_DRIVERS_MISC_SUPPORT=y CONFIG_NR_DRAM_BANKS=2 CONFIG_SPL=y
Signature · 1 line
2.20.1
PATCH v2 10/10 arm: mvebu: clearfog: reduce MMC boot assumptions
In reply to Joel JohnsonReduce those MMC booting assumptions from clearfog_defconfig which are already selected by dependent options via Kconfig.
---
v2 changes:
- rebased on master to use Baruch's dynamic MMC/SD offset logic
- update description, will revisit removal of CONFIG_MVEBU_SPL_BOOT_DEVICE_MMC in separate future path if a more viable option is identified
--- arch/arm/mach-mvebu/Kconfig | 1 + configs/clearfog_defconfig | 2 -- 2 files changed, 1 insertion(+), 2 deletions(-)
arch/arm/mach-mvebu/Kconfig +1 -0
@@ -249,6 +249,7 @@ config MVEBU_SPL_BOOT_DEVICE_MMC select SPL_DM_GPIO select SPL_DM_MMC select SPL_LIBDISK_SUPPORT + select SPL_MMC_SUPPORT config MVEBU_SPL_BOOT_DEVICE_SATA bool "SATA"
configs/clearfog_defconfig +0 -2
@@ -9,7 +9,6 @@ CONFIG_SPL_LIBGENERIC_SUPPORT=y CONFIG_SYS_MALLOC_F_LEN=0x2000 CONFIG_TARGET_CLEARFOG=y CONFIG_MVEBU_SPL_BOOT_DEVICE_MMC=y -CONFIG_SPL_MMC_SUPPORT=y CONFIG_SPL_SERIAL_SUPPORT=y CONFIG_SPL_DRIVERS_MISC_SUPPORT=y CONFIG_NR_DRAM_BANKS=2
@@ -42,7 +41,6 @@ CONFIG_CMD_CACHE=y CONFIG_CMD_TIME=y # CONFIG_SPL_PARTITION_UUIDS is not set CONFIG_DEFAULT_DEVICE_TREE="armada-388-clearfog" -CONFIG_ENV_IS_IN_MMC=y CONFIG_NET_RANDOM_ETHADDR=y CONFIG_SPL_OF_TRANSLATE=y CONFIG_AHCI_MVEBU=y
Signature · 1 line
2.20.1
v2 cover ClearFog Base static variant support
In reply to Joel JohnsonHi Joel,
Quoted 6 lines · Joel Johnson
This patch series adds support for ClearFog Base static configuration, as well as updating and fixing the ClearFog support for MMC and SPI booting.
V2 changes:
- updated against, and dependent on, https://patchwork.ozlabs.org/cover/1200324
Thanks for the update.
Next time please Cc at least me and Stefan on the entire series.
baruch
Quoted 21 lines
Joel Johnson (10):
arm: mvebu: fix SerDes table alignment
arm: mvebu: solidrun: remove hardcoded DTS MAC address
arm: mvebu: clearfog: initial ClearFog Base variant
arm: mvebu: clearfog: Use Pro DT by default
arm: mvebu: clearfog: Add SATA mode flags
arm: mvebu: clearfog: Add option for 2.5 Gbps SFP
arm: mvebu: clearfog: add SPI offsets
arm: mvebu: enable working default boot support
arm: mvebu: clearfog: move ENV params toKconfig
arm: mvebu: clearfog: reduce MMC boot assumptions.../arm/dts/armada-38x-solidrun-microsom.dtsi | 1 - arch/arm/mach-mvebu/Kconfig | 13 ++++ .../serdes/a38x/high_speed_env_spec.c | 6 +- board/solidrun/clearfog/Kconfig | 62 +++++++++++++++++++ board/solidrun/clearfog/clearfog.c | 26 +++++++- configs/clearfog_defconfig | 5 -- include/configs/clearfog.h | 1 - 7 files changed, 103 insertions(+), 11 deletions(-) create mode 100644 board/solidrun/clearfog/Kconfig
Signature · 3 lines
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -v2 cover ClearFog Base static variant support
Quoted 11 lines · Baruch Siach
Hi Joel,
Quoted 7 lines · Joel Johnson
This patch series adds support for ClearFog Base static configuration, as well as updating and fixing the ClearFog support for MMC and SPI booting.
V2 changes:
- updated against, and dependent on,
https://patchwork.ozlabs.org/cover/1200324
Quoted 5 lines
Thanks for the update.
Next time please Cc at least me and Stefan on the entire series.
baruch
I certainly intended to, and based on the email headers it appears that I did...
Actually, I see what you're saying, not all of the patches in the series were delivered to you. I neglected to add (or notice during sending) the Series-cc line for patman. My apologizes - I've added it for my local branch on this series and I'll keep an eye out for that in the future.
Relatedly, I've been directing the series to Prafulla Wadaskar as noted in the custodians listing for marvell, but am getting email delivery failures. Any updated guidance or contact updates would be appreciated.
Joel
v2 cover ClearFog Base static variant support
Hi Joel,
Quoted 19 lines · Joel Johnson
Quoted 9 lines · Baruch Siach
Quoted 7 lines · Joel Johnson
This patch series adds support for ClearFog Base static configuration, as well as updating and fixing the ClearFog support for MMC and SPI booting.
V2 changes:
- updated against, and dependent on,
https://patchwork.ozlabs.org/cover/1200324Quoted 5 lines
Thanks for the update.
Next time please Cc at least me and Stefan on the entire series.
baruch
I certainly intended to, and based on the email headers it appears that I did...
Quoted 8 lines
Actually, I see what you're saying, not all of the patches in the series were delivered to you. I neglected to add (or notice during sending) the Series-cc line for patman. My apologizes - I've added it for my local branch on this series and I'll keep an eye out for that in the future.
Relatedly, I've been directing the series to Prafulla Wadaskar as noted in the custodians listing for marvell, but am getting email delivery failures. Any updated guidance or contact updates would be appreciated.
Prafulla has been removed from the Marvell entry in MAINTAINERS in commit 1579faf52b9f4 (February 2019). I don't think you need to Cc him on Marvell SoC related patches.
baruch
Signature · 3 lines
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -v2 cover ClearFog Base static variant support
Quoted 38 lines · Baruch Siach
Hi Joel,
Quoted 29 lines · Joel Johnson
Quoted 10 lines · Baruch Siach
Quoted 8 lines · Joel Johnson
This patch series adds support for ClearFog Base static configuration,
as well as updating and fixing the ClearFog support for MMC and SPI booting.V2 changes:
- updated against, and dependent on,
https://patchwork.ozlabs.org/cover/1200324Quoted 5 lines
Thanks for the update.
Next time please Cc at least me and Stefan on the entire series.
baruch
I certainly intended to, and based on the email headers it appears that I
did...Actually, I see what you're saying, not all of the patches in the series were
delivered to you. I neglected to add (or notice during sending) the Series-cc
line for patman. My apologizes - I've added it for my local branch on this
series and I'll keep an eye out for that in the future.Quoted 5 lines
Relatedly, I've been directing the series to Prafulla Wadaskar as noted in the
custodians listing for marvell, but am getting email delivery failures. Any
updated guidance or contact updates would be appreciated.
Quoted 5 lines
Prafulla has been removed from the Marvell entry in
MAINTAINERSin commit1579faf52b9f4(February 2019). I don't think you need to Cc him on Marvell SoC related patches.baruch
Indeed, thanks. I had pulled his information from the Custodians wiki page at http://www.denx.de/wiki/U-Boot/Custodians, so perhaps something that Stefan or editor can update accordingly.
Joel
v2 cover ClearFog Base static variant support
Hi Joel,
Quoted 43 lines · Joel Johnson
Quoted 42 lines · Baruch Siach
Hi Joel,
Quoted 29 lines · Joel Johnson
Quoted 10 lines · Baruch Siach
Quoted 8 lines · Joel Johnson
This patch series adds support for ClearFog Base static configuration,
as well as updating and fixing the ClearFog support for MMC and SPI booting.V2 changes:
- updated against, and dependent on,
https://patchwork.ozlabs.org/cover/1200324Quoted 5 lines
Thanks for the update.
Next time please Cc at least me and Stefan on the entire series.
baruch
I certainly intended to, and based on the email headers it appears that I
did...Actually, I see what you're saying, not all of the patches in the series were
delivered to you. I neglected to add (or notice during sending) the Series-cc
line for patman. My apologizes - I've added it for my local branch on this
series and I'll keep an eye out for that in the future.Quoted 5 lines
Relatedly, I've been directing the series to Prafulla Wadaskar as noted in the
custodians listing for marvell, but am getting email delivery failures. Any
updated guidance or contact updates would be appreciated.Prafulla has been removed from the Marvell entry in
MAINTAINERSin commit1579faf52b9f4(February 2019). I don't think you need to Cc him on Marvell SoC related patches.
Quoted 5 lines
Quoted 1 line
baruch
Indeed, thanks. I had pulled his information from the Custodians wiki page at http://www.denx.de/wiki/U-Boot/Custodians, so perhaps something that Stefan or editor can update accordingly.
Yes, thanks for the notification. We'll update this page accordingly soon.
Thanks,
Stefan