From: Vinod Koul <vkoul@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
linux-kernel@vger.kernel.org, patches@opensource.cirrus.com,
rdunlap@infradead.org
Subject: Re: [PATCH] soundwire: bus: Make IRQ handling conditionally built
Date: Wed, 20 Sep 2023 15:50:01 +0200 [thread overview]
Message-ID: <ZQr4iYRmDppFJS0w@matsya> (raw)
In-Reply-To: <20230920085133.GE103419@ediswmail.ad.cirrus.com>
On 20-09-23, 08:51, Charles Keepax wrote:
> On Wed, Sep 20, 2023 at 09:05:13AM +0200, Vinod Koul wrote:
> > On 18-09-23, 17:10, Charles Keepax wrote:
> > > SoundWire has provisions for a simple callback for the IRQ handling so
> > > has no hard dependency on IRQ_DOMAIN, but the recent addition of IRQ
> > > handling was causing builds without IRQ_DOMAIN to fail. Resolve this by
> > > moving the IRQ handling into its own file and only add it to the build
> > > when IRQ_DOMAIN is included in the kernel.
> > >
> > > Fixes: 12a95123bfe1 ("soundwire: bus: Allow SoundWire peripherals to register IRQ handlers")
> > > Reported-by: kernel test robot <lkp@intel.com>
> > > Closes: https://lore.kernel.org/oe-kbuild-all/202309150522.MoKeF4jx-lkp@intel.com/
> > > Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
> > > ---
> > > drivers/soundwire/Makefile | 4 +++
> > > drivers/soundwire/bus.c | 31 +++----------------
> > > drivers/soundwire/bus_type.c | 11 +++----
> > > drivers/soundwire/irq.c | 59 ++++++++++++++++++++++++++++++++++++
> > > drivers/soundwire/irq.h | 43 ++++++++++++++++++++++++++
> > > 5 files changed, 115 insertions(+), 33 deletions(-)
> > > create mode 100644 drivers/soundwire/irq.c
> > > create mode 100644 drivers/soundwire/irq.h
> > >
> > > diff --git a/drivers/soundwire/Makefile b/drivers/soundwire/Makefile
> > > index c3d3ab3262d3a..657f5888a77b0 100644
> > > --- a/drivers/soundwire/Makefile
> > > +++ b/drivers/soundwire/Makefile
> > > @@ -15,6 +15,10 @@ ifdef CONFIG_DEBUG_FS
> > > soundwire-bus-y += debugfs.o
> > > endif
> > >
> > > +ifdef CONFIG_IRQ_DOMAIN
> > > +soundwire-bus-y += irq.o
> > > +endif
> >
> > Any reason why we cant use depends for this?
> >
>
> No reason we can't, but my thinking was really that SoundWire doesn't
> really have a dependency on IRQ_DOMAIN, as you can use the original
> callback mechanism. It seemed a shame to force it as a dependency,
> when the whole subsystem can function happily without it.
>
> That said, I am happy to switch to a simple dependency if you prefer?
> It would certainly be a much simpler change.
That is very valid point, not every user needs it... I guess lets go
with this change now, can you fix the comment style and we can merge
this
--
~Vinod
next prev parent reply other threads:[~2023-09-20 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 16:10 [PATCH] soundwire: bus: Make IRQ handling conditionally built Charles Keepax
2023-09-18 18:55 ` Randy Dunlap
2023-09-20 7:05 ` Vinod Koul
2023-09-20 8:51 ` Charles Keepax
2023-09-20 13:50 ` Vinod Koul [this message]
2023-09-20 13:56 ` Charles Keepax
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=ZQr4iYRmDppFJS0w@matsya \
--to=vkoul@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rdunlap@infradead.org \
--cc=sanyog.r.kale@intel.com \
--cc=yung-chuan.liao@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.