Received: by 2002:ac0:e34a:0:0:0:0:0 with SMTP id g10csp329436imn; Thu, 28 Jul 2022 01:47:05 -0700 (PDT) X-Google-Smtp-Source: AGRyM1thZzd7UfYbWynw2PmY9SCT4hnRZOc84Q6fVrLdcEzv2T9Iox6MP9wLLYRjempdV11IQCol X-Received: by 2002:a17:907:2e01:b0:72b:740c:1543 with SMTP id ig1-20020a1709072e0100b0072b740c1543mr20188890ejc.571.1658998025715; Thu, 28 Jul 2022 01:47:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658998025; cv=none; d=google.com; s=arc-20160816; b=hAnUObpQ3s0sSqE5Q672moKHp9O+j95MH7UWsmQ55bArGkLCnrDZldPt6XhGYhcrPv T3Khv6MfqggQSJB5I0qd5c8tx1Eq6LPNjz+RHE5AA6P4NellYRH+2kg15x6FfG1xxDaX cTTmM6ImYJLzwugZTTJ7HgV63FSHa9ZWxvns3PiUZXY0aYe+vnyh0S2mFYXPpwBKJwIo /m+WBNDJ5sFS1cZ1dR4IzVJ4HUlQRuLr03ELEoL0JRCGqmObz9hRf7en589VrRBoUAL2 T/KEJTkJuznjokDKnG0YIbwPTylTa6AXJofXxVgeIgrC5ZCcaJYWMNU8ORUvqwPQQi6D S7iw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=mQ4GccIy9hNP31xQJF2XQcbsBmG0JbUqCrFaRLMS6nA=; b=nFm3dbQcG5Na3O3RaJ/90UY5yFcHxhJhrlIn7L8D9Opmb5AGegIPw0puV/ff06E5zD fLdeMQbkaBtPh4Bvfu/OCXHkahlM7OIaCm4CO2/XrDp5Ewfz8Cr95dwbpzrpuplBeDE4 jgAruHVzbJGyP+Xoof9gCDDdu5PgwDAT7NLqOz9ZTmIf3CFfqEz4FPDGvvCvaLPhUI5f 19YKuw7o+oqyeDwwgFoWx1C50yGGS9neMPKytqxQiRClcekHWARuyVUt9U5IfWg268HW 5mcbzeY0Eb+Li+7GPsbYo7WNNgemOB0maxdJrUQdxwqd9zhGb/qVe1J3beMDcj8sLgT5 BC0w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=gLPXiL68; 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=linuxfoundation.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id my49-20020a1709065a7100b00722e66b9403si221115ejc.603.2022.07.28.01.46.41; Thu, 28 Jul 2022 01:47:05 -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=@linuxfoundation.org header.s=korg header.b=gLPXiL68; 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=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234869AbiG1H5Y (ORCPT + 99 others); Thu, 28 Jul 2022 03:57:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47604 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234866AbiG1H5V (ORCPT ); Thu, 28 Jul 2022 03:57:21 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8C47261734 for ; Thu, 28 Jul 2022 00:57:20 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id E64A061B77 for ; Thu, 28 Jul 2022 07:57:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EF143C433B5; Thu, 28 Jul 2022 07:57:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1658995039; bh=sVC6R36w9q8CDkln0Ao6dfLC7vtO3DXrKYaDh8h3Nkw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=gLPXiL68T7jk9Y8z7tguQOrvg/Z7hbirEaOMqZ5EMUHHHkHscPUEc8TPHY1S4tqbi OZ7wFZ/MapFI13B2I30GMMT2axyNSq2alk+RlnhRUHMM9gAw46ChbC/uoqJWMtrCqz YOLPKQi4ZQpKDv/G9KFwaQVpcXEcKN2mX+lTREgY= Date: Thu, 28 Jul 2022 09:57:16 +0200 From: Greg KH To: kah.jing.lee@intel.com Cc: linux-kernel@vger.kernel.org, arnd@arndb.de, rafael.j.wysocki@intel.com, tien.sung.ang@intel.com, dinh.nguyen@intel.com, Zhou@kroah.com, Furong , Pierre-Louis Bossart Subject: Re: [PATCH v2 1/3] drivers: misc: intel_sysid: Add sysid from arch to drivers Message-ID: References: <20220721123017.416438-1-kah.jing.lee@intel.com> <20220721123149.416618-1-kah.jing.lee@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220721123149.416618-1-kah.jing.lee@intel.com> X-Spam-Status: No, score=-7.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS 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 On Thu, Jul 21, 2022 at 08:31:50PM +0800, kah.jing.lee@intel.com wrote: > From: Kah Jing Lee > > Add new sysid driver. The Altera(Intel) Sysid component is generally part > of an FPGA design. The component can be hotplugged when the FPGA is > reconfigured. This driver support the component being hotplugged. > The sysid driver stores unique 32-bit id value which is similar to a > check-sum value; different components, different configuration options, > or both, can be configured to produce different id values. Timestamp field > is the unique 32-bit value that is based on the system generation time. I really do not understand what this driver does at all, sorry. It only exports 2 sysfs files. Who will use those sysfs files? What are they for? Why is a driver needed at all as all you are doing is reading 2 memory values from the device, right? Why is the kernel responsible for doing the data conversion logic and not userspace? > There are two basic ways to use the system ID core: > - Verify the system ID before downloading new software to a system. This > method can be used by software development tools, before downloading a > program to a target hardware system, if the program is compiled for > different hardware. verify it how? This is just a random value that we have no idea how to treat it. > - Check system ID after reset. If a program is running on hardware other > than the expected Platform Designer system, the program may fail to > function altogether. If the program does not crash, it can behave > erroneously in subtle ways that are difficult to debug. To protect against > this case, a program can compare the expected system ID against the system > ID core, and report an error if they do not match. Where are these ids listed to be able to verify anything? What userspace tools use this new driver? thanks, greg k-h