From: Clemens Ladisch <clemens@ladisch.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [RFC] dice: simplifying address registration
Date: Sat, 25 Apr 2015 10:49:56 +0200 [thread overview]
Message-ID: <553B5534.1060005@ladisch.de> (raw)
In-Reply-To: <553A3FC5.60809@sakamocchi.jp>
Takashi Sakamoto wrote:
> Currently Dice driver keeps address ranges for each unit instance. But
> there's a way to reuse the same address range.
This requires an additional check for the packet's source node, which is
essentially a duplicate of the core's address lookup code.
> I think this idea can simplify driver probe processing
Yes, but that code is just moved to the module load processing.
> and save resources of host controller.
When using multiple DICE devices, this saves four bytes of FireWire
address space per card, out of the total address space of 2^48 bytes.
Or what other resources do you mean?
Regards,
Clemens
next prev parent reply other threads:[~2015-04-25 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 13:06 [RFC] dice: simplifying address registration Takashi Sakamoto
2015-04-25 8:49 ` Clemens Ladisch [this message]
2015-04-25 12:25 ` Takashi Sakamoto
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=553B5534.1060005@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=o-takashi@sakamocchi.jp \
/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