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=-0.9 required=3.0 tests=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 BAEAAC10DCE for ; Tue, 24 Mar 2020 04:47:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 376D320663 for ; Tue, 24 Mar 2020 04:47:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=ellerman.id.au header.i=@ellerman.id.au header.b="ZKDb9UyS" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727270AbgCXEri (ORCPT ); Tue, 24 Mar 2020 00:47:38 -0400 Received: from ozlabs.org ([203.11.71.1]:46309 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725853AbgCXEri (ORCPT ); Tue, 24 Mar 2020 00:47:38 -0400 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 48mdyt6sMWz9sQt; Tue, 24 Mar 2020 15:47:33 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ellerman.id.au; s=201909; t=1585025256; bh=eqi/v0a6DbFHrDzrxmOXFZgLWISAx9HNAd7CmQW2dvY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=ZKDb9UySEgPx3dQom6x12AFQi9YWWb05OSLUxbi6q2t4U9P5skHiCRi0ClQ/9p2GN 9inTSNSA50qJFmjQ1tbgeu7ALkrHuEnHdOHjdghNq3tIHtpmiLRalTxQYCamKTnAXx N4qlqZljA8kuILxI+lDqGa927TCvNrst+I4Gsy7NKlnMaRmUb2kNaI7gHKWJye4hpe 5IBHj85XRBvR5Wyum1BJNSM9KSgCrdwjgypQQrS5VwPdk/dlaFveY04KigHP16PCHp SvFo/7rqZWrPDtrSluYShqfjhXoDH38LfWMkJvZhu7WCSzf9w9Ya7WF9p/SKbLje3R hUwOF6qNLOLxg== From: Michael Ellerman To: Chris Packham , "christophe.leroy\@c-s.fr" , "paulus\@samba.org" , "benh\@kernel.crashing.org" , "tglx\@linutronix.de" , "cai\@lca.pw" Cc: "linuxppc-dev\@lists.ozlabs.org" , "linux-kernel\@vger.kernel.org" , Hamish Martin Subject: Re: Argh, can't find dcache properties ! In-Reply-To: References: Date: Tue, 24 Mar 2020 15:47:38 +1100 Message-ID: <87tv2exst1.fsf@mpe.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Chris Packham writes: > Hi All, > > Just booting up v5.5.11 on a Freescale T2080RDB and I'm seeing the > following mesage. > > kern.warning linuxbox kernel: Argh, can't find dcache properties ! > kern.warning linuxbox kernel: Argh, can't find icache properties ! > > This was changed from DBG() to pr_warn() in commit 3b9176e9a874 > ("powerpc/setup_64: fix -Wempty-body warnings") but the message seems > to be much older than that. So it's probably been an issue on the T2080 > (and other QorIQ SoCs) for a while. That's an e6500 I think? So 64-bit Book3E. You'll be getting the default values, which is 64 bytes so I guess that works in practice. > Looking at the code the t208x doesn't specifiy any of the d-cache- > size/i-cache-size properties. Should I add them to silence the warning > or switch it to pr_debug()/pr_info()? Yeah ideally you'd add them to the device tree(s) for those boards. cheers