All of lore.kernel.org
 help / color / mirror / Atom feed
From: noman pouigt <variksla@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"broonie@kernel.org" <broonie@kernel.org>
Subject: Re: recording problem in beagleboard-mcbsp
Date: Fri, 10 Apr 2015 14:42:01 -0700	[thread overview]
Message-ID: <CAES_P+-6S3_uc0EJUtBDOTyCGSPt_qSOZftOfFzbN9DJqUDuJQ@mail.gmail.com> (raw)
In-Reply-To: <CAES_P+_PcMT4gLUAcvo8QugDdJVhqRnNxfuR3UczE+Mdqe9maA@mail.gmail.com>

On Fri, Apr 10, 2015 at 10:54 AM, noman pouigt <variksla@gmail.com> wrote:
> On Fri, Apr 10, 2015 at 12:11 AM, Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
>> On 04/10/2015 02:04 AM, noman pouigt wrote:
>>> On Thu, Apr 9, 2015 at 7:07 AM, Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
>>>> On 04/09/2015 03:06 PM, Peter Ujfalusi wrote:
>>>>> Hrm, McBSP1 is kind of problematic port since it has 6pin config by default.
>>>>> It might worth a try to do something like:
>>>>> http://lists.infradead.org/pipermail/linux-arm-kernel/2012-August/113058.html
>>>>> has removed.
>>>>> Or to switch to use McBSP3.
>>>>>
>>>>> But for some reason now I can not get the recording working via McBSP1 either.
>>>>> I remember that it worked not that long time ago...
>>>>
>>>> One thing I would also try:
>>>> use the codec as master and connect the FS to McBSP1 FSX _and_ FSR. Do the
>>>> same for the bclk (connect it to BCLKX _and_ BCLKR of McBSP1)
>>>> Configure the pin mux for these pins also.
>>>
>>> I did but it didn't work.Below is my configuration.
>>> configured mcbsp1_clkx, mcbsp1_fsx, mcbsp1_dx and mcbsp1_dr
>>> +
>>> +       mcbsp1_pins: pinmux_mcbsp1_pins {
>>> +                pinctrl-single,pins = <
>>> +                        OMAP3_CORE1_IOPAD(0x2196, PIN_OUTPUT | MUX_MODE0)
>>> +                        OMAP3_CORE1_IOPAD(0x2198, PIN_OUTPUT | MUX_MODE0)
>>> +                        OMAP3_CORE1_IOPAD(0x2190, PIN_OUTPUT | MUX_MODE0)
>>> +                        OMAP3_CORE1_IOPAD(0x2192, PIN_INPUT | MUX_MODE0)
>>> +                        OMAP3_CORE1_IOPAD(0x218C, PIN_OUTPUT | MUX_MODE0)
>>> +                        OMAP3_CORE1_IOPAD(0x218E, PIN_OUTPUT | MUX_MODE0)
>>> +                >;
>>> +        };
>>
>> What about the codec master mode? Does that work?
> I will also try this and update.
Tried this as well and it didn't work. Strange that FSR and CLKR is also
having the required clocks.
>>
>>>  };
>>>>
>>>> --
>>>> Péter
>>
>>
>> --
>> Péter
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2015-04-10 21:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 20:24 recording problem in beagleboard-mcbsp noman pouigt
2015-03-27 21:20 ` noman pouigt
2015-03-31 18:41   ` noman pouigt
2015-04-01 18:46     ` Peter Ujfalusi
2015-04-07  4:29       ` noman pouigt
2015-04-07  9:22         ` Peter Ujfalusi
2015-04-07 18:33           ` noman pouigt
2015-04-08  9:52             ` Peter Ujfalusi
2015-04-08 23:44               ` noman pouigt
2015-04-09 12:06                 ` Peter Ujfalusi
2015-04-09 14:07                   ` Peter Ujfalusi
2015-04-09 23:04                     ` noman pouigt
2015-04-10  7:11                       ` Peter Ujfalusi
2015-04-10 17:54                         ` noman pouigt
2015-04-10 21:42                           ` noman pouigt [this message]
2015-04-09 23:02                   ` noman pouigt
2015-04-10  7:13                     ` Peter Ujfalusi
2015-04-10 17:53                       ` noman pouigt
2015-04-10 22:58                         ` noman pouigt
2015-04-13 15:14                     ` Peter Ujfalusi
2015-04-14  9:39                       ` Peter Ujfalusi
2015-04-14 12:39                         ` Peter Ujfalusi
2015-04-14 16:41                           ` Variksla
2015-04-15  6:03                             ` Peter Ujfalusi
2015-04-14 22:32                           ` noman pouigt

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=CAES_P+-6S3_uc0EJUtBDOTyCGSPt_qSOZftOfFzbN9DJqUDuJQ@mail.gmail.com \
    --to=variksla@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=peter.ujfalusi@ti.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 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.