From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "Thierry Reding" <thierry.reding@gmail.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
linux-pwm@vger.kernel.org,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v2] pwm: lpss: Make builtin so that i915 can find the pwm_backlight
Date: Fri, 20 Jan 2017 11:55:19 +0200 [thread overview]
Message-ID: <20170120095519.GF17297@lahna.fi.intel.com> (raw)
In-Reply-To: <8737gei2fp.fsf@intel.com>
On Fri, Jan 20, 2017 at 10:02:50AM +0200, Jani Nikula wrote:
> That said, I suppose there could be an alternative to handling pwm_get()
> failures at probe. We could just go on with our init, but schedule a
> retry later. Perhaps a bit hacky, but it would address both of the
> concerns above. Again, this patch seems a simple workaround in the mean
> time.
Not sure if this works or how hacky it is, but can't you
request_module() before you start looking up for the pwm?
next prev parent reply other threads:[~2017-01-20 9:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 17:58 [PATCH v2] pwm: lpss: Make builtin so that i915 can find the pwm_backlight Hans de Goede
2017-01-20 7:03 ` Thierry Reding
2017-01-20 7:18 ` Thierry Reding
2017-01-20 7:50 ` Hans de Goede
2017-01-20 8:02 ` Jani Nikula
2017-01-20 8:56 ` Thierry Reding
2017-01-20 9:48 ` Hans de Goede
2017-01-20 9:55 ` Andy Shevchenko
2017-01-20 10:18 ` Hans de Goede
2017-01-20 10:42 ` Thierry Reding
2017-01-22 16:21 ` Hans de Goede
2017-01-20 9:58 ` Thierry Reding
2017-01-20 9:55 ` Mika Westerberg [this message]
2017-03-08 9:40 ` Jani Nikula
2017-03-08 9:48 ` Hans de Goede
2017-03-08 10:15 ` Jani Nikula
2017-03-08 13:41 ` Hans de Goede
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=20170120095519.GF17297@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=ville.syrjala@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