All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raanan Avargil <raanan.avargil@intel.com>
To: Denis Turischev <denis.turischev@compulab.co.il>,
	intel-wired-lan@lists.osuosl.org, "Brown,
	Aaron F" <aaron.f.brown@intel.com>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] e1000e: PHY cann't be initialized correctly on some I218 controllers
Date: Tue, 9 Aug 2016 18:10:53 +0300	[thread overview]
Message-ID: <f9d596bd-226b-0faf-bab1-858823f17ee4@intel.com> (raw)
In-Reply-To: <57A6F7A9.1030401@compulab.co.il>



On 8/7/2016 11:56, Denis Turischev wrote:
> Hi Raanan,
>
> On 08/04/2016 07:18 PM, Raanan Avargil wrote:
>> It is hard to determine what is exactly the problem here and what causes the -3 error, but this is not the place to perform hw reset and retry to init the phy.
> I agree that may be this is not the correct place for hw reset, can you advice about another solution?
>
> It works, not only for me, for example it helps here:
> http://www.linux.org.ru/forum/linux-hardware/10268216
>
> Another fact that Windows drivers work fine with the same hw.
>
> Denis
>

Hi Denis,

More suitable place to retry init the device would be in probe function.
However, we haven't seen initialization issues like this on i218.

Adding Aaron.

@Aaron - have you seen initialization errors on i218 devices?

Raanan
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

WARNING: multiple messages have this Message-ID (diff)
From: Raanan Avargil <raanan.avargil@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] e1000e: PHY cann't be initialized correctly on some I218 controllers
Date: Tue, 9 Aug 2016 18:10:53 +0300	[thread overview]
Message-ID: <f9d596bd-226b-0faf-bab1-858823f17ee4@intel.com> (raw)
In-Reply-To: <57A6F7A9.1030401@compulab.co.il>



On 8/7/2016 11:56, Denis Turischev wrote:
> Hi Raanan,
>
> On 08/04/2016 07:18 PM, Raanan Avargil wrote:
>> It is hard to determine what is exactly the problem here and what causes the -3 error, but this is not the place to perform hw reset and retry to init the phy.
> I agree that may be this is not the correct place for hw reset, can you advice about another solution?
>
> It works, not only for me, for example it helps here:
> http://www.linux.org.ru/forum/linux-hardware/10268216
>
> Another fact that Windows drivers work fine with the same hw.
>
> Denis
>

Hi Denis,

More suitable place to retry init the device would be in probe function.
However, we haven't seen initialization issues like this on i218.

Adding Aaron.

@Aaron - have you seen initialization errors on i218 devices?

Raanan
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


  reply	other threads:[~2016-08-09 15:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01 12:28 e1000e: PHY cann't be initialized correctly on some I218 controllers Denis Turischev
2016-08-01 12:28 ` [Intel-wired-lan] " Denis Turischev
2016-08-04 16:18 ` Raanan Avargil
2016-08-04 16:18   ` Raanan Avargil
2016-08-07  8:56   ` Denis Turischev
2016-08-07  8:56     ` Denis Turischev
2016-08-09 15:10     ` Raanan Avargil [this message]
2016-08-09 15:10       ` Raanan Avargil
2016-08-09 18:59       ` Brown, Aaron F
2016-08-09 18:59         ` Brown, Aaron F
2016-08-10 15:00         ` Neftin, Sasha
2016-08-10 15:00           ` Neftin, Sasha

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=f9d596bd-226b-0faf-bab1-858823f17ee4@intel.com \
    --to=raanan.avargil@intel.com \
    --cc=aaron.f.brown@intel.com \
    --cc=denis.turischev@compulab.co.il \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.