From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Caleb Crome <caleb@crome.org>, Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Sascha Hauer <kernel@pengutronix.de>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Timur Tabi <timur@tabi.org>,
Arnaud Mouiche <arnaud.mouiche@invoxia.com>,
lukma@denx.de, Fabio Estevam <fabio.estevam@nxp.com>,
mail@maciej.szmigiero.name, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v4 00/11] ASoC: fsl_ssi: Clean up - coding style level
Date: Mon, 18 Dec 2017 15:02:21 -0800 [thread overview]
Message-ID: <20171218230220.GA16161@Asurada-Nvidia> (raw)
In-Reply-To: <CAG5mAdxsWmHfCc=vFkO+Wmi8m0c_9t7B6BTUBGVOmPoGOQrsyg@mail.gmail.com>
On Mon, Dec 18, 2017 at 02:19:08PM -0800, Caleb Crome wrote:
> > Acked-by: Timur Tabi <timur@tabi.org>
--- To Mark ---
Mark, can you still take these changes first? Since this failed
test that Caleb reported here is already existing on the top of
the mainline tree, I would like to treat this mail as a separate
bug report and fix it with a separate patch.
Besides, this series of changes don't change any function flow.
Thank you
--- To Caleb ---
> I'm re-setting up my loopback test to try to verify these most recent changes.
I really appreciate your verification and help.
> warn: 11a0 11a1 1160 11a3 11a4 11a5 11a6 11a7
> warn: Valid frame after 1 invalid frames
> warn: 11c0 11c1 11c2 11c3 11c4 11c5 11c6 11c7
> warn: first invalid frame while expecting frame 0x00a0
> warn: 13e7 1400 1401 1402 1403 1404 1405 1404
> warn: 1407 1420 1421 1422 1423 1424 1425 1426
> warn: 1427 1440 1441 1442 1443 1444 1445 1484
> warn: 1447 1460 1461 1462 1463 1464 1465 1466
>
> Those last 4 lines are the channel slips -- the least significant
> nibble should be the channel number: i.e. should go 0, 1, 2, 3, 4, 5,
> 6, 7.
>
> Ugh, so it's basically quite broken again -- before these patches.
I remember Arnaud reviewed one of my changes back to September.
So I suppose the test should be fine at that time -- so a change
being merged recently might have impacted the test result.
> I guess I need to go backwards in time and see what rev re-broke it.
> I don't really have time to dig too deep on this again.
>
> I'd be happy to provide the hardware to anybody that can diagnose and
> debug this more quickly than I can. I'm very inefficient at kernel
> drivers I think. My day job is acoustical and electrical
> engineering.
>
> Here's what the hardware looks like for anybody that's interested.
> Just a single wire loopback on the wandboard header.
I would definitely like to take the hardware to debug it as long
as you are willing to provide me. Can you send me a private mail
to discuss about it?
Thanks
Nicolin
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Caleb Crome <caleb@crome.org>, Mark Brown <broonie@kernel.org>
Cc: Timur Tabi <timur@tabi.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
mail@maciej.szmigiero.name,
Arnaud Mouiche <arnaud.mouiche@invoxia.com>,
lukma@denx.de, Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH v4 00/11] ASoC: fsl_ssi: Clean up - coding style level
Date: Mon, 18 Dec 2017 15:02:21 -0800 [thread overview]
Message-ID: <20171218230220.GA16161@Asurada-Nvidia> (raw)
In-Reply-To: <CAG5mAdxsWmHfCc=vFkO+Wmi8m0c_9t7B6BTUBGVOmPoGOQrsyg@mail.gmail.com>
On Mon, Dec 18, 2017 at 02:19:08PM -0800, Caleb Crome wrote:
> > Acked-by: Timur Tabi <timur@tabi.org>
--- To Mark ---
Mark, can you still take these changes first? Since this failed
test that Caleb reported here is already existing on the top of
the mainline tree, I would like to treat this mail as a separate
bug report and fix it with a separate patch.
Besides, this series of changes don't change any function flow.
Thank you
--- To Caleb ---
> I'm re-setting up my loopback test to try to verify these most recent changes.
I really appreciate your verification and help.
> warn: 11a0 11a1 1160 11a3 11a4 11a5 11a6 11a7
> warn: Valid frame after 1 invalid frames
> warn: 11c0 11c1 11c2 11c3 11c4 11c5 11c6 11c7
> warn: first invalid frame while expecting frame 0x00a0
> warn: 13e7 1400 1401 1402 1403 1404 1405 1404
> warn: 1407 1420 1421 1422 1423 1424 1425 1426
> warn: 1427 1440 1441 1442 1443 1444 1445 1484
> warn: 1447 1460 1461 1462 1463 1464 1465 1466
>
> Those last 4 lines are the channel slips -- the least significant
> nibble should be the channel number: i.e. should go 0, 1, 2, 3, 4, 5,
> 6, 7.
>
> Ugh, so it's basically quite broken again -- before these patches.
I remember Arnaud reviewed one of my changes back to September.
So I suppose the test should be fine at that time -- so a change
being merged recently might have impacted the test result.
> I guess I need to go backwards in time and see what rev re-broke it.
> I don't really have time to dig too deep on this again.
>
> I'd be happy to provide the hardware to anybody that can diagnose and
> debug this more quickly than I can. I'm very inefficient at kernel
> drivers I think. My day job is acoustical and electrical
> engineering.
>
> Here's what the hardware looks like for anybody that's interested.
> Just a single wire loopback on the wandboard header.
I would definitely like to take the hardware to debug it as long
as you are willing to provide me. Can you send me a private mail
to discuss about it?
Thanks
Nicolin
next prev parent reply other threads:[~2017-12-18 23:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 2:51 [PATCH v4 00/11] ASoC: fsl_ssi: Clean up - coding style level Nicolin Chen
2017-12-18 2:52 ` [PATCH v4 01/11] ASoC: fsl_ssi: Rename fsl_ssi_private to fsl_ssi Nicolin Chen
2017-12-18 2:52 ` [PATCH v4 02/11] ASoC: fsl_ssi: Cache pdev->dev pointer Nicolin Chen
2017-12-18 2:52 ` Nicolin Chen
2017-12-18 2:52 ` [PATCH v4 03/11] ASoC: fsl_ssi: Refine all comments Nicolin Chen
2017-12-18 2:52 ` Nicolin Chen
2017-12-19 11:00 ` Applied "ASoC: fsl_ssi: Refine all comments" to the asoc tree Mark Brown
2017-12-19 11:00 ` Mark Brown
2017-12-18 2:52 ` [PATCH v4 04/11] ASoC: fsl_ssi: Rename registers and fields macros Nicolin Chen
2017-12-19 11:00 ` Applied "ASoC: fsl_ssi: Rename registers and fields macros" to the asoc tree Mark Brown
2017-12-19 11:00 ` Mark Brown
2017-12-18 2:52 ` [PATCH v4 05/11] ASoC: fsl_ssi: Refine indentations and wrappings Nicolin Chen
2017-12-19 11:00 ` Applied "ASoC: fsl_ssi: Refine indentations and wrappings" to the asoc tree Mark Brown
2017-12-19 11:00 ` Mark Brown
2017-12-18 2:52 ` [PATCH v4 06/11] ASoC: fsl_ssi: Refine printk outputs Nicolin Chen
2017-12-18 2:52 ` [PATCH v4 07/11] ASoC: fsl_ssi: Rename cpu_dai parameter to dai Nicolin Chen
2017-12-18 2:52 ` [PATCH v4 08/11] ASoC: fsl_ssi: Rename scr_val to scr Nicolin Chen
2017-12-18 2:52 ` [PATCH v4 09/11] ASoC: fsl_ssi: Replace fsl_ssi_rxtx_reg_val with fsl_ssi_regvals Nicolin Chen
2017-12-19 10:59 ` Applied "ASoC: fsl_ssi: Replace fsl_ssi_rxtx_reg_val with fsl_ssi_regvals" to the asoc tree Mark Brown
2017-12-19 10:59 ` Mark Brown
2017-12-18 2:52 ` [PATCH v4 10/11] ASoC: fsl_ssi: Rename i2smode to i2s_net Nicolin Chen
2017-12-18 2:52 ` [PATCH v4 11/11] ASoC: fsl_ssi: Define ternary macros to simplify code Nicolin Chen
2017-12-18 3:13 ` [PATCH v4 00/11] ASoC: fsl_ssi: Clean up - coding style level Timur Tabi
2017-12-18 22:19 ` Caleb Crome
2017-12-18 22:19 ` Caleb Crome
2017-12-18 23:02 ` Nicolin Chen [this message]
2017-12-18 23:02 ` Nicolin Chen
2017-12-19 0:25 ` Caleb Crome
2017-12-20 11:40 ` Arnaud Mouiche
2017-12-20 11:40 ` Arnaud Mouiche
2017-12-20 17:26 ` Nicolin Chen
2017-12-20 17:26 ` Nicolin Chen
2017-12-21 16:08 ` Caleb Crome
2017-12-21 16:08 ` Caleb Crome
2017-12-21 16:10 ` Caleb Crome
2017-12-21 16:21 ` Nicolin Chen
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=20171218230220.GA16161@Asurada-Nvidia \
--to=nicoleotsuka@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.mouiche@invoxia.com \
--cc=broonie@kernel.org \
--cc=caleb@crome.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukma@denx.de \
--cc=mail@maciej.szmigiero.name \
--cc=timur@tabi.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.