netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: David.Choi@Micrel.Com
Cc: horms@verge.net.au, netdev@vger.kernel.org, Charles.Li@Micrel.Com
Subject: Re: [PATCH linux-2.6.35-rc3] ks8842 driver
Date: Thu, 08 Jul 2010 21:41:01 -0700 (PDT)	[thread overview]
Message-ID: <20100708.214101.39178389.davem@davemloft.net> (raw)
In-Reply-To: <C43529A246480145B0A6D0234BDB0F0D481D67@MELANITE.micrel.com>

From: "Choi, David" <David.Choi@Micrel.Com>
Date: Thu, 8 Jul 2010 12:01:51 -0700

> The original ks8842 driver is designed to work on the customized bus
> interface based on an FPGA. This patch is intended to address the more
> commonly used generic bus interface available on the majority of SoC in
> the market.
> 
> It is unlikely that for a system to use both FPGA based and generic bus
> interface for ks8842, I am quite certain that those 2 devices are used
> mutual exclusively.

Like Simon, I'm not to thrilled with this approach.

Any flag bit test you'd need to add to the driver to handle both cases
will have zero performance impact since the cost of the MMIO accesses
will dominate such tests entirely.

Add a boolean flag bit to the driver software state, set it based upon
some platform_device private setting, and test it in these paths to
device what to do.

As a bonus, anyone who enables this driver at all in their build will
test the compilation of both code paths.  And to me, that extra
compilation testing trumps whatever arguments you may make for not
making this support dynamic.

Thanks.

  parent reply	other threads:[~2010-07-09  4:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 15:24 [PATCH linux-2.6.35-rc3] ks8842 driver Choi, David
2010-07-08  7:52 ` Simon Horman
2010-07-08 19:01   ` Choi, David
2010-07-09  2:40     ` Simon Horman
2010-07-09  4:41     ` David Miller [this message]
2010-07-09  6:08       ` Simon Horman
2010-07-09 21:22         ` [PATCH v2 " Choi, David
2010-07-10  0:25           ` Simon Horman
2010-07-12 19:56           ` 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=20100708.214101.39178389.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Charles.Li@Micrel.Com \
    --cc=David.Choi@Micrel.Com \
    --cc=horms@verge.net.au \
    --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 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).