Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp2528486iob; Fri, 20 May 2022 11:17:10 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyOjPzuXlFl/1V44LHAs35QhHZfQJWb0LTujXyUm9I9ZRlnSTi3Tj/fbKOuFzQMIAvAwi+V X-Received: by 2002:a17:907:3e8f:b0:6f4:645c:f418 with SMTP id hs15-20020a1709073e8f00b006f4645cf418mr9491683ejc.609.1653070630446; Fri, 20 May 2022 11:17:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1653070630; cv=none; d=google.com; s=arc-20160816; b=isWetRZdFOXnHaobcZFo+Wn+s0UiTrJW94dzQNNu7vKYR7ED1jvhjD62JbsrAq+Aam Hm+O/6N2Qw20vSyzkaG63Ac745+iL7Pem20YuzUEucaO3KPE+hLGa4t5MJSuiQY9ESSg CNfDVjhyHsXQ+xg1Ldkb4NIXCIJG7foVefWCjkQyEa6O99k7jQ1R1UcIg6nFJkqnyCvT d0dPGwwq5tTq/ntFVgaPP8K/C0bXiv/RO0ia3VgMzpBMd05i9ajyx9/Zkp+zK63nTXbm 7I0dlQt5QiVao+z81j0UwMtNyDSGfy/zGN1AqB2CnNbPoO7YWKuFqDG6Lf0RvHO3zDbw cdKg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=RvrP+8rCgkMvepnQXCIhMnc3T80MuXBpuTNeKYREL20=; b=mw9/L/jQAydYUezr4Tx+sr9MBbVf8dVssLE9tOm89yOuQtCSXqekN4GMwbrkkvtX2w a6EJH81ZKF1WOVM6RnJao88dQYwRWXaXjnWkQGZqJ+Fnr1vAOODndstvdyKgdlq76HB+ pDFWW5Vnrxl62/I+tGGddvuk3CBxU38xUx9o73C2Pg3WAyga5hzPvMpCnqadkoEGCtSN 4emyxnfMnsmQT78hTYChUj7J/ELOewVWQDxozGnKkR+SMSGmvlCcXTlenxYZAyAD17u+ A697pQRdmDv3RL+G3/mfi8OEfvMnajR35OkofWVFj2P2YtabjP/1lOm7IViSahmSRgVC 8yrw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chrisdown.name header.s=google header.b=hTiQI7Ph; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chrisdown.name Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id h7-20020a056402280700b004261f72c9adsi11392148ede.286.2022.05.20.11.16.44; Fri, 20 May 2022 11:17:10 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@chrisdown.name header.s=google header.b=hTiQI7Ph; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chrisdown.name Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239858AbiESOhS (ORCPT + 99 others); Thu, 19 May 2022 10:37:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52712 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239765AbiESOhP (ORCPT ); Thu, 19 May 2022 10:37:15 -0400 Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BC9D698084 for ; Thu, 19 May 2022 07:37:12 -0700 (PDT) Received: by mail-wr1-x436.google.com with SMTP id t6so7470749wra.4 for ; Thu, 19 May 2022 07:37:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chrisdown.name; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=RvrP+8rCgkMvepnQXCIhMnc3T80MuXBpuTNeKYREL20=; b=hTiQI7PhXxZLhxDo4a5AJZOqlnFOeizRqaOHA0Qjy3yRXis1s5m2aiNeY1k/AV1Nna XzXegvc6/9+lxKg+BmcB8nEn5EZEsyIRrhJhWStW1490k+Ipn2oNXoXqg11QUdN4tLyd 6R4WfNSYKuzHVazGDMnihrO+BocvrSQr9qt7w= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=RvrP+8rCgkMvepnQXCIhMnc3T80MuXBpuTNeKYREL20=; b=t9bxzXt+wNddV1GbAsnpeorLB6fVV04pWu9/4rjfby7RwU62pL6ruio/De2nHqIcBJ +tw3Jijb1YAKwxw/x4aV7lgxkjkZS2Cces1qZEjax1DS4H0Ny7qxFWoNjeZi4xAeDN2h WTj3YCL0ZOua6x42uUNz8CnwWck3++pguIfegdJzib2HBSJbigOgqbGW8mF32qQxFpTK bPqajj43pXqIUX66IVvi+hwu9l5KRs792kFCGNcblqPpq2MAWylFHKDviZDi/0HTrrdG Z+WuGihd8hVDLYyqclFj8VO779vwwHNYrdm6tnG9IRKpaJeVdygO/0Vos+CQ3BC3Q3Hi 9aaQ== X-Gm-Message-State: AOAM5323uVNfqBjl6tVjYq014gut7ZhJ/YW+RnbmSyw0r8XpXj9Tyn/j Fe4drK+1yupvlUb7lYlvnU85rQ== X-Received: by 2002:adf:c64c:0:b0:20a:79c7:4bf2 with SMTP id u12-20020adfc64c000000b0020a79c74bf2mr4266184wrg.587.1652971031327; Thu, 19 May 2022 07:37:11 -0700 (PDT) Received: from localhost ([2620:10d:c092:400::4:c1eb]) by smtp.gmail.com with ESMTPSA id c4-20020adfc6c4000000b0020c5253d8desm5081803wrh.42.2022.05.19.07.37.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 19 May 2022 07:37:10 -0700 (PDT) Date: Thu, 19 May 2022 15:37:10 +0100 From: Chris Down To: Geert Uytterhoeven Cc: Linux Kernel Mailing List , Petr Mladek , Greg Kroah-Hartman , Kernel Team Subject: Re: [RFC PATCH] printk: console: Allow each console to have its own loglevel Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.4 (c3baa83e) (2022-04-30) X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hey Geert, Geert Uytterhoeven writes: >All of the above options are appropriate for "classic" systems, >where the console device is selected using the "console=" option. > >On systems using Device tree, the serial console device is selected >using the "chosen/stout-path" property in DT, and the graphical >console is usually auto-detected and auto-enabled through DRM. >Do you envision a way to specify a specific console loglevel on the >kernel command line on such systems? Interesting question! I hadn't really thought about device tree. I actually have very little understanding of how it works to be honest :-) I'm happy to add loglevel support to device tree, I assume I'd add another property under the chosen node, like chosen/stdout-loglevel. I have some questions, though: 1. It looks like DT is standardised. Do I need to get standards approval first? 2. Is there documentation on how to reliably test DT changes? Thanks! Chris