From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH net-next] net: phy: meson-gxl: cleanup by defining the control registers
Date: Tue, 05 Dec 2017 19:47:14 +0100 [thread overview]
Message-ID: <1512499634.21892.6.camel@baylibre.com> (raw)
In-Reply-To: <20171205180142.GS12805@lunn.ch>
On Tue, 2017-12-05 at 19:01 +0100, Andrew Lunn wrote:
> On Tue, Dec 05, 2017 at 10:33:34AM +0100, Jerome Brunet wrote:
> > From: Neil Armstrong <narmstrong@baylibre.com>
> >
> > Define registers and bits in meson-gxl PHY driver to make a bit
> > more human friendly. No functional change
>
>
> > static int meson_gxl_config_init(struct phy_device *phydev)
> > {
> > - /* Enable Analog and DSP register Bank access by */
> > - phy_write(phydev, 0x14, 0x0000);
> > - phy_write(phydev, 0x14, 0x0400);
> > - phy_write(phydev, 0x14, 0x0000);
> > - phy_write(phydev, 0x14, 0x0400);
> > + int ret;
> >
> > - /* Write Analog register 23 */
> > - phy_write(phydev, 0x17, 0x8E0D);
> > - phy_write(phydev, 0x14, 0x4417);
> > + /* Write PLL Configuration 1 */
> > + ret = meson_gxl_write_reg(phydev, BANK_ANALOG_DSP, A6_CONFIG_REG,
> > + A6_CONFIG_PLLMULX4ICH |
> > + FIELD_PREP(A6_CONFIG_PLLBUFITRIM, 7) |
> > + A6_CONFIG_PLLRSTVCOPD |
> > + A6_CONFIG_PLLCPOFF |
> > + A6_CONFIG_PLL_SRC);
> > + if (ret)
> > + return ret;
>
> This does not look like "No functional Change".
>
> Please can you break this up. First make use of #defines.
> That should be a clear "No functional Change".
>
> Then a second patch adding a helper for banked registers?
Sure, It would be better.
I also noticed that the write function was inlined which is probably not good.
>
> Thanks
> Andrew
prev parent reply other threads:[~2017-12-05 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 9:33 [PATCH net-next] net: phy: meson-gxl: cleanup by defining the control registers Jerome Brunet
2017-12-05 15:23 ` Yixun Lan
2017-12-05 15:57 ` Jerome Brunet
2017-12-05 18:01 ` Andrew Lunn
2017-12-05 18:47 ` Jerome Brunet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1512499634.21892.6.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linus-amlogic@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).