[PATCH 9/9] net: ksz9477: add support for KSZ GbE switches using SPI bus

Kconfig option to include SPI bus support. Signed-off-by: Romain Naour --- drivers/net/Kconfig | 6 +-- drivers/net/ksz9477.c | 103 ++ 2 files changed, 106 insertions(+), 3 deletions(-) diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig index

[PATCH 8/9] net: ksz9477: prepare ksz9477 without I2C support

With the upcoming ksz9477 SPI support added, the I2C support will be optional. Either the I2C or the SPI bus will be used. For now, DM_I2C is still mandatory. Signed-off-by: Romain Naour --- drivers/net/ksz9477.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a

[PATCH 7/9] net: ksz9477: rename ksz_i2c_probe() to ksz_probe()

In order to support management bus other than the I2C, rename ksz_i2c_probe() to ksz_probe() since this function is no longer specific to the I2C bus. Signed-off-by: Romain Naour --- drivers/net/ksz9477.c | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/drivers/net

[PATCH 5/9] net: ksz9477: set i2c bus offset length only when needed

z9xxx" located under under an SPI bus node. Signed-off-by: Romain Naour --- drivers/net/ksz9477.c | 19 +++ 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/drivers/net/ksz9477.c b/drivers/net/ksz9477.c index 3756f48c9ba..ce9d4b8753f 100644 --- a/drivers/net/ks

[PATCH 6/9] net: ksz9477: store ksz bus operations functions

, introduce struct ksz_phy_ops to store low-level ksz bus operations (I2C for now). [1] https://lists.denx.de/pipermail/u-boot/2018-May/329392.html Signed-off-by: Romain Naour --- drivers/net/ksz9477.c | 92 --- 1 file changed, 86 insertions(+), 6 deletions

[PATCH 4/9] net: ksz9477: rename udevice_id tab to ksz_ids

mpatible string (like for TPM2 TIS devices). So, rename udevice_id tab to ksz_ids since it's not specific to i2c bus. Signed-off-by: Romain Naour --- drivers/net/ksz9477.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/ksz9477.c b/drivers/net/ksz9477

[PATCH 3/9] net: ksz9477: add KSZ9896 switch support

Add support for the KSZ9896 6-port Gigabit Ethernet Switch to the ksz9477 driver. The KSZ9896 is similar to KSZ9897 but has only one configurable MII/RMII/RGMII/GMII cpu port. Signed-off-by: Romain Naour --- drivers/net/ksz9477.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers

[PATCH 1/9] net: ksz9477: move struct ksz_dsa_priv *priv declaration

struct ksz_dsa_priv *priv should be declared before dev_dbg() Signed-off-by: Romain Naour --- drivers/net/ksz9477.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ksz9477.c b/drivers/net/ksz9477.c index 43baa699619..091e9689487 100644 --- a/drivers/net/ksz9477.c

[PATCH 0/9] net: ksz9477: add support for KSZ GbE switches using SPI bus

0-rc5/drivers/core/Kconfig?ref_type=tags#L188 Best regards, Romain Romain Naour (9): net: ksz9477: move struct ksz_dsa_priv *priv declaration net: ksz9477: remove dev_set_parent_priv() call net: ksz9477: add KSZ9896 switch support net: ksz9477: rename udevice_id tab to ksz_ids net: ks

[PATCH 2/9] net: ksz9477: remove dev_set_parent_priv() call

the underlying bus. While it doesn't cause any issue with I2C bus, it override the per-child data used by the SPI bus (struct spi_slave) and prevent further bus access (even with sspi command). Signed-off-by: Romain Naour --- Tested using the upcoming ksz9477 driver with spi support added lat

[PATCH 0/1] add KSZ9896 switch support with spi interface

8-May/329392.html Best regards, Romain Romain Naour (1): net: ksz9477: add KSZ9896 switch support drivers/net/ksz9477.c | 3 +++ 1 file changed, 3 insertions(+) -- 2.45.0

[PATCH 1/1] net: ksz9477: add KSZ9896 switch support

Add support for the KSZ9896 6-port Gigabit Ethernet Switch to the ksz9477 driver. The KSZ9896 is similar to KSZ9897 but has only one configurable MII/RMII/RGMII/GMII cpu port. Signed-off-by: Romain Naour --- drivers/net/ksz9477.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers

[PATCH] arch/arm/mach-omap2/omap5/fdt.c: ft_fixup_clocks: use clock-output-names property as fallback (kernel 5.19+)

From: Romain Naour Clock names has been updated in kernel 5.19+ with the removal of non-standard node names [1]. Due to this change, ft_opp_clock_fixups() doesn't work anymore since ft_fixup_clocks() is looking to the clock name and ft_opp_clock_fixups() error out with the following me

Re: [PATCH 14/15] board: ti: Add j721e_beagleboneai64_* config fragments and env file

Hello Andrew, All, Le 17/11/2023 à 19:43, Andrew Davis a écrit : > On 11/17/23 8:27 AM, Romain Naour wrote: >> Hello Andrew, All, >> >> Le 03/11/2023 à 20:20, Andrew Davis a écrit : >>> On 11/3/23 2:06 PM, Nishanth Menon wrote: >>>> On 13:51-20231103, An

Re: [PATCH 14/15] board: ti: Add j721e_beagleboneai64_* config fragments and env file

Hello Andrew, All, Le 03/11/2023 à 20:20, Andrew Davis a écrit : > On 11/3/23 2:06 PM, Nishanth Menon wrote: >> On 13:51-20231103, Andrew Davis wrote: >>> On 11/2/23 7:38 PM, Nishanth Menon wrote: Add defconfig fragments for J721E based BeagleBone AI-64 and corresponding customized envir

Re: [PATCH] ARM: dts: Use clock-output-names for dra7

Hello, Le 04/02/2022 à 09:08, Tony Lindgren a écrit : > With the TI clocks supporting the use of clock-output-names devicetree > property, we no longer need to use non-standard node names for clocks. > > Depends-on: 31aa7056bbec ("ARM: dts: Don't use legacy clock defines for dra7 > clkctrl") > D

Re: [PATCH] configs: ti: use standard configuration nodes naming

Hi Denys, Le 28/02/2022 à 21:38, Denys Dmytriyenko a écrit : > On Thu, Feb 10, 2022 at 11:13:36PM +0100, Romain Naour wrote: >> Currently, any u-boot bootloader for ti armv7 platforms using >> DEFAULT_FIT_TI_ARGS to boot with a fitimage (boot_fit = 1) >> doesn't boot

[PATCH 3/4] ARM: omap3_beagle: Enable Pinctrl

The simple pinctrl driver currently available works with the omap3. Enabling this will use the device tree to automatically set the pin-muxing for various drivers. Based on commit: 57dbf754e37d3347cad441f3869bf72c0d726a71 Signed-off-by: Romain Naour --- configs/omap3_beagle_defconfig | 2 ++ 1

[PATCH 4/4] ARM: omap3_beagle: Enable DM_PMIC and DM_REGULATOR

]. [1] a40d3cc845756e1e38af5ac31986539417e64abb [2] 2448e42d73fb91e4b56bb41b2677e18ab99a6c83 Signed-off-by: Romain Naour --- configs/omap3_beagle_defconfig | 5 + 1 file changed, 5 insertions(+) diff --git a/configs/omap3_beagle_defconfig b/configs/omap3_beagle_defconfig index a9b2c15cee

[PATCH 2/4] ARM: omap3_beagle: Power on MMC when setting up PMIC

53 [2] 27b653449178e80b333e7bc5a81eed3bd1bd6861 Signed-off-by: Romain Naour --- board/ti/beagle/beagle.c | 9 ++--- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/board/ti/beagle/beagle.c b/board/ti/beagle/beagle.c index d5a122af2b..847d596646 100644 --- a/board/ti/beagle/beagle.c +++ b/

[PATCH 1/4] ARM: omap3_beagle: Remove non-DM initialization

With DM_MMC working for both SPL and U-Boot, this patch removes the legacy style of initializing the MMC driver. Based on omap3_logic: 42140dd0962bc134c0aad27524d0f4cc3955f255. Signed-off-by: Romain Naour --- board/ti/beagle/beagle.c | 7 --- 1 file changed, 7 deletions(-) diff --git a

[PATCH] configs: ti: use standard configuration nodes naming

rg/git/meta-arago.git?p=meta-arago.git;a=commitdiff;h=f23f2876a0cda89241d031bb7ba0b4256ed90035 [3] https://git.openembedded.org/openembedded-core/tree/meta/classes/kernel-fitimage.bbclass?h=yocto-3.1.13#n290 [3] 1e93cc8473e4fe018aececc8ed3bf8fc2b3ff561 Signed-off-by: Romain Naour Cc: Tom Rini --- inc

[PATCH] tools/env/fw_env.h: remove env.h

This problem is present since uboot v2019.10. [1] http://lists.busybox.net/pipermail/buildroot/2020-April/280307.html [2] https://gitlab.denx.de/u-boot/u-boot/-/commit/9fb625ce05539fe6876a59ce1dcadb76b33c6f6e Reported-by: Nicolas Carrier Signed-off-by: Romain Naour --- tools/env/fw_env.h | 1 -

Re: [U-Boot] Using sspi for hardware detection?

Hi, Le 27/11/2019 à 21:13, Simon Goldschmidt a écrit : > On Wed, Nov 27, 2019 at 1:58 PM Romain Naour wrote: >> >> Hello, >> >> I'm working on a modular socfpga based system with several optional boards. >> Each optional board contain a board ID that can be

[U-Boot] Using sspi for hardware detection?

Hello, I'm working on a modular socfpga based system with several optional boards. Each optional board contain a board ID that can be read through a SPI bus. Since we want just read the board ID, we used manually the sspi command, something like: => sspi 1:1.0 8 0 42 But it seems that the sspi