[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200414183652.GB637127@lunn.ch>
Date: Tue, 14 Apr 2020 20:36:52 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Robert Marko <robert.marko@...tura.hr>
Cc: f.fainelli@...il.com, hkallweit1@...il.com, linux@...linux.org.uk,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
robh+dt@...nel.org, Mark Rutland <mark.rutland@....com>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
devicetree@...r.kernel.org,
Christian Lamparter <chunkeey@...il.com>,
Luka Perkov <luka.perkov@...tura.hr>
Subject: Re: [PATCH 1/3] net: phy: mdio: add IPQ40xx MDIO driver
> Unfortunately, I don't have access to documentation and this is all based on
> GPL code from Qualcomm's SDK.
> So I don't really know whats their purpose.
Then please try to reverse engineer it. Just looking at the code, it
seems like one register is read, and the other is write. So use that
in the name.
> No, this is also an old relic from the SDK driver.
> It works without this perfectly fine, so I will drop it from v2.
Part of cleaning up 'Vendor Crap' is throwing out all the stuff like
this. What you end up with should be something you would of been happy
to write yourself.
> > Why the name am? Generally priv is used. I could also understand bus,
> > or even data, but am?
> Like most stuff in this driver, its a leftover from the SDK driver.
I guessed as much. But this is the sort of thing you need to fix when
cleaning up 'vendor crap'.
Andrew
Powered by blists - more mailing lists