From: Mark Brown <broonie@kernel.org> To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>, Thomas Petazzoni <thomas.petazzoni@free-electrons.com>, Mark Rutland <mark.rutland@arm.com>, Jean-Francois Moine <moinejf@free.fr>, Jason Cooper <jason@lakedaemon.net>, Pawel Moll <pawel.moll@arm.com>, devicetree@vger.kernel.org, Stephen Warren <swarren@wwwdotorg.org>, linux-kernel@vger.kernel.org, Rob Herring <rob.herring@calxeda.com>, Gregory CLEMENT <gregory.clement@free-electrons.com>, linux-arm-kernel@lists.infradead.org, Ian Campbell <ian.campbell@citrix.com>, liam.r.girdwood@intel.com Subject: Re: [PATCH 1/2] ARM: Dove: Add the audio devices in DT Date: Thu, 29 Aug 2013 19:20:11 +0100 [thread overview] Message-ID: <20130829182010.GQ10783@sirena.org.uk> (raw) In-Reply-To: <521F8CB3.5060407@gmail.com> [-- Attachment #1: Type: text/plain, Size: 998 bytes --] On Thu, Aug 29, 2013 at 08:02:27PM +0200, Sebastian Hesselbarth wrote: > > it is referring the same differences Russell already mentioned. But I > already came to the conclusion, that we don't need the information in > the binding. For example, if you use that controller on Dove and you > hook it up for SPDIF-in (which it hasn't), than I consider this a > DT bug. No need to double-check that in the driver. From that p-o-v, > please just let the current binding as is. OK, great - none of these devices have any differences which are visible only within the controller, they're all extra external interfaces? > Thomas Petazzoni mentioned earlier, that the _usual_ procedure to > name the compatibles is to pick the SoC that the IP appeared in first. > But I am also fine with "marvell,mvebu-audio" and adding compatibles > for dove or kirkwood _if_ we will ever need them. Yeah, it doesn't make much difference either way so long as the base name isn't utterly confusing. [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/2] ARM: Dove: Add the audio devices in DT Date: Thu, 29 Aug 2013 19:20:11 +0100 [thread overview] Message-ID: <20130829182010.GQ10783@sirena.org.uk> (raw) In-Reply-To: <521F8CB3.5060407@gmail.com> On Thu, Aug 29, 2013 at 08:02:27PM +0200, Sebastian Hesselbarth wrote: > > it is referring the same differences Russell already mentioned. But I > already came to the conclusion, that we don't need the information in > the binding. For example, if you use that controller on Dove and you > hook it up for SPDIF-in (which it hasn't), than I consider this a > DT bug. No need to double-check that in the driver. From that p-o-v, > please just let the current binding as is. OK, great - none of these devices have any differences which are visible only within the controller, they're all extra external interfaces? > Thomas Petazzoni mentioned earlier, that the _usual_ procedure to > name the compatibles is to pick the SoC that the IP appeared in first. > But I am also fine with "marvell,mvebu-audio" and adding compatibles > for dove or kirkwood _if_ we will ever need them. Yeah, it doesn't make much difference either way so long as the base name isn't utterly confusing. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130829/45a71d28/attachment.sig>
next prev parent reply other threads:[~2013-08-29 18:20 UTC|newest] Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-28 9:34 [PATCH 1/2] ARM: Dove: Add the audio devices in DT Jean-Francois Moine 2013-08-28 9:34 ` Jean-Francois Moine 2013-08-28 10:13 ` Sebastian Hesselbarth 2013-08-28 10:13 ` Sebastian Hesselbarth 2013-08-28 10:13 ` Sebastian Hesselbarth 2013-08-28 10:19 ` Thomas Petazzoni 2013-08-28 10:19 ` Thomas Petazzoni 2013-08-28 10:19 ` Thomas Petazzoni 2013-08-28 10:26 ` Sebastian Hesselbarth 2013-08-28 10:26 ` Sebastian Hesselbarth 2013-08-28 10:26 ` Sebastian Hesselbarth 2013-08-28 11:15 ` Thomas Petazzoni 2013-08-28 11:15 ` Thomas Petazzoni 2013-08-28 11:44 ` Sebastian Hesselbarth 2013-08-28 11:44 ` Sebastian Hesselbarth 2013-08-28 11:58 ` Thomas Petazzoni 2013-08-28 11:58 ` Thomas Petazzoni 2013-08-28 12:13 ` Russell King - ARM Linux 2013-08-28 12:13 ` Russell King - ARM Linux 2013-08-28 12:29 ` Thomas Petazzoni 2013-08-28 12:29 ` Thomas Petazzoni 2013-08-28 12:42 ` Russell King - ARM Linux 2013-08-28 12:42 ` Russell King - ARM Linux 2013-08-28 12:51 ` Thomas Petazzoni 2013-08-28 12:51 ` Thomas Petazzoni 2013-08-28 13:58 ` Russell King - ARM Linux 2013-08-28 13:58 ` Russell King - ARM Linux 2013-08-28 12:16 ` Sebastian Hesselbarth 2013-08-28 12:16 ` Sebastian Hesselbarth 2013-08-29 10:07 ` Jean-Francois Moine 2013-08-29 10:07 ` Jean-Francois Moine 2013-08-29 10:13 ` Russell King - ARM Linux 2013-08-29 10:13 ` Russell King - ARM Linux 2013-08-29 11:01 ` Sebastian Hesselbarth 2013-08-29 11:01 ` Sebastian Hesselbarth 2013-08-30 15:08 ` Russell King - ARM Linux 2013-08-30 15:08 ` Russell King - ARM Linux 2013-08-29 9:46 ` Jean-Francois Moine 2013-08-29 9:46 ` Jean-Francois Moine 2013-08-29 16:12 ` Mark Brown 2013-08-29 16:12 ` Mark Brown 2013-08-29 16:33 ` Russell King - ARM Linux 2013-08-29 16:33 ` Russell King - ARM Linux 2013-08-29 17:12 ` Mark Brown 2013-08-29 17:12 ` Mark Brown 2013-08-29 18:02 ` Sebastian Hesselbarth 2013-08-29 18:02 ` Sebastian Hesselbarth 2013-08-29 18:20 ` Mark Brown [this message] 2013-08-29 18:20 ` Mark Brown 2013-08-29 18:34 ` Russell King - ARM Linux 2013-08-29 18:34 ` Russell King - ARM Linux 2013-08-28 19:49 ` Sergei Shtylyov 2013-08-28 19:49 ` Sergei Shtylyov 2013-08-29 9:38 ` Jean-Francois Moine 2013-08-29 9:38 ` Jean-Francois Moine 2013-08-29 14:13 ` Sergei Shtylyov 2013-08-29 14:13 ` Sergei Shtylyov
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=20130829182010.GQ10783@sirena.org.uk \ --to=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=gregory.clement@free-electrons.com \ --cc=ian.campbell@citrix.com \ --cc=jason@lakedaemon.net \ --cc=liam.r.girdwood@intel.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=mark.rutland@arm.com \ --cc=moinejf@free.fr \ --cc=pawel.moll@arm.com \ --cc=rob.herring@calxeda.com \ --cc=sebastian.hesselbarth@gmail.com \ --cc=swarren@wwwdotorg.org \ --cc=thomas.petazzoni@free-electrons.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: linkBe 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.