Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp1452145imp; Fri, 22 Feb 2019 03:55:04 -0800 (PST) X-Google-Smtp-Source: AHgI3Ia4IPrqvxnKOPDEpF8BDnktq/Y7GB4+uiLQiqOsUG2UDSH5e8UI9J1ek4dJnt3pK09TPY0g X-Received: by 2002:a63:4005:: with SMTP id n5mr3579482pga.86.1550836504804; Fri, 22 Feb 2019 03:55:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550836504; cv=none; d=google.com; s=arc-20160816; b=A1aICwxjTM13g69EF41shuj+9zSR4x81cyxFcn1UAplKjnkdDvzT3p8aTwHUgMWItW boytn+KaQiDEQXSagWpn1CtkcW5Yjrs/Ievy1jnLxuUmmtnQ+p7tN3Fg4lCp2YSpZMS3 Oe5fDvNr3h6fN564tuN/OEq7edbLmQSY5LuTIeFzLHpFwcYgloZD7hSgt3kx4RnwQFJm daJuSD1Q5fU0y2olNfI3x6DE5rL09CPijzoGo8a2kpKkABw8x+fAogPj7R+4Hzn2GlY7 tlFFVWeoPSRoxo7hjCtgUH61LgD/8Tpx3QMiau7GXTNpsabx/P3AqoPwYKngYOrInLoL 6P0A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=j6yxL3w9kLsVOthZIGrQHBC+SIngE5LFSxcy4GB+WRU=; b=zkQZqUJEmQUwcGum68hJFHc3jKo7qDqMVHnMCWSnWDEU0eMUBFgTHEA6oatvboiNTY A6hOh1AkOeazNMCo+n1dn073FolFwtJJ93FISFlhc6vLXHd7o66FK9exUNG5NUMrc7er 5/7hTmrEWakCzf4HrvHj3oK/K0DOVswX8q4o7l9E91uwtc6ZqBk+THJ0YMIzzxCIIjVQ 4jy4CCOPp4bRIPstGiHHMCslBHEqEkYTza9QEko6humRWN9ZiT2EBolOrNvIGrb498gN TuDFoUsTwQIr37ovQJMudtLImd4Up567LUfbaKoYZ0nN98O3TU35BCczA4ymXzHg7LAk DbNQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c19si1198926plo.410.2019.02.22.03.54.48; Fri, 22 Feb 2019 03:55:04 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726673AbfBVLy2 (ORCPT + 99 others); Fri, 22 Feb 2019 06:54:28 -0500 Received: from ns.iliad.fr ([212.27.33.1]:58798 "EHLO ns.iliad.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726087AbfBVLy1 (ORCPT ); Fri, 22 Feb 2019 06:54:27 -0500 Received: from ns.iliad.fr (localhost [127.0.0.1]) by ns.iliad.fr (Postfix) with ESMTP id B0BFE20E2A; Fri, 22 Feb 2019 12:54:25 +0100 (CET) Received: from [192.168.108.68] (freebox.vlq16.iliad.fr [213.36.7.13]) by ns.iliad.fr (Postfix) with ESMTP id 9368A20B77; Fri, 22 Feb 2019 12:54:25 +0100 (CET) Subject: Re: [PATCH v2 3/5] soc: qcom: socinfo: Expose custom attributes To: Bjorn Andersson , Laurent Pinchart Cc: Vaishali Thakkar , Andy Gross , David Brown , Greg Kroah-Hartman , MSM , LKML , Vinod Koul References: <20190220045829.6852-1-vaishali.thakkar@linaro.org> <20190221121841.GA32108@pendragon.ideasonboard.com> <20190221155742.GD2122@tuxbook-pro> From: Marc Gonzalez Message-ID: Date: Fri, 22 Feb 2019 12:54:25 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20190221155742.GD2122@tuxbook-pro> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP ; ns.iliad.fr ; Fri Feb 22 12:54:25 2019 +0100 (CET) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 21/02/2019 16:57, Bjorn Andersson wrote: > On Thu 21 Feb 04:18 PST 2019, Laurent Pinchart wrote: > >> On Wed, Feb 20, 2019 at 10:28:29AM +0530, Vaishali Thakkar wrote: >> >>> The Qualcomm socinfo provides a number of additional attributes, >>> add these to the socinfo driver and expose them via debugfs >>> functionality. >> >> What is the use case for these attributes ? I fear they will be used in >> production systems, and that would require debugfs in production, which >> isn't a good idea. If you need to expose those attributes for anything >> else than debugging then we need a proper API, likely sysfs-based. > > The use case of these attributes, beyond development/debugging, are > unfortunately somewhat unknown and is the reason why they where moved to > debugfs from the earlier attempts to upstream this. > > I think the production requirements at hand prohibits debugfs to be > present, so attributes that are required beyond development/debugging > purposes would have to be migrated out to sysfs - but the idea here is > that such migration would have come with the missing motivation to add > them there today. On a tangential note, I saw the following message when using PCIe: atl1c 0000:01:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update pcilib: sysfs_read_vpd: read failed: Connection timed out Is this in any way related to custom attributes? Regards.