From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751496AbdAMWaK (ORCPT ); Fri, 13 Jan 2017 17:30:10 -0500 Received: from mail-qt0-f193.google.com ([209.85.216.193]:36127 "EHLO mail-qt0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750901AbdAMWaJ (ORCPT ); Fri, 13 Jan 2017 17:30:09 -0500 MIME-Version: 1.0 In-Reply-To: References: <20170112120101.16933-1-shrirang.bagul@canonical.com> <20170112120101.16933-2-shrirang.bagul@canonical.com> From: Andy Shevchenko Date: Sat, 14 Jan 2017 00:30:08 +0200 Message-ID: Subject: Re: [PATCH v2 1/4] ASoC: rt5660: Add ACPI support To: Bard Liao Cc: Shrirang Bagul , "alsa-devel@alsa-project.org" , "linux-kernel@vger.kernel.org" , Oder Chiou , Liam Girdwood , Mark Brown , Jaroslav Kysela , Takashi Iwai Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 13, 2017 at 4:53 AM, Bard Liao wrote: >> +static const struct acpi_gpio_mapping byt_rt5660_gpios[] = { >> + { "audio-wake-intr-gpios", &audio_wake_intr_gpio, 1 }, >> + { "lineout-mute-gpios", &lineout_mute_gpio, 1 }, >> + { NULL }, >> +}; >> + > > I am thinking if it is more suitable to move the gpio params to > machine driver? They are not codec's gpios and are only used > by machine driver. Generally speaking those properties should come per ACPI ID. So, they should share the same module which has MODULE_DEVICE_TABLE(acpi, ...) defined. -- With Best Regards, Andy Shevchenko