From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Mark Brown <broonie@kernel.org>, Inki Dae <inki.dae@samsung.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Andrzej Hajda <a.hajda@samsung.com>
Subject: Re: [FAIL bisect] Sound card probe error
Date: Mon, 14 May 2018 14:40:35 +0200 [thread overview]
Message-ID: <4c61c422-a036-8fec-1153-d612fe5df878@samsung.com> (raw)
In-Reply-To: <CAJKOXPc+kLA+BPBmaP14zMLbbxxCmWF1eZnKoa_PcO2z9jG9JQ@mail.gmail.com>
On 05/14/2018 02:29 PM, Krzysztof Kozlowski wrote:
> Ah, I missed these messages because I was looking at err dmesg level
> (and for some reason these are warn). Anyway do you have any thoughts
> how is it connected with missing Odroid XU3 sound card and max98090
> codec?
One reason is that the DRM driver registers an ASoC codec object which
is required for the sound card registration to complete. But I wonder
why there is no any error messages related to this.
--
Regards,
Sylwester
WARNING: multiple messages have this Message-ID (diff)
From: s.nawrocki@samsung.com (Sylwester Nawrocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [FAIL bisect] Sound card probe error
Date: Mon, 14 May 2018 14:40:35 +0200 [thread overview]
Message-ID: <4c61c422-a036-8fec-1153-d612fe5df878@samsung.com> (raw)
In-Reply-To: <CAJKOXPc+kLA+BPBmaP14zMLbbxxCmWF1eZnKoa_PcO2z9jG9JQ@mail.gmail.com>
On 05/14/2018 02:29 PM, Krzysztof Kozlowski wrote:
> Ah, I missed these messages because I was looking at err dmesg level
> (and for some reason these are warn). Anyway do you have any thoughts
> how is it connected with missing Odroid XU3 sound card and max98090
> codec?
One reason is that the DRM driver registers an ASoC codec object which
is required for the sound card registration to complete. But I wonder
why there is no any error messages related to this.
--
Regards,
Sylwester
next prev parent reply other threads:[~2018-05-14 12:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180514101728epcas4p3108760546a415b36252df93dfe38e0fb@epcas4p3.samsung.com>
2018-05-14 10:17 ` [FAIL bisect] Sound card probe error Krzysztof Kozlowski
2018-05-14 10:17 ` Krzysztof Kozlowski
2018-05-14 12:22 ` Sylwester Nawrocki
2018-05-14 12:22 ` Sylwester Nawrocki
2018-05-14 12:29 ` Krzysztof Kozlowski
2018-05-14 12:29 ` Krzysztof Kozlowski
2018-05-14 12:36 ` Marek Szyprowski
2018-05-14 12:36 ` Marek Szyprowski
2018-05-14 12:40 ` Sylwester Nawrocki [this message]
2018-05-14 12:40 ` Sylwester Nawrocki
2018-05-14 12:45 ` Krzysztof Kozlowski
2018-05-14 12:45 ` Krzysztof Kozlowski
2018-05-14 12:50 ` Krzysztof Kozlowski
2018-05-14 12:50 ` Krzysztof Kozlowski
2018-05-14 13:34 ` Sylwester Nawrocki
2018-05-14 13:34 ` Sylwester Nawrocki
2018-05-14 12:30 ` Ulf Hansson
2018-05-14 12:30 ` Ulf Hansson
2018-05-14 12:43 ` Krzysztof Kozlowski
2018-05-14 12:43 ` Krzysztof Kozlowski
2018-05-14 14:35 ` Ulf Hansson
2018-05-14 14:35 ` Ulf Hansson
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=4c61c422-a036-8fec-1153-d612fe5df878@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=a.hajda@samsung.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=inki.dae@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rafael.j.wysocki@intel.com \
--cc=ulf.hansson@linaro.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.