On Tue, 2014-11-25 at 08:01 -0800, Darren Hart wrote:
>
> On 11/25/14 06:28, Liam Girdwood wrote:
> > On Tue, 2014-11-25 at 12:11 +, Grant Likely wrote:
> >> On Sat, Nov 15, 2014 at 6:56 AM, Ben Zhang wrote:
> >>> The rt5677 codec driver looks for ACPI device ID "RT5677CE",
> >>> which is
On 11/25/14 06:28, Liam Girdwood wrote:
> On Tue, 2014-11-25 at 12:11 +, Grant Likely wrote:
>> On Sat, Nov 15, 2014 at 6:56 AM, Ben Zhang wrote:
>>> The rt5677 codec driver looks for ACPI device ID "RT5677CE",
>>> which is specified in coreboot. This patch allows platform
>>> data to be
On Tue, 2014-11-25 at 12:11 +, Grant Likely wrote:
> On Sat, Nov 15, 2014 at 6:56 AM, Ben Zhang wrote:
> > The rt5677 codec driver looks for ACPI device ID "RT5677CE",
> > which is specified in coreboot. This patch allows platform
> > data to be obtained via ACPI
> >
> > Signed-off-by: Ben
On Tue, 2014-11-25 at 12:11 +, Grant Likely wrote:
On Sat, Nov 15, 2014 at 6:56 AM, Ben Zhang be...@chromium.org wrote:
The rt5677 codec driver looks for ACPI device ID RT5677CE,
which is specified in coreboot. This patch allows platform
data to be obtained via ACPI
Signed-off-by:
On 11/25/14 06:28, Liam Girdwood wrote:
On Tue, 2014-11-25 at 12:11 +, Grant Likely wrote:
On Sat, Nov 15, 2014 at 6:56 AM, Ben Zhang be...@chromium.org wrote:
The rt5677 codec driver looks for ACPI device ID RT5677CE,
which is specified in coreboot. This patch allows platform
data to
On Tue, 2014-11-25 at 08:01 -0800, Darren Hart wrote:
On 11/25/14 06:28, Liam Girdwood wrote:
On Tue, 2014-11-25 at 12:11 +, Grant Likely wrote:
On Sat, Nov 15, 2014 at 6:56 AM, Ben Zhang be...@chromium.org wrote:
The rt5677 codec driver looks for ACPI device ID RT5677CE,
which is
6 matches
Mail list logo
