On Wed, Aug 14, 2019 at 12:09 PM Nevo Hed wrote:
>
> On Wed, Aug 14, 2019 at 11:39 AM Joe Hershberger
> wrote:
> >
> > On Fri, Aug 2, 2019 at 12:54 PM wrote:
> > >
> > > From: Ken Ma
> > >
>
> > > -
> > > -static int mvpp2_recv(struct udevice *dev, int flags, uchar **packetp)
> > > +int mvpp2_r
On Wed, Aug 14, 2019 at 11:39 AM Joe Hershberger
wrote:
>
> On Fri, Aug 2, 2019 at 12:54 PM wrote:
> >
> > From: Ken Ma
> >
> > -
> > -static int mvpp2_recv(struct udevice *dev, int flags, uchar **packetp)
> > +int mvpp2_recv(struct udevice *dev, int flags, uchar **packetp)
>
> Why does this ne
On Fri, Aug 2, 2019 at 12:54 PM wrote:
>
> From: Ken Ma
>
> Since marvell MDIO driver is added, SMI function implementation in
> mvpp2 driver can be removed and NETA driver can use marvell MDIO API
> directly.
> This replacement also fixes 2 old issues:
> 1. Each pp2 port device should have its o
From: Ken Ma
Since marvell MDIO driver is added, SMI function implementation in
mvpp2 driver can be removed and NETA driver can use marvell MDIO API
directly.
This replacement also fixes 2 old issues:
1. Each pp2 port device should have its own mdio bus field member since
some pp2 ports may us
4 matches
Mail list logo