From: Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Lars-Peter Clausen <lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>,
alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
kernel-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org,
Jaroslav Kysela <perex-/Fr2/VpizcU@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [alsa-devel] [RFC-PATCH 0/2] ASoC: simple_card: support for hw-params rules
Date: Mon, 23 May 2016 19:59:18 +0200 [thread overview]
Message-ID: <s5ha8jg3bbd.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160523165931.GY8206-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On Mon, 23 May 2016 18:59:31 +0200,
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.
Using eBPF is a good idea for our purposes, but I understand Mark's
concern, too. That said, I'm in favor of eBPF as long as DT people
don't mind. We'd need some tools but the rest would be easier (less
patching) once after it's done.
thanks,
Takashi
--
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 17:59 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
[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 [this message]
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=s5ha8jg3bbd.wl-tiwai@suse.de \
--to=tiwai-l3a5bk7wagm@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=lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=perex-/Fr2/VpizcU@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@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 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.