Received: by 10.223.185.116 with SMTP id b49csp3231350wrg; Mon, 5 Mar 2018 17:08:14 -0800 (PST) X-Google-Smtp-Source: AG47ELtaaveRyPwngPDMaFBzvpVFySLRFGs7+Rme86lTy+tWIv/JYL+U8kCLDoscPVdX4EZRS5K+ X-Received: by 10.98.147.156 with SMTP id r28mr17260698pfk.204.1520298494180; Mon, 05 Mar 2018 17:08:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520298494; cv=none; d=google.com; s=arc-20160816; b=D5V0RXDoY/JLDq++pchnDw2ukWhv3UKHN50/s8dGEw3BO1HyLn7UgELqarISNy1Ku0 Q1oajuE4uqElSEcr4oy3FM9f0/JlkzzeRBNaccwn8029sKCf4/L+wdVTyPTogMVhLz3R k/LgsG1RCg8R287QV4lxT3sRWQImQdOejxcwxP2VTCforBMjooo69gJMleiTgIlaZap2 vX+rTM+3/dsxrAcPqM/vLet8WehyIxZH9ir83har/iAFGxn53qTza6lFu/qAdxX26Hxm xuDbE+3VTo5TYdC2PaiSFRlxrFVBytW3K5TebdfelKVk5k3D20VGsQBVU6xf3G2vWh10 zgbg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=mRJQ5GmPbLHNDxJq+z6QMi8o6jkuU+dpypvCSuZ7OPs=; b=aRZwdi+Pm35F0Mv7pnE3rs/mqYBAJ+WAxG/NPQPrFkbw404dQXamaTRJC6AhfTv9z4 TnjZEYGWBcWDrHUSSz4SQ9t3jd/ZJPm/4/zDdxzSLCxsF87DZcLMkdIEMdLAsTsyDJLr X5D/hr7DDX+Oq0mmFnmLcKaUbyG9ghoi9u78nXwVzbbRfsnLDRmjV5nmBCI2Dp/h4ev8 S/GDkmKG2piHtxVR6Otp2O89VHkDiUFmWUhKmZOJHuC48dNsskGybTEZNGaOC8jafjk1 KMmUTvDPGIY7Tjc7ALRaE/RtUluv5l662ZrSDBbm3xunT0BKqk3Aqgn0s4C2y9nm/7SZ Mgeg== 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 j186si9044219pgc.578.2018.03.05.17.07.59; Mon, 05 Mar 2018 17:08:14 -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 S1753007AbeCFBGr (ORCPT + 99 others); Mon, 5 Mar 2018 20:06:47 -0500 Received: from mga06.intel.com ([134.134.136.31]:42051 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752063AbeCFBGp (ORCPT ); Mon, 5 Mar 2018 20:06:45 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Mar 2018 17:06:44 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,429,1515484800"; d="scan'208";a="34878960" Received: from hao-dev.bj.intel.com (HELO localhost) ([10.238.157.61]) by fmsmga004.fm.intel.com with ESMTP; 05 Mar 2018 17:06:43 -0800 Date: Tue, 6 Mar 2018 08:56:58 +0800 From: Wu Hao To: Alan Tull Cc: Moritz Fischer , linux-fpga@vger.kernel.org, linux-kernel , linux-api@vger.kernel.org, "Kang, Luwei" , "Zhang, Yi Z" Subject: Re: [PATCH v4 13/24] fpga: region: add compat_id support Message-ID: <20180306005658.GA32057@hao-dev> References: <1518513893-4719-1-git-send-email-hao.wu@intel.com> <1518513893-4719-14-git-send-email-hao.wu@intel.com> <20180301061750.GB8999@hao-dev> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 05, 2018 at 01:42:41PM -0600, Alan Tull wrote: > On Thu, Mar 1, 2018 at 12:17 AM, Wu Hao wrote: > > On Wed, Feb 28, 2018 at 04:55:15PM -0600, Alan Tull wrote: > >> On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote: > >> > >> Hi Hao, > > > > Hi Alan, > > > > Thanks for the review. > > > >> > >> > This patch introduces a compat_id member and sysfs interface for each > >> > fpga-region, e.g userspace applications could read the compat_id > >> > from the sysfs interface for compatibility checking before PR. > >> > > >> > Signed-off-by: Wu Hao > >> > --- > >> > Documentation/ABI/testing/sysfs-class-fpga-region | 5 +++++ > >> > drivers/fpga/fpga-region.c | 19 +++++++++++++++++++ > >> > include/linux/fpga/fpga-region.h | 13 +++++++++++++ > >> > 3 files changed, 37 insertions(+) > >> > create mode 100644 Documentation/ABI/testing/sysfs-class-fpga-region > >> > > >> > diff --git a/Documentation/ABI/testing/sysfs-class-fpga-region b/Documentation/ABI/testing/sysfs-class-fpga-region > >> > new file mode 100644 > >> > index 0000000..419d930 > >> > --- /dev/null > >> > +++ b/Documentation/ABI/testing/sysfs-class-fpga-region > >> > @@ -0,0 +1,5 @@ > >> > +What: /sys/class/fpga_region//compat_id > >> > +Date: February 2018 > >> > +KernelVersion: 4.16 > >> > +Contact: Wu Hao > >> > +Description: FPGA region id for compatibility check. > > It would be helpful to add some explanation here that although the > intended function of compat_id is set, the way the actual value is > defined or calculated is set by the layer that is creating the FPGA > region. Sure. Description: FPGA region id for compatibility check, e.g compatibility of the FPGA reconfiguration hardware and image. This value is defined or calculated by the layer that is creating the FPGA region. This interface returns the compat_id value or just error code -ENOENT in case compat_id is not used. > > >> > diff --git a/drivers/fpga/fpga-region.c b/drivers/fpga/fpga-region.c > >> > index 660a91b..babec96 100644 > >> > --- a/drivers/fpga/fpga-region.c > >> > +++ b/drivers/fpga/fpga-region.c > >> > @@ -162,6 +162,24 @@ int fpga_region_program_fpga(struct fpga_region *region) > >> > } > >> > EXPORT_SYMBOL_GPL(fpga_region_program_fpga); > >> > > >> > +static ssize_t compat_id_show(struct device *dev, > >> > + struct device_attribute *attr, char *buf) > >> > +{ > >> > + struct fpga_region *region = to_fpga_region(dev); > >> > >> This looks good, but not all users of FPGA are going to use compat_id. > >> How would you feel about making it a pointer in struct fpga_region? > >> With compat_id as a pointer, could check for non-null compat_id > >> pointer and return an error if it wasn't initialized. > > > > It sounds good to me. > > > > if (!region->compat_id) > > return -ENOENT; > > Yes, thanks! Thanks for the review. Hao > > Alan > > > > >> > >> > + > >> > + return sprintf(buf, "%016llx%016llx\n", > >> > + (unsigned long long)region->compat_id.id_h, > >> > + (unsigned long long)region->compat_id.id_l); > >> > +} > >> > + > >> > +static DEVICE_ATTR_RO(compat_id); > >> > + > >> > +static struct attribute *fpga_region_attrs[] = { > >> > + &dev_attr_compat_id.attr, > >> > + NULL, > >> > +}; > >> > +ATTRIBUTE_GROUPS(fpga_region); > >> > + > >> > int fpga_region_register(struct fpga_region *region) > >> > { > >> > struct device *dev = region->parent; > >> > @@ -226,6 +244,7 @@ static int __init fpga_region_init(void) > >> > if (IS_ERR(fpga_region_class)) > >> > return PTR_ERR(fpga_region_class); > >> > > >> > + fpga_region_class->dev_groups = fpga_region_groups; > >> > fpga_region_class->dev_release = fpga_region_dev_release; > >> > > >> > return 0; > >> > diff --git a/include/linux/fpga/fpga-region.h b/include/linux/fpga/fpga-region.h > >> > index 423c87e..bf97dcc 100644 > >> > --- a/include/linux/fpga/fpga-region.h > >> > +++ b/include/linux/fpga/fpga-region.h > >> > @@ -6,6 +6,17 @@ > >> > #include > >> > > >> > /** > >> > + * struct fpga_region_compat_id - FPGA Region id for compatibility check > >> > + * > >> > + * @id_h: high 64bit of the compat_id > >> > + * @id_l: low 64bit of the compat_id > >> > + */ > >> > +struct fpga_region_compat_id { > >> > + u64 id_h; > >> > + u64 id_l; > >> > >> I guess each user will choose how to define these bits. > > > > Yes. > > > >> > >> > +}; > >> > + > >> > +/** > >> > * struct fpga_region - FPGA Region structure > >> > * @dev: FPGA Region device > >> > * @parent: parent device > >> > @@ -13,6 +24,7 @@ > >> > * @bridge_list: list of FPGA bridges specified in region > >> > * @mgr: FPGA manager > >> > * @info: FPGA image info > >> > + * @compat_id: FPGA region id for compatibility check. > >> > * @priv: private data > >> > * @get_bridges: optional function to get bridges to a list > >> > * @groups: optional attribute groups. > >> > @@ -24,6 +36,7 @@ struct fpga_region { > >> > struct list_head bridge_list; > >> > struct fpga_manager *mgr; > >> > struct fpga_image_info *info; > >> > + struct fpga_region_compat_id compat_id; > >> > >> Here it would be a pointer instead. > > > > Yes. Will update this patch. > > > > Thanks > > Hao > > > >> > >> Alan > >> > >> > void *priv; > >> > int (*get_bridges)(struct fpga_region *region); > >> > const struct attribute_group **groups; > >> > -- > >> > 2.7.4 > >> > > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-fpga" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html