From: Lars-Peter Clausen <lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
To: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Takashi Iwai <tiwai-IBi9RG/b67k@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
kernel-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org
Subject: Re: [alsa-devel] [RFC-PATCH 0/2] ASoC: simple_card: support for hw-params rules
Date: Mon, 23 May 2016 20:26:41 +0200 [thread overview]
Message-ID: <57434B61.2080705@metafoo.de> (raw)
In-Reply-To: <20160523171515.GI4976@leverpostej>
On 05/23/2016 07:15 PM, Mark Rutland wrote:
> On Mon, May 23, 2016 at 05:59:31PM +0100, Mark Brown wrote:
>> On Fri, May 20, 2016 at 09:16:09PM +0200, Lars-Peter Clausen wrote:
>>
>>> How about allowing to embed eBPF bytecode in the DT that can be installed as
>>> a constraint set? This would allow maximum for flexibility and also make the
>>> implementation a lot easier.
>>
>> That seems somewhat Linux specific, I'd like to see some DT maintainer
>> buy in on that one as well as Takashi's thoughts.
>
> I am very much not in favour of embedding eBPF bytecode into the DT.
This has to be seen in the context of the suggestion to reference kernel
symbols by name from the DT.
My opinion is that if the interdependence between the components in your
system is non-trivial you should write a proper driver. Otherwise we'll end
up with DT-script and replicate all the terrible things from the ACPI world
where people ship completely horrendous and broken byte code in the firmware.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-05-23 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 12:30 [RFC-PATCH 0/2] ASoC: simple_card: support for hw-params rules kernel-TqfNSX0MhmxHKSADF0wUEw
[not found] ` <1463747445-14167-1-git-send-email-kernel-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org>
2016-05-20 12:30 ` [PATCH 1/2] ASoC: hw-params-rules: add generic hw_params-rules kernel-TqfNSX0MhmxHKSADF0wUEw
2016-05-20 12:30 ` [PATCH 2/2] ASoC: simple_card: add support for hw_params_rules kernel-TqfNSX0MhmxHKSADF0wUEw
2016-05-20 19:16 ` [alsa-devel] [RFC-PATCH 0/2] ASoC: simple_card: support for hw-params rules Lars-Peter Clausen
[not found] ` <573F6279.8040008-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2016-05-23 16:59 ` Mark Brown
[not found] ` <20160523165931.GY8206-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-05-23 17:15 ` Mark Rutland
2016-05-23 18:26 ` Lars-Peter Clausen [this message]
[not found] ` <57434B61.2080705-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2016-05-23 19:02 ` Mark Brown
2016-05-23 21:29 ` Rob Herring
2016-05-23 17:59 ` Takashi Iwai
2016-05-23 17:18 ` Mark Rutland
2016-05-25 15:44 ` kernel-TqfNSX0MhmxHKSADF0wUEw
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=57434B61.2080705@metafoo.de \
--to=lars-qo5elluwu/uelga04laivw@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=tiwai-IBi9RG/b67k@public.gmane.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;
as well as URLs for NNTP newsgroup(s).