From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 88F57C433F5 for ; Thu, 16 Sep 2021 09:16:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6F36560E94 for ; Thu, 16 Sep 2021 09:16:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236228AbhIPJSR (ORCPT ); Thu, 16 Sep 2021 05:18:17 -0400 Received: from smtp-out2.suse.de ([195.135.220.29]:38630 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236566AbhIPJRi (ORCPT ); Thu, 16 Sep 2021 05:17:38 -0400 Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id BCCC91FEBA; Thu, 16 Sep 2021 09:16:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1631783777; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4BtHHTpVzGs0XpFHR8D6XsmcKBC0z4EhoSusSo6vw4w=; b=TNnQr0pfd63qqoQRixOIlGGvHl0GDwEd+ZyJfsCzlo3o/DhVKWE3y6ksQowwXvOTTJSITK wimxhuHYU384UIAXnv3+fHVLara93n94NcMkX/fNiscCnMDziNQ2ImlLp6zpfqVsHplHWa CrGhHEva0z9GeVFjihidWNcQvFlTZts= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1631783777; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4BtHHTpVzGs0XpFHR8D6XsmcKBC0z4EhoSusSo6vw4w=; b=kSQ9XJ3u6pFxYQlOJaR1yMxNuo10+zo/1L6dHZpvYZW6mOqKLBp0yCGWK1wIrshlsCQipV Ebrghm9sh9UMG7Aw== Received: from alsa1.suse.de (alsa1.suse.de [10.160.4.42]) by relay2.suse.de (Postfix) with ESMTP id B5F30A3DA6; Thu, 16 Sep 2021 09:16:17 +0000 (UTC) Date: Thu, 16 Sep 2021 11:16:17 +0200 Message-ID: From: Takashi Iwai To: Fabio Estevam Cc: Dmitry Torokhov , linux-input@vger.kernel.org Subject: Re: Delaying i8042 probe? In-Reply-To: References: User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-input@vger.kernel.org On Sat, 11 Sep 2021 20:50:25 +0200, Fabio Estevam wrote: > > On Sat, Sep 11, 2021 at 3:43 PM Fabio Estevam wrote: > > > > On Sat, Sep 11, 2021 at 4:32 AM Takashi Iwai wrote: > > > > > OK, I'll update and let the reporter testing it. > > > > Sorry, platform_device_alloc() and platform_device_add() were missing > > in the earlier patch. > > > > New patch atached. > > > > Dmitry, does this look correct? > > Please consider this one instead. The patch was confirmed to work. https://bugzilla.suse.com/show_bug.cgi?id=1190256#c19 | That one worked despite the CTR error: | | [ 0.000000] Linux version 5.14.2-3.g9458b22-default (geeko@buildhost) (gcc (SUSE Linux) 11.2.1 20210816 [revision 056e324ce46a7924b5cf10f61010cf9dd2ca10e9], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.36.1.20210326-4) #1 SMP Sun Sep 12 20:15:58 UTC 2021 (9458b22) | [ 0.484315] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1 | [ 0.484318] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp | [ 1.005361] i8042: Can't read CTR while initializing i8042 | [ 1.477053] serio: i8042 KBD port at 0x60,0x64 irq 1 | [ 1.503700] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2 | | Seems it takes more than a secod to initialize, ugh I'm not sure what's done during this 0.5 second period after CTR read failure. At least only shuffling the driver init order for built-in drivers didn't suffice. A full log was requested, but I don't think it'll give much more information. Takashi