Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Bard Liao <bardliao@realtek.com>
Subject: Re: [REANNOUNCE] Audio Mini Summit 2015, 8th October, Dublin
Date: Mon, 3 Aug 2015 08:45:52 +0530	[thread overview]
Message-ID: <20150803031552.GN29916@localhost> (raw)
In-Reply-To: <55B6B92B.5010305@linux.intel.com>

On Mon, Jul 27, 2015 at 06:05:15PM -0500, Pierre-Louis Bossart wrote:
> On 7/21/15 6:29 AM, Bard Liao wrote:
> >>-----Original Message-----
> >>From: Mark Brown [mailto:broonie@kernel.org]
> >>Sent: Tuesday, July 14, 2015 11:04 PM
> >>To: Takashi Iwai; Liam Girdwood; Jaroslav Kysela
> >>Cc: alsa-devel@alsa-project.org
> >>Subject: [REANNOUNCE] Audio Mini Summit 2015, 8th October, Dublin
> >>
> >>Like previous years, we're going to hold a meeting to discuss lowlevel
> >>audio on Linux.  This will be held the day after ELC Europe on 8th
> >>October at CCD (The Convention Centre) in Dublin.
> >>
> >>If you're interested please sign up in the attendee list:
> >>
> >>https://docs.google.com/spreadsheets/d/1bi-8GHsqlzt41FR20WiMuWILe_
> >>cZowFireVMBd-QM8Q/edit?usp=sharing
> >>
> >>and please follow up to this mail with any topics you'd like to see raised so
> >>we can start collecting them (probably another Google doc will be
> >>forthcoming for them).
> >>
> >>Previously suggested topics include:
> >>
> >>  - Reducing kernel size for IoT applications
> >>  - ACPI simple-card
> 
> I think we should also share findings on DeviceTree vs. ACPI support
> for machine drivers and subnodes.

I am planning to discuss two things in this space:
- One the NHLT table in BIOS
- Second my ongoing work on ACPI properties for machines, hopefully should be
  able to send patches before conference

-- 
~Vinod

  reply	other threads:[~2015-08-03  3:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 15:03 [REANNOUNCE] Audio Mini Summit 2015, 8th October, Dublin Mark Brown
2015-07-14 16:04 ` Alexander E. Patrakov
2015-07-14 16:17   ` Mark Brown
2015-07-14 16:36     ` Alexander E. Patrakov
2015-07-14 17:05       ` Alexander E. Patrakov
2015-07-27 23:26   ` Pierre-Louis Bossart
2015-07-18 17:07 ` Vinod Koul
2015-09-10 21:35   ` Eric Laurent
2015-09-14 18:02     ` Mark Brown
2015-09-14 18:10       ` Eric Laurent
2015-07-21 11:29 ` Bard Liao
2015-07-27 23:05   ` Pierre-Louis Bossart
2015-08-03  3:15     ` Vinod Koul [this message]
2015-09-22  8:49       ` Arun Raghavan
2015-10-03 16:13         ` Takashi Iwai
2015-10-04 22:57           ` Mark Brown
2015-10-04 23:19             ` Mark Brown
2015-10-04  9:24         ` Arun Raghavan
2015-08-01  7:37 ` Lars-Peter Clausen
2015-08-03  3:21   ` Vinod Koul
2015-08-04 16:13     ` Mark Brown
2015-08-05  2:56       ` Vinod Koul
2015-08-05  9:39         ` Mark Brown
2015-08-03 19:11   ` Pierre-Louis Bossart
2015-08-04 16:03   ` Mark Brown
2015-08-04 18:50     ` Lars-Peter Clausen

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=20150803031552.GN29916@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    /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