From: Vinod Koul <vkoul@kernel.org>
To: Dave Jiang <dave.jiang@intel.com>
Cc: dmaengine@vger.kernel.org
Subject: Re: [PATCH] dmaengine: fix channel index enumeration
Date: Mon, 27 Apr 2020 21:27:02 +0530 [thread overview]
Message-ID: <20200427155702.GE56386@vkoul-mobl.Dlink> (raw)
In-Reply-To: <158679961260.7674.8485924270472851852.stgit@djiang5-desk3.ch.intel.com>
On 13-04-20, 10:40, Dave Jiang wrote:
> When the channel register code was changed to allow hotplug operations,
> dynamic indexing wasn't taken into account. When channels are randomly
> plugged and unplugged out of order, the serial indexing breaks. Convert
> channel indexing to using IDA tracking in order to allow dynamic
> assignment. The previous code does not cause any regression bug for
> existing channel allocation besides idxd driver since the hotplug usage
> case is only used by idxd at this point.
>
> With this change, the chan->idr_ref is also not needed any longer. We can
> have a device with no channels registered due to hot plug. The channel
> device release code no longer should attempt to free the dma device id on
> the last channel release.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2020-04-27 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 17:40 [PATCH] dmaengine: fix channel index enumeration Dave Jiang
2020-04-23 14:17 ` Dave Jiang
2020-04-27 15:57 ` Vinod Koul [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=20200427155702.GE56386@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
/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