Linux PWM subsystem development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-pwm@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 1/2] pinctrl: intel: Import namespace for pwm_lpss function
Date: Mon, 3 Feb 2025 17:19:40 +0200	[thread overview]
Message-ID: <Z6DejKRkxa1XCc5E@smile.fi.intel.com> (raw)
In-Reply-To: <yynjwr57jf4ytixfo2c6bojo5ib5plue7krlwzb64rxrfuqghy@u4pkkktbe7b3>

On Thu, Jan 23, 2025 at 05:30:07PM +0100, Uwe Kleine-König wrote:
> On Thu, Jan 23, 2025 at 05:48:17PM +0200, Andy Shevchenko wrote:
> > On Thu, Jan 23, 2025 at 03:52:06PM +0100, Uwe Kleine-König wrote:
> > > On Thu, Jan 23, 2025 at 01:45:17PM +0200, Andy Shevchenko wrote:
> > > > On Thu, Jan 23, 2025 at 12:11 PM Uwe Kleine-König
> > > > <u.kleine-koenig@baylibre.com> wrote:
> > > > >
> > > > > The intel pinctrl driver can provide a PWM device and for that needs to
> > > > > call the function devm_pwm_lpss_probe(). That function is provided by
> > > > > the pwm-lpss driver which intends to export it in the "PWM_LPSS"
> > > > > namespace. To prepare fixing the pwm-lpss driver to indeed use the
> > > > > "PWM_LPSS" namespace, import that namespace when used.

...

> > > > > +#if IS_REACHABLE(CONFIG_PWM_LPSS)
> > > > 
> > > > > +#endif
> > > > 
> > > > Why?
> > > 
> > > Because devm_pwm_lpss_probe() is only used #if
> > > IS_REACHABLE(CONFIG_PWM_LPSS). Without the #if but with
> > > https://lore.kernel.org/all/20250123110951.370759-2-u.kleine-koenig@baylibre.com/
> > > this results in a warning (with W=1) :-)
> > 
> > There is no such commit in the current Linux Next, so let's solve the issues
> > when they come up.
> > 
> > I'm okay to take your series via Intel pin control without that ifdeffery.
> > If you don't agree on the change, we need to find the way how to avoid ugly
> > ifdeffery from day 1.
> 
> I'm ok with dropping the #if. Should I resend or do you want to edit the
> patch? Would you take both patches then?

I can take both. No need to resend.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-02-03 15:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 10:11 [PATCH v2 0/2] pwm: lpss: module namespace fixes Uwe Kleine-König
2025-01-23 10:11 ` [PATCH v2 1/2] pinctrl: intel: Import namespace for pwm_lpss function Uwe Kleine-König
2025-01-23 11:45   ` Andy Shevchenko
2025-01-23 14:52     ` Uwe Kleine-König
2025-01-23 15:48       ` Andy Shevchenko
2025-01-23 16:30         ` Uwe Kleine-König
2025-02-03 15:19           ` Andy Shevchenko [this message]
2025-01-23 10:11 ` [PATCH v2 2/2] pwm: lpss: Actually use a module namespace by defining the namespace earlier Uwe Kleine-König
2025-01-23 11:46 ` [PATCH v2 0/2] pwm: lpss: module namespace fixes Andy Shevchenko
2025-02-03 15:25 ` Andy Shevchenko

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=Z6DejKRkxa1XCc5E@smile.fi.intel.com \
    --to=andy.shevchenko@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=u.kleine-koenig@baylibre.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