mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steev Klimaszewski <steev@kali.org>
To: Javier Martinez Canillas <javierm@redhat.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
	Saravana Kannan <saravanak@google.com>,
	Peter Robinson <pbrobinson@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Sergio Lopez Pascual <slp@redhat.com>,
	Enric Balletbo i Serra <eballetbo@redhat.com>,
	John Stultz <jstultz@google.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH] driver core: Disable driver deferred probe timeout by default
Date: Mon, 14 Nov 2022 10:20:23 -0600	[thread overview]
Message-ID: <2b8c40ba-0068-99ca-6dc8-64d075e9112c@kali.org> (raw)
In-Reply-To: <9d53f7f9-b77b-21ff-500a-88f3a7fcee80@redhat.com>

Hi All,

On 11/14/22 5:56 AM, Javier Martinez Canillas wrote:
> On 11/14/22 12:38, Greg Kroah-Hartman wrote:
>> On Mon, Nov 14, 2022 at 12:13:15PM +0100, Javier Martinez Canillas wrote:
>>> Hello Greg,
> [...]
>
>>> I even gave an example about general purpose distributions that build as
>>> much as possible as a module. What more info do you think that is missing?
>> Exact systems that this is failing on would be great to have.
>>
> The exact system is a Snapdragon SC7180 based HP X2 Chromebook with latest
> Fedora Rawhide image (kernel version 6.1-rc4). The reason why is timing out
> is that the arm_smmu driver is built-in (CONFIG_ARM_SMMU=y) but it depends
> on gpucc-sc7180 clk driver that's built as module (CONFIG_SC_GPUCC_7180=m).

Additionally, this fails on the Snapdragon SC8280XP based Thinkpad X13s 
with 6.1-rc4 (and rc5), however, unlike Javier's setup, I *do* have 
CONFIG_SC_GPUCC_SC8280XP=y, so it's already built in to the kernel.  
Additionally, all DRM options =y, except for CONFIG_DRM_GEM_HELP=m and 
CONFIG_DRM_DISPLAY_CONNECTOR=m.

I am hoping to find some time tonight after work to also test on my 
SDM850 based Lenovo Yoga C630, as I believe my previous testing of 6.1 
may have been hitting this but I did not have time to dig into what was 
going on there.

-- steev

  reply	other threads:[~2022-11-14 16:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 10:43 Javier Martinez Canillas
2022-11-14 10:54 ` Greg Kroah-Hartman
2022-11-14 11:13   ` Javier Martinez Canillas
2022-11-14 11:38     ` Greg Kroah-Hartman
2022-11-14 11:56       ` Javier Martinez Canillas
2022-11-14 16:20         ` Steev Klimaszewski [this message]
2022-11-15  9:33 ` John Stultz
2022-11-15 10:52   ` Javier Martinez Canillas
2022-11-16 20:49     ` John Stultz
2022-11-17  8:14       ` Javier Martinez Canillas

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=2b8c40ba-0068-99ca-6dc8-64d075e9112c@kali.org \
    --to=steev@kali.org \
    --cc=eballetbo@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=javierm@redhat.com \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbrobinson@redhat.com \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=saravanak@google.com \
    --cc=slp@redhat.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

all inboxes | Powered by JetHome®