netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	davem@davemloft.net
Cc: u.kleine-koenig@pengutronix.de, f.fainelli@gmail.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH] Revert "phy: add support for a reset-gpio specification"
Date: Thu, 19 May 2016 06:29:58 -0700	[thread overview]
Message-ID: <573DBFD6.2050508@roeck-us.net> (raw)
In-Reply-To: <b2763da7-575a-4d73-2997-4236173761bf@cogentembedded.com>

On 05/19/2016 06:11 AM, Sergei Shtylyov wrote:
> Hello.
>
> On 5/18/2016 7:05 PM, Fabio Estevam wrote:
>
>> Commit da47b4572056 ("phy: add support for a reset-gpio specification")
>> causes the following xtensa qemu crash according to Guenter Roeck:
>>
>> [    9.366256] libphy: ethoc-mdio: probed
>> [    9.367389]  (null): could not attach to PHY
>> [    9.368555]  (null): failed to probe MDIO bus
>> [    9.371540] Unable to handle kernel paging request at virtual address 0000001c
>> [    9.371540]  pc = d0320926, ra = 903209d1
>> [    9.375358] Oops: sig: 11 [#1]
>
>     Of course, I'd like this patch to be reverted (as it was applied erroneously instead of my patches)... but where's the backtrace? It's not immediately clear how this code can cause kernel oops...
>

See http://www.spinics.net/lists/kernel/msg2258611.html.

Guenter

>> This reverts commit da47b4572056487fd7941c26f73b3e8815ff712a.
>>
>> Reported-by: Guenter Roeck <linux@roeck-us.net>
>> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
> [...]
>> diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
>> index 307f72a..e977ba9 100644
>> --- a/drivers/net/phy/phy_device.c
>> +++ b/drivers/net/phy/phy_device.c
> [...]
>> @@ -1571,16 +1570,9 @@ static int phy_probe(struct device *dev)
>>      struct device_driver *drv = phydev->mdio.dev.driver;
>>      struct phy_driver *phydrv = to_phy_driver(drv);
>>      int err = 0;
>> -    struct gpio_descs *reset_gpios;
>>
>>      phydev->drv = phydrv;
>>
>> -    /* take phy out of reset */
>> -    reset_gpios = devm_gpiod_get_array_optional(dev, "reset",
>> -                            GPIOD_OUT_LOW);
>> -    if (IS_ERR(reset_gpios))
>> -        return PTR_ERR(reset_gpios);
>> -
>>      /* Disable the interrupt if the PHY doesn't support it
>>       * but the interrupt is still a valid one
>>       */
>
> MBR, Sergei
>
>

  reply	other threads:[~2016-05-19 13:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 16:05 [PATCH] Revert "phy: add support for a reset-gpio specification" Fabio Estevam
2016-05-18 16:52 ` Florian Fainelli
2016-05-18 19:54   ` Guenter Roeck
2016-05-19 13:11 ` Sergei Shtylyov
2016-05-19 13:29   ` Guenter Roeck [this message]
2016-05-19 17:11     ` Sergei Shtylyov
2016-05-19 18:09       ` Guenter Roeck
2016-05-20 21:57 ` David Miller

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=573DBFD6.2050508@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=fabio.estevam@nxp.com \
    --cc=netdev@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).