[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160711081451.GX28305@atomide.com>
Date: Mon, 11 Jul 2016 01:14:52 -0700
From: Tony Lindgren <tony@...mide.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: netdev@...r.kernel.org, "David S . Miller" <davem@...emloft.net>,
Steve Glendinning <steve.glendinning@...c.com>,
Guenter Roeck <linux@...ck-us.net>,
Jeremy Linton <jeremy.linton@....com>,
Kamlakant Patel <kamlakant.patel@...adcom.com>,
Pavel Fedin <p.fedin@...sung.com>,
Sudeep Holla <sudeep.holla@....com>,
Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
John Stultz <john.stultz@...aro.org>,
linux-omap@...r.kernel.org
Subject: Re: [PATCH 3/3] RFC: net: smsc911x: add wake-up event interrupt
support
* Linus Walleij <linus.walleij@...aro.org> [160708 02:10]:
> The SMSC911x have a line out of the chip called "PME",
> Power Management Event. When connected to an asynchronous
> interrupt controller this is able to wake the system up
> from sleep in response to certain network events.
Cool, so far have not found any boards here with that
connected. Should be possible to solder that on at least
omap3-evm at some point though.
> +static irqreturn_t smsc911x_pme_irq_thread(int irq, void *dev_id)
> +{
> + struct net_device *dev = dev_id;
> + struct smsc911x_data *pdata __maybe_unused = netdev_priv(dev);
> +
> + SMSC_TRACE(pdata, pm, "wakeup event");
> + /* This signal is active for 50 ms, wait for it to deassert */
> + usleep_range(50000, 100000);
> + return IRQ_HANDLED;
> +}
This probably adds an extra 50 ms latency before we wake up
the smsc911x driver. Maybe we can eventually come up with
some nice solution to that too. Anyways, no objections on
my side for this patch as it provides a nice GPIO wakeirq test
case that can be automated with just ping -c 1 :)
Regards,
Tony
Powered by blists - more mailing lists