From: Thierry Reding <thierry.reding@gmail.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Chew Chiau Ee <chiau.ee.chew@intel.com>,
Alan Cox <alan@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pwm_lpss: Add support for PCI devices
Date: Tue, 13 May 2014 08:59:36 +0200 [thread overview]
Message-ID: <20140513065935.GA6754@ulmo> (raw)
In-Reply-To: <20140512231816.GA65896@dvhart-mac01.jf.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]
On Mon, May 12, 2014 at 04:18:16PM -0700, Darren Hart wrote:
> On Sat, Apr 12, 2014 at 09:58:51PM +0800, Chew Chiau Ee wrote:
> > From: Alan Cox <alan@linux.intel.com>
> >
> > Not all systems enumerate the PWM devices via ACPI. They can also be exposed
> > via the PCI interface.
> >
> > Signed-off-by: Alan Cox <alan@linux.intel.com>
> > Signed-off-by: Chew, Chiau Ee <chiau.ee.chew@intel.com>
> > ---
> > drivers/pwm/pwm-lpss.c | 160 ++++++++++++++++++++++++++++++++++++++---------
> > 1 files changed, 129 insertions(+), 31 deletions(-)
[...]
> Has this landed anywhere? I didn't see it in mainline or next, am I looking in
> the wrong place?
This was applied to the pwm/for-next tree and has been in linux-next
since next-20140429.
> If it's just still pending, I ran into one issue integrating it
> with 3.14.2:
>
> CC [M] drivers/pwm/pwm-lpss.o
> drivers/pwm/pwm-lpss.c: In function ‘pwm_lpss_probe_pci’:
> drivers/pwm/pwm-lpss.c:192:2: warning: passing argument 3 of ‘pwm_lpss_probe’
> discards ‘const’ qualifier from pointer target type [enabled by default]
> drivers/pwm/pwm-lpss.c:130:30: note: expected ‘struct pwm_lpss_boardinfo *’
> but argument is of type ‘const struct pwm_lpss_boardinfo *’
>
> Can we make the third argument to pwm_lpss_probe a const? The following is
> working for me:
>
> static struct pwm_lpss_chip *pwm_lpss_probe(struct device *dev,
> struct resource *r,
> const struct pwm_lpss_boardinfo *info)
A fix like that was applied last week and is in next-20140512.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-05-13 7:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 13:58 [PATCH] pwm_lpss: Add support for PCI devices Chew Chiau Ee
2014-04-13 10:32 ` Li, Aubrey
2014-04-14 2:05 ` Chew, Chiau Ee
2014-04-14 8:59 ` Mika Westerberg
2014-04-15 8:59 ` Chew, Chiau Ee
2014-04-14 8:18 ` Mika Westerberg
2014-04-15 8:41 ` Chew, Chiau Ee
2014-04-15 9:03 ` Mika Westerberg
2014-04-15 9:06 ` Chew, Chiau Ee
2014-05-12 23:18 ` Darren Hart
2014-05-13 6:59 ` Thierry Reding [this message]
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=20140513065935.GA6754@ulmo \
--to=thierry.reding@gmail.com \
--cc=alan@linux.intel.com \
--cc=chiau.ee.chew@intel.com \
--cc=dvhart@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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).