From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: pxa: raumfeld: fix device name for codec ak4104
Date: Wed, 25 May 2011 13:37:33 +0200 [thread overview]
Message-ID: <1306323453-6371-3-git-send-email-zonque@gmail.com> (raw)
In-Reply-To: <1306323453-6371-1-git-send-email-zonque@gmail.com>
In commit f0fba2ad (ASoC: multi-component - ASoC Multi-Component
Support), the name of the ak4104 codec driver was changed without
amending the platform code which uses it as well.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
arch/arm/mach-pxa/raumfeld.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-pxa/raumfeld.c b/arch/arm/mach-pxa/raumfeld.c
index cdec616..c17883b 100644
--- a/arch/arm/mach-pxa/raumfeld.c
+++ b/arch/arm/mach-pxa/raumfeld.c
@@ -660,10 +660,10 @@ static struct lis3lv02d_platform_data lis3_pdata = {
#define SPI_AK4104 \
{ \
- .modalias = "ak4104", \
- .max_speed_hz = 10000, \
- .bus_num = 0, \
- .chip_select = 0, \
+ .modalias = "ak4104-codec", \
+ .max_speed_hz = 10000, \
+ .bus_num = 0, \
+ .chip_select = 0, \
.controller_data = (void *) GPIO_SPDIF_CS, \
}
--
1.7.5.1
next prev parent reply other threads:[~2011-05-25 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 12:13 [PATCH 1/2] ARM: pxa: raumfeld: follow upcoming hardware change Daniel Mack
2011-05-24 12:13 ` [PATCH 2/2] ARM: pxa: raumfeld: fix device name for codec ak4104 Daniel Mack
2011-05-24 17:50 ` [PATCH 1/2] ARM: pxa: raumfeld: follow upcoming hardware change Russell King - ARM Linux
2011-05-25 11:11 ` Daniel Mack
2011-05-25 11:37 ` [PATCH 1/3] ARM: pxa: raumfeld: adapt to " Daniel Mack
2011-05-25 11:37 ` [PATCH 2/3] ARM: pxa: raumfeld: display initialisation fixes Daniel Mack
2011-05-25 11:37 ` Daniel Mack [this message]
2011-05-26 18:24 ` [PATCH 1/3] ARM: pxa: raumfeld: adapt to upcoming hardware change Daniel Mack
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=1306323453-6371-3-git-send-email-zonque@gmail.com \
--to=zonque@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).