Received: by 10.223.185.116 with SMTP id b49csp7051987wrg; Wed, 28 Feb 2018 22:00:52 -0800 (PST) X-Google-Smtp-Source: AG47ELvi84TuaalUA1uIaQj5ipDywPqfx0Gz+CVPhfE7mZPC1ufYsbUlNi0wjQ2iViBAG3idfkdl X-Received: by 10.99.164.25 with SMTP id c25mr622880pgf.235.1519884052322; Wed, 28 Feb 2018 22:00:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519884052; cv=none; d=google.com; s=arc-20160816; b=pZXDdEJflgRRe2sC+bUUUVCw49xpGe9bWNxUQcNL4nQ2Vh0u040rN8xkymSAT6xFn2 5p50JWisvilaiFPfTYDUJhOlMZKKf6IHCJpDI1ZVFgq8w+goQwToDp7+rz5lnGiSVPx0 CFobJIgp/5yMK/oosaSiyLOe1ORhOvvTEXyRJ1HJsDNj5IvIf2CaBCNIHqgT+IpsMNSw LMF7V4kmdWgf5uYpFPHvTK7PHk1vjMdAuP9Thfv/KJFHfcWEQHufo2dH519sp+rxQpmQ 14+XtnUD9z/M7jSBa88ElArwhFiGGPOMJYYOa9ozsLS0RuztxSMSbaHK7ADPHnxELV6g FHww== 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=JKen+c9PtLISzO4Lj0I2m5q+Sxno5dJLYd6F2YZgx64=; b=z+Tw706E84UrMeKDdCa13zOM5BjqOdQrLgab5VrtSCBCN6lNeDg/MpfghmvZJd2S7Q wTkwyS/PexPp+dpgnw8uXt+CweV5O6xz8ytEDqlwyin/+gC1WiPV4XO1lCFD+Um37lGe tQBNfg+oYYswD1Xcf1psyhz+h+0whfWNBRCBIxbPGaqap6jRlO2Fb7ZAADWjH6MTE5JK TK5tY+Ljqdrm+cAi0R0vsbKPFJeoSpT3sXiC+XFJaV9AbQ64pbOSH7BSSi/MWnsxpAZF XCS7+IIyo8MqsImPRo4X9wYeON6F3I8O6qqlWRZCyNwISGMjBV4l6GrYn9V6m5zIWB2h mk4Q== 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 b1si2037332pgn.191.2018.02.28.22.00.36; Wed, 28 Feb 2018 22:00:52 -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 S966270AbeCAF7Y (ORCPT + 99 others); Thu, 1 Mar 2018 00:59:24 -0500 Received: from mga03.intel.com ([134.134.136.65]:10832 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966037AbeCAF7W (ORCPT ); Thu, 1 Mar 2018 00:59:22 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Feb 2018 21:59:21 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,407,1515484800"; d="scan'208";a="178982993" Received: from hao-dev.bj.intel.com (HELO localhost) ([10.238.157.61]) by orsmga004.jf.intel.com with ESMTP; 28 Feb 2018 21:59:17 -0800 Date: Thu, 1 Mar 2018 13:49:35 +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 15/24] fpga: dfl-fme-pr: add compat_id support for dfl-fme-region platform device. Message-ID: <20180301054935.GA8999@hao-dev> References: <1518513893-4719-1-git-send-email-hao.wu@intel.com> <1518513893-4719-16-git-send-email-hao.wu@intel.com> 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 Wed, Feb 28, 2018 at 05:06:57PM -0600, Alan Tull wrote: > On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote: > > Hi Hao, > > > This patch adds compat_id support when driver creates the platform > > device for dfl-fme-region. It allows dfl-fme-region platform driver > > to create fpga-region with correct compat_id. > > > > Signed-off-by: Wu Hao > > --- > > drivers/fpga/dfl-fme-pr.c | 20 ++++++++++++++++++++ > > drivers/fpga/dfl-fme-pr.h | 3 +++ > > 2 files changed, 23 insertions(+) > > > > diff --git a/drivers/fpga/dfl-fme-pr.c b/drivers/fpga/dfl-fme-pr.c > > index 526e90b..c17170b 100644 > > --- a/drivers/fpga/dfl-fme-pr.c > > +++ b/drivers/fpga/dfl-fme-pr.c > > @@ -314,6 +314,25 @@ static void fpga_fme_destroy_bridges(struct feature_platform_data *pdata) > > } > > > > /** > > + * fpga_fme_get_region_compat_id - read region compat_id from hardware > > + * > > + * @dev: fme device. > > + */ > > +static struct fpga_region_compat_id > > +fpga_fme_get_region_compat_id(struct device *dev) > > +{ > > + struct fpga_region_compat_id compat_id; > > + void __iomem *fme_pr; > > + > > + fme_pr = get_feature_ioaddr_by_id(dev, FME_FEATURE_ID_PR_MGMT); > > + > > + compat_id.id_l = readq(fme_pr + FME_PR_INTFC_ID_L); > > + compat_id.id_h = readq(fme_pr + FME_PR_INTFC_ID_H); > > I tried building for 32 bit ARM and ran into readq and writeq not > being defined. v2 had proper '#indef readq/writeq', so looks like we > need that after all. Sorry, it's missing a header file for dfl-fme-pr.h, as some files don't include dfl.h at this version. That header file has definitions for readq/writeq. +#include will fix it. Thanks Hao > Alan