From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Dan Murphy <dmurphy@ti.com>,
lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] dt-bindings: tas2562: Add firmware support for tas2563
Date: Thu, 18 Jun 2020 11:57:22 +0100 [thread overview]
Message-ID: <20200618105722.GA5789@sirena.org.uk> (raw)
In-Reply-To: <20200617220459.GA2884884@bogus>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
On Wed, Jun 17, 2020 at 04:04:59PM -0600, Rob Herring wrote:
> Given bus numbering may not be constant, that seems like not the best
> way to match up devices. I'd assume that userspace needs some way to
> identify which instance is which already, so maybe there's other data
> you can use already.
There isn't really, you're putting stuff in the DT for that - usually as
part of the card binding. I guess we could use that string rather than
the dev_name().
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-18 10:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 17:28 [RFC PATCH 0/2] TAS2563 DSP Firmware Loader Dan Murphy
2020-06-09 17:28 ` [RFC PATCH 1/2] dt-bindings: tas2562: Add firmware support for tas2563 Dan Murphy
2020-06-09 17:31 ` Mark Brown
2020-06-09 17:35 ` Dan Murphy
2020-06-09 17:58 ` Mark Brown
2020-06-09 18:06 ` Dan Murphy
2020-06-09 18:47 ` Mark Brown
2020-06-09 19:20 ` Dan Murphy
2020-06-10 10:29 ` Mark Brown
2020-06-10 14:12 ` Dan Murphy
2020-06-10 14:28 ` Mark Brown
2020-06-17 22:04 ` Rob Herring
2020-06-18 10:57 ` Mark Brown [this message]
2020-06-09 17:28 ` [RFC PATCH 2/2] ASoc: tas2563: DSP Firmware loading support Dan Murphy
2020-06-09 17:50 ` Mark Brown
2020-06-12 17:30 ` Dan Murphy
2020-06-12 17:46 ` Mark Brown
2020-06-09 17:52 ` [RFC PATCH 0/2] TAS2563 DSP Firmware Loader Mark Brown
2020-06-09 18:07 ` Dan Murphy
2020-06-09 18:16 ` Mark Brown
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=20200618105722.GA5789@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=tiwai@suse.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