All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Calfee <stevecalfee@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Connecting a codec to an i2c codec driver.
Date: Tue, 22 Mar 2011 17:40:54 -0700	[thread overview]
Message-ID: <4D894196.4040002@gmail.com> (raw)
In-Reply-To: <AANLkTi=0SKc+2vUH=DV+c1Vm5NwoeAcHMac=tdyi4E8w@mail.gmail.com>

Hi,

I have a beagleboard xm and have a trainer board installed, so that adds another i2c bus, which with some platform tweaks I now have as /dev/i2c-2

I can use i2ctools and i2cdump my codec on that i2c bus, connected up on the platform data stuff.

I can modprobe the driver (in this case snd_soc_max98088), and no alsa "cards" or other linkages are established.

I got the i2c_probe routine to finally be called when I set the driver name to match the platform name:

static struct i2c_board_info __initdata beagle_i2c_trainer_boardinfo[] = {
	{
		I2C_BOARD_INFO("max98088", 0x10),
		.flags = I2C_CLIENT_WAKE,
		.irq = INT_34XX_SYS_NIRQ,
		.platform_data =&beagle_twldata,
	},
};

But then my max98088 probe routine was never called.

1) Is there a way to connect the i2c bus to a codec driver without having it built in the platform code?

2) What is the proper way to connect using a platform connection with multiple i2c buses and devices?

Thanks, Steve

  reply	other threads:[~2011-03-23  0:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 14:12 how to create alsa nodes? loody
2011-03-17 14:26 ` Clemens Ladisch
2011-03-18  9:03   ` loody
2011-03-23  0:40     ` Steve Calfee [this message]
2011-03-23 11:07       ` Connecting a codec to an i2c codec driver Mark Brown
2011-03-23 13:22         ` Steve Calfee
2011-03-23 13:30           ` Mark Brown
2011-03-24 19:56             ` Steve Calfee
2011-03-25 11:43               ` Mark Brown
2013-02-12  8:17       ` emi62 (may be slightly off-topic) Karl Grill
2013-02-15 14:44         ` Takashi Iwai
2013-02-15 15:28           ` Monty Montgomery
2013-02-15 15:37             ` Monty Montgomery
2013-02-15 16:07               ` Takashi Iwai
2013-02-15 16:14                 ` Monty Montgomery
2013-02-15 16:26                   ` Takashi Iwai
2013-12-11  0:04                     ` Monty Montgomery
2013-12-11 14:34                       ` Takashi Iwai
2013-12-12  7:32                         ` Monty Montgomery
2013-12-12 17:11                           ` Takashi Iwai

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=4D894196.4040002@gmail.com \
    --to=stevecalfee@gmail.com \
    --cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.