Access to MDIO bus private data can be provided by both
struct mii_dev .priv member and struct bb_miiphy_bus .priv
member, use the former directly and remove .priv from the
later. Drop unused bb_miiphy_getbus(). This removes any
dependency on struct bb_miiphy_bus from the miiphybb code,
except for
Hi Chaoyi Chen,
On Thursday, February 27, 2025 6:29:13 AM UTC Chaoyi Chen wrote:
>
> Could you use a naming prefix like "rkvop2" to explicitly indicate the
> use of vop2, thereby distinguishing it from rk_vop.c?
>
Yes. This will be in v3.
> > + struct rk3568_vop_esmart *esmart = priv->regs +
Move miiphybb operations into separate struct bb_miiphy_bus_ops
structure, add pointer to struct bb_miiphy_bus_ops into the base
struct bb_miiphy_bus and access the ops through this pointer in
miiphybb generic code. The variable reshuffling in miiphybb.c
cannot be easily avoided.
Signed-off-by: Ma
The access to struct bb_miiphy_bus_ops via ops pointer in
struct bb_miiphy_bus is not necessary with wrappers added
in previous patch. Pass the ops pointer directly to both
bb_miiphy_read() and bb_miiphy_write() functions.
Signed-off-by: Marek Vasut
---
Cc: Jim Liu
Cc: Joe Hershberger
Cc: Mario
These functions are no longer necessary, remove them.
The struct bb_miiphy_bus is no longer necessary either,
remove it as well.
Signed-off-by: Marek Vasut
---
Cc: Jim Liu
Cc: Joe Hershberger
Cc: Mario Six
Cc: Michael Chang
Cc: Nobuhiro Iwamatsu
Cc: Parvathi Bhogaraju
Cc: Paul Barker
Cc: R
Inline mdio_init() back into mdio_alloc(), separate
access to mdio_init() is no longer necessary.
Signed-off-by: Marek Vasut
---
Cc: Jim Liu
Cc: Joe Hershberger
Cc: Mario Six
Cc: Michael Chang
Cc: Nobuhiro Iwamatsu
Cc: Parvathi Bhogaraju
Cc: Paul Barker
Cc: Ramon Fried
Cc: Tom Rini
Cc: u
Use mdio_alloc() again to allocate MDIO bus. This is possible
because all the miiphybb parameters and ops passing is handled in
at bb_miiphy_read()/bb_miiphy_write() level.
Signed-off-by: Marek Vasut
---
Cc: Jim Liu
Cc: Joe Hershberger
Cc: Mario Six
Cc: Michael Chang
Cc: Nobuhiro Iwamatsu
Cc
Use mdio_alloc() again to allocate MDIO bus. This is possible
because all the miiphybb parameters and ops passing is handled in
at bb_miiphy_read()/bb_miiphy_write() level.
This also fixes previously missed bb_miiphy_free() in .remove
callback of this driver. which does not pose a problem anymore.
Use mdio_alloc() again to allocate MDIO bus. This is possible
because all the miiphybb parameters and ops passing is handled in
at bb_miiphy_read()/bb_miiphy_write() level.
This also fixes previously missed bb_miiphy_free() in .remove
callback of this driver. which does not pose a problem anymore.
Use mdio_alloc() again to allocate MDIO bus. This is possible
because all the miiphybb parameters and ops passing is handled in
at bb_miiphy_read()/bb_miiphy_write() level.
This also fixes previously missed bb_miiphy_free() in .remove
callback of this driver. which does not pose a problem anymore.
Remove the priv member from struct bb_miiphy_bus and its assignment
from drivers. This turns struct bb_miiphy_bus int struct mii_dev
wrapper, to be cleaned up next.
Signed-off-by: Marek Vasut
---
Cc: Jim Liu
Cc: Joe Hershberger
Cc: Mario Six
Cc: Michael Chang
Cc: Nobuhiro Iwamatsu
Cc: Parvat
Do not call bb_miiphy_read()/bb_miiphy_write() accessors directly
in drivers, instead call them through wrapper functions. Those are
meant to be used as function parameter adaptation layer between
struct mii_dev callback function parameters and what the miiphybb
does expect and will soon expect. Th
On Fri, 14 Feb 2025 at 20:06, Fabio Estevam wrote:
> On Fri, Feb 14, 2025 at 3:55 PM Tom Rini wrote:
>
> > Applied to u-boot/next, thanks!
>
> The author's Signed-off-by tag is missing.
>
Maybe we need to add a CI check for sign-off's
On Thu, 27 Feb 2025 at 06:01, Anand Moon wrote:
> Hi Sebastian,
>
> On Thu, 27 Feb 2025 at 00:15, Sebastian Reichel
> wrote:
> >
> > Hi,
> >
> > I have a couple of fixes/improvements for the TCPM code. Three are fixing
> > actual problems I noticed on the Rock 5B, which prevented booting up the
On Fri, Feb 28, 2025 at 04:27:06PM +0100, Neil Armstrong wrote:
> Hi,
>
> On 06/02/2025 09:49, Neil Armstrong wrote:
> > Set the INCREASE_REGION_SIZE for the outbound iATU entry if it
> > causes the 4GB range overflow in order to activate the extended
> > limit address by means of an additional iA
On Wed, 26 Feb 2025 at 14:27, Raymond Mao wrote:
> HOSTCFLAGS of some tools components (image-host, rsa-sign and
> ecdsa-libcrypto) depend on the directory where openssl is installed.
> Add them via pkg-config.
> This fixes a potential build failure in tools when openssl in installed
> in varied
Hi,
On 3/1/25 04:39, Diederik de Haas wrote:
Hi,
The file ``test/lib/strlcat.c`` has "SPDX-License-Identifier: GPL-2.1+"
and that SPDX identifier doesn't exist.
As there is no indication this was a typo it needs to be relicensed by
the copyright holders AFAIK.
Cheers,
Diederik
As noted in
-rockchip.git
tags/u-boot-rockchip-20250301
for you to fetch changes up to a390c485756cf2b352ee781a94e47dafc7b9b2c8:
rockchip: nanopi-r3s-rk3566: disable unneeded CONFIG_NVME_PCI (2025-02-28
19:21:17 +0800)
Jonas Karlman (1
Siddharth Vadapalli writes:
> Introduce the config fragment for enabling USB MSC boot. USB MSC boot
> involves fetching the next stage of the bootloader from a USB Mass Storage
> device such as a USB Flash Drive with the USB controller on the SoC acting
> as the USB Host.
>
> Signed-off-by: Siddh
The GPL-2.1+ SPDX License Identifier doesn't exist, but luckily the full
license text was available which shows that GPL-2.1+ was a typo and it
should have been LGPL-2.1-or-later.
As the '+' in LGPL-2.1+ is deprecated in SPDX 3.0, use the preferred
identifier, which is '-or-later'.
Normally the fu
Hi,
The file ``test/lib/strlcat.c`` has "SPDX-License-Identifier: GPL-2.1+"
and that SPDX identifier doesn't exist.
As there is no indication this was a typo it needs to be relicensed by
the copyright holders AFAIK.
Cheers,
Diederik
signature.asc
Description: PGP signature
This device uses the SCSI subsystem to interface with SATA devices.
Trying to use the sata command results in an unhandled exception.
This has the side effect of also causing bootflow scan to raise
an unhandled exception when it attempts to probe the SATA
subsystem. Disabling the sata command fixes
On Fri, Feb 28, 2025 at 06:59:14PM -0600, Jon Humphreys wrote:
Hello Jon,
> Siddharth Vadapalli writes:
>
> > Introduce the config fragment for enabling USB MSC boot. USB MSC boot
> > involves fetching the next stage of the bootloader from a USB Mass Storage
> > device such as a USB Flash Drive
Hello,
This series adds config fragment for enabling USB MSC boot and USB
Storage devices which are applicable to AM62, AM62A and AM62P SoCs.
Series is based on commit
962217d218c Merge patch series "boards: siemens: iot2050: SM variant, sysinfo
support, fixes & cleanups"
of the next branch of U
Introduce the config fragment for enabling USB MSC boot. USB MSC boot
involves fetching the next stage of the bootloader from a USB Mass Storage
device such as a USB Flash Drive with the USB controller on the SoC acting
as the USB Host.
Signed-off-by: Siddharth Vadapalli
---
v1 of this patch is
Introduce the config fragment for enabling USB MSC boot. USB MSC boot
involves fetching the next stage of the bootloader from a USB Mass Storage
device such as a USB Flash Drive with the USB controller on the SoC acting
as the USB Host.
Signed-off-by: Siddharth Vadapalli
---
v1 of this patch is
26 matches
Mail list logo
