From: Matt Flax <flatmax@flatmax.org>
To: Vasily Khoruzhick <anarsoul@gmail.com>, alsa-devel@alsa-project.org
Cc: vano@ivankiten.com, cw00.choi@samsung.com
Subject: Re: I2S driver for implants
Date: Wed, 23 Jul 2014 19:43:38 +1000 [thread overview]
Message-ID: <53CF83CA.3030004@flatmax.org> (raw)
In-Reply-To: <CA+E=qVfJ47g76=Zzq+smQUR5UY0zRWjV8Aswx5D7AAfdKLPQmA@mail.gmail.com>
On 23/07/14 18:23, Vasily Khoruzhick wrote:
> On Wed, Jul 23, 2014 at 11:10 AM, Matt Flax <flatmax@flatmax.org> wrote:
>> Hi there,
> Hi Matt,
>
> I'd suggest you include alsa-devel ML next time (added it to CC)
>
>> I saw your driver sound/soc/samsung
>>
>> I am wanting to look into an I2S driver for the Exynos 5250 for eye
>> implants.
> Driver for I2S in Exynos 5 is already included in mainline kernel.
>
>> The implants use a serial bus and I am wanting to specify an I2S connection
>> to them.
>>
>> In order to do that I would need to write an I2S driver to talk to them.
>> Their bit rates are either 300 kbps or 600 kbps.
>> They only need I2S and not I2C ... there are not controls, simply serial
>> data in and out.
> Are you sure that your implants can talk over I2S?
Yes, we do/will have custom hardware to reconstruct the required signals
from the I2S lines.
>> I am wondering if I can do something simple ... I notice that your driver
>> doesn't require too much code ...
>> Do you think it is possible for me to take a similar approach in writing my
>> implant driver ?
> Don't know, you didn't share much details on your hardware.
The hardware requires one I2S output line and one I2S input line + the
clock line.
You say "Driver for I2S in Exynos 5 is already included in mainline
kernel." ... do you mean that all I need is a device tree file to enable
it ? If so, then can you please link me to an example device tree ... my
assumption is that this I2S device will show up in alsa once the device
tree is setup ?
>> Can you give me advice - how to start ?
> Start with reading specs and try to understand how your implants work,
> then look at existing code and try to adapt it for your usage.
> Then clean it up and prepare for submitting into mainline.
>> thanks
>> Matt
> Regards,
> Vasily
next prev parent reply other threads:[~2014-07-23 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53CF6DD8.3000507@flatmax.org>
2014-07-23 8:23 ` I2S driver for implants Vasily Khoruzhick
2014-07-23 9:43 ` Matt Flax [this message]
2014-07-23 9:52 ` Vasily Khoruzhick
2014-07-23 11:08 ` Matt Flax
2014-07-23 14:16 ` Vasily Khoruzhick
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=53CF83CA.3030004@flatmax.org \
--to=flatmax@flatmax.org \
--cc=alsa-devel@alsa-project.org \
--cc=anarsoul@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=vano@ivankiten.com \
/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