[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANEJEGuiw7w0aV47AnRQGzqBNCyAb7jj9t+Dh2XbzwMtV=doWw@mail.gmail.com>
Date: Mon, 9 Jul 2012 10:45:28 -0700
From: Grant Grundler <grundler@...omium.org>
To: Christian Riesch <christian.riesch@...cron.at>
Cc: netdev@...r.kernel.org, Oliver Neukum <oneukum@...e.de>,
Eric Dumazet <edumazet@...gle.com>,
Allan Chou <allan@...x.com.tw>,
Mark Lord <kernel@...savvy.com>,
Ming Lei <tom.leiming@...il.com>,
Michael Riesch <michael@...sch.at>
Subject: Re: [PATCH 0/4] Add a driver for the ASIX AX88172A
Christian,
Here's my $0.02 response to your questions.
On Fri, Jul 6, 2012 at 4:33 AM, Christian Riesch
<christian.riesch@...cron.at> wrote:
...
> I have a few questions:
>
> 1) Is it ok to factor out the common code like I did? Or should
> it go into a separate kernel module?
I think it's ok. I'd rather not see additional kernel modules unless
the driver is substantially different.
> 2) phylib/usbnet: Currently I have an empty .status function
> in my const struct driver_info ax88172a_info. I think this
> notifies me of a link change, right? I don't know
> what I should do in this function. Trigger the phy state machine
> like a phy interrupt would do, since link changes are handled
> by the phy state machine?
I don't see any Documentation for this entry point. My reading of the
code is driver_info->status (include/linux/usb/usbnet.h) is to poll
current link status from URBs. See usbnet_probe() (calls
init_status()) and intr_complete() (calls your stub). I also looked
at usbnet_cdc_status() in cdc_ethernet.c. Maybe other drivers are
better examples.
hth,
grant
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists