linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: Freescale imx35: sgtl5000 codec not working over i2c
Date: Thu, 2 May 2013 20:18:21 +0200	[thread overview]
Message-ID: <20130502181821.GC31135@pengutronix.de> (raw)
In-Reply-To: <20130502200024.72c112cc@jobraun>

On Thu, May 02, 2013 at 08:00:24PM +0200, Johannes Braun wrote:
> Hello @all,
> 
> I hope this is the right place for my problem. Currently I am trying to
> get a sigmatel sgtl5000 codec to work on a Freescale imx35 based board.
> I am using a vanilla kernel 3.7.10. The codec is connected via i2c. I
> configured the i2c device in /arch/arm/mach-imx/mach-proxmobil2.c.
> Proxmobil2 is the name of our device. Here is the part which configures
> the i2c device and the bus.
> 
> static const struct imxi2c_platform_data mx35_prox2_i2c0_data
> 	__initconst = {
>         .bitrate = 100000,
> };
> 
> imx35_add_imx_i2c0(&mx35_prox2_i2c0_data);
> 
> static struct i2c_board_info __initdata i2c_devices_prox2[] = {
>         {
>                 I2C_BOARD_INFO("imx-audio-sgtl5000", 0x0a),
>         },

The driver matches "sgtl5000", not "imx-audio-sgtl5000".

You should use devicetree support for new boards. The platform support
will vanish sooner or later.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2013-05-02 18:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02 18:00 Freescale imx35: sgtl5000 codec not working over i2c Johannes Braun
2013-05-02 18:18 ` Sascha Hauer [this message]
2013-05-02 18:40   ` Johannes Braun
2013-05-03  9:39     ` Sascha Hauer
2013-05-03 11:56       ` Johannes Braun

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=20130502181821.GC31135@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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).