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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 60ED4C433FE for ; Sat, 21 May 2022 09:06:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233119AbiEUJGa (ORCPT ); Sat, 21 May 2022 05:06:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50578 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238688AbiEUJG3 (ORCPT ); Sat, 21 May 2022 05:06:29 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id A5B5E3C493 for ; Sat, 21 May 2022 02:06:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1653123986; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=e9LHz14wFa2/WI+cnfgVklfc1muOyIoWusP/XZeOz08=; b=Mq8xHTn92c1YO2I8aPgP2FBk6nAkCDJ1BJA3VpUAbxDP+k3nMdkqWYYFdImy1KDoc9GBWv sdhjFB67YBwaDd8MnoNbrr/pfQsgCLYG+VsY8LvuJ9IZW7KE77uEedrWgze7TvCcHR3/Yz po9Rxe3DNoi/U4AyoHAosWPb8PwqWBA= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-26-ZYJjD5BaM2-WrETeqRjSdw-1; Sat, 21 May 2022 05:06:24 -0400 X-MC-Unique: ZYJjD5BaM2-WrETeqRjSdw-1 Received: by mail-wr1-f69.google.com with SMTP id s16-20020adfeb10000000b0020cc4e5e683so3074915wrn.6 for ; Sat, 21 May 2022 02:06:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=e9LHz14wFa2/WI+cnfgVklfc1muOyIoWusP/XZeOz08=; b=Up3sX/Eb1I2Va2umRZvbb1ghG6uuWpGBLVueV6znK1T5eKnlySK4+SE0tFTxe4Yow+ NkL73xpNdgDowLDXyiL9c+QvP+RoAjHpHstiw+4JAw0NGriGexwJIatsgOHroQkFU28+ Zy+ce5MZ7M5/PDfJJa0IsEEQ1P5K+2j4iYeiXdj3e7ghTrGrgI0hZZhBpuhAJPJOzfvS B1nS+AEne6wmg/HDrfwqcQX2ZWWpI0y7FOE5hRK2kHozpSobQQLvvP/boUkOS1O19q9q o3D80p/UdnWrZ0Ur9udC7xxyIQTTBB2cdeJrOtC6YrJBPqHCz/F3KXJZifzqKP/D/EXg Rwpg== X-Gm-Message-State: AOAM5332Rvw4U7UeEEv5TCwe0VV1RK9S3WlSiG+8QdE67Osq/35KTCXz I8UYhKYqH5NjKZHfsDyN3q7ZQzjpqO3c6xA0TAlAtYSvIXdsBGdrzYP6+WG3/mGYWu/DG3uvpG5 PXax0zQvKE8CFGcUzH98Qzg== X-Received: by 2002:a05:600c:1986:b0:394:867f:984c with SMTP id t6-20020a05600c198600b00394867f984cmr12146592wmq.20.1653123983681; Sat, 21 May 2022 02:06:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxTeDbWSfdAJKkl4YczGM0UAl7TEZvciQfkOJv5cOIeHM43M+qHKKLXGP9/j3dj+RKra7iq3w== X-Received: by 2002:a05:600c:1986:b0:394:867f:984c with SMTP id t6-20020a05600c198600b00394867f984cmr12146563wmq.20.1653123983458; Sat, 21 May 2022 02:06:23 -0700 (PDT) Received: from [192.168.1.129] (205.pool92-176-231.dynamic.orange.es. [92.176.231.205]) by smtp.gmail.com with ESMTPSA id z13-20020a7bc7cd000000b0039456fb80b3sm3750711wmk.43.2022.05.21.02.06.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 21 May 2022 02:06:23 -0700 (PDT) Message-ID: <7caec251-20e7-4a8c-93ee-b28558ec580f@redhat.com> Date: Sat, 21 May 2022 11:06:21 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH V11 09/22] LoongArch: Add boot and setup routines Content-Language: en-US To: Huacai Chen Cc: Ard Biesheuvel , Huacai Chen , Arnd Bergmann , Andy Lutomirski , Thomas Gleixner , Peter Zijlstra , Andrew Morton , David Airlie , Jonathan Corbet , Linus Torvalds , linux-arch , Linux Doc Mailing List , Linux Kernel Mailing List , Xuefeng Li , Yanteng Si , Guo Ren , Xuerui Wang , Jiaxun Yang , Stephen Rothwell , linux-efi References: <20220518092619.1269111-1-chenhuacai@loongson.cn> <20220518092619.1269111-10-chenhuacai@loongson.cn> <0bae0df1-48ae-d02f-bce4-d1f69acf269e@redhat.com> <256e0b82-5d0f-cf40-87c6-c2505d2a6d3b@redhat.com> <859d5489-9361-3db0-1da4-1417ed2fad6c@redhat.com> From: Javier Martinez Canillas In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-arch@vger.kernel.org Hello Huacai, On 5/21/22 09:37, Huacai Chen wrote: [snip] >> >> A problem with moving to subsys_initcall_sync() is that this will delay >> more when a display is available in the system, and just to cope up with >> a corner case (as mentioned the common case is native drivers as module). > OK, your method seems better, but I think moving to > subsys_initcall_sync() can make the screen display as early as > possible. > But it doesn't cover all cases. For example, you will get the same error if for example your native driver is built-in and efifb built as module. So my opinion is that instead of playing with the init call levels, is just better for you to build your native driver as a module instead of making it built-in. -- Best regards, Javier Martinez Canillas Linux Engineering Red Hat