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=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 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 D979AC432C3 for ; Fri, 15 Nov 2019 12:01:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BA1F02073A for ; Fri, 15 Nov 2019 12:01:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727417AbfKOMBE (ORCPT ); Fri, 15 Nov 2019 07:01:04 -0500 Received: from mx2.suse.de ([195.135.220.15]:34764 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726983AbfKOMBE (ORCPT ); Fri, 15 Nov 2019 07:01:04 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 17814ACB4; Fri, 15 Nov 2019 12:01:02 +0000 (UTC) Subject: Re: Sense of soc bus? (was: [PATCH] base: soc: Export soc_device_to_device() helper) To: Geert Uytterhoeven Cc: Neil Armstrong , Greg Kroah-Hartman , Geert Uytterhoeven , linux-realtek-soc@lists.infradead.org, Tony Lindgren , Linus Walleij , Bjorn Andersson , Thierry Reding , Lee Jones , Rob Herring , Kevin Hilman , "Rafael J. Wysocki" , Michal Simek , Jonathan Hunter , NXP Linux Team , =?UTF-8?Q?Uwe_Kleine-K=c3=b6nig?= , boot-architecture@lists.linaro.org, Sascha Hauer , Fabio Estevam , "linux-tegra@vger.kernel.org" , linux-amlogic@lists.infradead.org, linux-omap@vger.kernel.org, Alexander Sverdlin , Linux ARM , Linux Kernel Mailing List , Hartley Sweeten , Pengutronix Kernel Team , Shawn Guo References: <20191103013645.9856-3-afaerber@suse.de> <20191111045609.7026-1-afaerber@suse.de> <20191111052741.GB3176397@kroah.com> <586fa37c-6292-aca4-fa7c-73064858afaf@suse.de> <20191111064040.GA3502217@kroah.com> <20191112052347.GA1197504@kroah.com> <20191112072926.isjxfa4ci6akhx56@pengutronix.de> From: =?UTF-8?Q?Andreas_F=c3=a4rber?= Organization: SUSE Software Solutions Germany GmbH Message-ID: Date: Fri, 15 Nov 2019 13:00:59 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Geert, Am 15.11.19 um 09:58 schrieb Geert Uytterhoeven: > On Fri, Nov 15, 2019 at 9:52 AM Neil Armstrong wrote: >> On 12/11/2019 11:47, Andreas Färber wrote: >>> For example, RTD1295 will support LSADC only from revision B00 >>> on (and it's not the first time I'm seeing such things in the industry). >>> So if a user complains, it will be helpful to see that information. >>> >>> Referencing your Amlogic review, with all due respect for its authors, >>> the common framework here just lets that information evaporate into the >>> deeps of sysfs. >> >> Hopefully we never had the case where needed to use the soc info in drivers, >> but now we have one and having such infrastructure already in-place will help. >> >> Renesas platforms makes a extensive usage of the soc info infrastructure to >> figure out plenty of HW parameters at runtime and lower their DT changes. > > We do our best to use it solely for detecting quirks in early SoC revisions. Got a pointer? I fail to immediately understand how sysfs would help drivers (as opposed to userspace) detect quirks: Parsing strings back doesn't sound efficient, and I don't see you exporting any custom APIs in drivers/soc/renesas/renesas-soc.c? Regards, Andreas -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)