public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: wwang <wei_wang@realsil.com.cn>
Cc: devel@linuxdriverproject.org, gregkh@linuxfoundation.org,
	sameo@linux.intel.com, rogerable@realtek.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: rtsx: Modify rts5249_optimize_phy
Date: Thu, 5 Sep 2013 14:47:11 +0300	[thread overview]
Message-ID: <20130905114711.GM6329@mwanda> (raw)
In-Reply-To: <52286822.9090402@realsil.com.cn>

On Thu, Sep 05, 2013 at 07:16:50PM +0800, wwang wrote:
> 于 2013年09月05日 18:48, Dan Carpenter 写道:
> >On Thu, Sep 05, 2013 at 05:45:38PM +0800, wei_wang@realsil.com.cn wrote:
> >>From: Wei WANG <wei_wang@realsil.com.cn>
> >>
> >>In some platforms, specially Thinkpad series, rts5249 won't be
> >>initialized properly. So we need adjust some phy parameters to
> >>improve the compatibility issue.
> >>
> >>Signed-off-by: Wei WANG <wei_wang@realsil.com.cn>
> >>---
> >>  drivers/mfd/rts5249.c |   25 +++++++++++++++++++++++--
> >>  1 file changed, 23 insertions(+), 2 deletions(-)
> >>
> >>diff --git a/drivers/mfd/rts5249.c b/drivers/mfd/rts5249.c
> >>index 3b835f5..e3c6dc1 100644
> >>--- a/drivers/mfd/rts5249.c
> >>+++ b/drivers/mfd/rts5249.c
> >>@@ -130,13 +130,34 @@ static int rts5249_optimize_phy(struct rtsx_pcr *pcr)
> >>  {
> >>  	int err;
> >>-	err = rtsx_pci_write_phy_register(pcr, PHY_REG_REV, 0xFE46);
> >>+	err = rtsx_pci_write_phy_register(pcr, PHY_REG_REV, 0xFC6C);
> >
> >How are we supposed to review this change?  What happened to 0xFE46?
> >What are all these magic numbers?  I understand that this fixes an issue
> >for think pads but does it break something else?
> >
> >regards,
> >dan carpenter
> >
> >.
> >
> Hi Dan:
> 
> These numbers are used to configure the parameters of our internal
> analog circuit. Those new values have been tested for quite a long
> time with our Windows driver. So it's guaranteed and won't break
> other platforms.
> 

Give them human readable names so we at least have some idea about what
they are trying to do.

regards,
dan carpenter


  reply	other threads:[~2013-09-05 11:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05  9:45 [PATCH] mfd: rtsx: Modify rts5249_optimize_phy wei_wang
2013-09-05 10:48 ` Dan Carpenter
2013-09-05 11:16   ` wwang
2013-09-05 11:47     ` Dan Carpenter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-09-10  9:09 wei_wang
2013-09-10  9:11 ` wwang
2013-09-10  9:45   ` Lee Jones

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=20130905114711.GM6329@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rogerable@realtek.com \
    --cc=sameo@linux.intel.com \
    --cc=wei_wang@realsil.com.cn \
    /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