linux-pwm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Chew Chiau Ee <chiau.ee.chew@intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Alan Cox <alan@linux.intel.com>,
	linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] pwm_lpss: Add support for PCI devices
Date: Thu, 17 Apr 2014 12:16:43 +0100	[thread overview]
Message-ID: <20140417121643.2c07ecfc@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <20140417110756.GB32603@ulmo>

> > +static int pci_drv, plat_drv;	/* So we know which drivers registered */
> 
> I think that rather than having everything in a single file, perhaps a
> better approach would be to keep pwm-lpss.c as a common module and then
> have separate drivers for ACPI (pwm-lpss-acpi) and PCI (pwm-lpss-pci).
> That way you don't have to keep track of which driver was successfully
> registered.

It would then take up 16K for a tiny trivial piece of code

> Would that work?

Badly

> > +static const struct pwm_lpss_boardinfo byt_info = {
> 
> What does byt_ stand for?

Baytrail.

> > -static int pwm_lpss_probe(struct platform_device *pdev)
> > +static struct pwm_lpss_chip *pwm_lpss_probe(struct device *dev,
> > +			struct resource *r, struct pwm_lpss_boardinfo *info)
> 
> Indentation is odd here. Please align arguments one subsequent lines
> with those of the first.

That doesn't appear to be present in CodingStyle or indeed most of the
kernel.

> > -static struct platform_driver pwm_lpss_driver = {
> > +static int pwm_lpss_probe_pci(struct pci_dev *pdev,
> > +			      const struct pci_device_id *id)
> > +{
> > +	struct pwm_lpss_boardinfo *info;
> 
> I think this should be const to mirror the type of the byt_info
> variable.

Agreed

Alan

  reply	other threads:[~2014-04-17 11:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 18:18 [PATCH v2] pwm_lpss: Add support for PCI devices Chew Chiau Ee
2014-04-17  7:49 ` Mika Westerberg
2014-04-17 11:08 ` Thierry Reding
2014-04-17 11:16   ` One Thousand Gnomes [this message]
2014-04-17 11:34     ` Thierry Reding
2014-04-17 12:45       ` One Thousand Gnomes

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=20140417121643.2c07ecfc@alan.etchedpixels.co.uk \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=alan@linux.intel.com \
    --cc=chiau.ee.chew@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=thierry.reding@gmail.com \
    /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).