Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp4994271img; Tue, 26 Mar 2019 23:12:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqxsMQEbsnJXeKCfKgEfvigvphf+ltpon3mVuH+X6hNk+E6dmQQVepiS1HIT22GxCEJxw1Bo X-Received: by 2002:a17:902:778a:: with SMTP id o10mr3750350pll.135.1553667159593; Tue, 26 Mar 2019 23:12:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553667159; cv=none; d=google.com; s=arc-20160816; b=pdVNRyIdkbSkGFYL4CLvMbK3oJMugXvQ6dJPaVqjEmaGQF1JxV159nsPxUDFbBrzOL HIBBqRZLlkbtHx1ON69dGiVLgolyNJ55E5Rz00tHEtvbopP4VzzXf6aAKvp6MpP2J5mO dpDk913K/ZArAv8xFsyNh+yq+aahUlcviplTFPTBSPoc1KJxWYCNRYIX7UqzsesY4ucD 09nHXb2h1GFtUOZEbdxFxvEE1SirYu1ehVefxIHrsb8tsT93IUt8ItM/gRoOi+T2nI6C sdsA/UzL8cIH1Y6NSuFc+DyRq6S8gmaxZiem8OfJOc00Sy21vsaieA93W3TdzpdmbmdW mRTw== 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:mime-version :user-agent:organization:references:in-reply-to:date:cc:to:from :subject:message-id; bh=PAilE+BXBV35WIU++gSQduxNdRtR7BBPqlF11j7ftFA=; b=bfYzKvmifNofPTkXd6gGuVuj7OpHDYmW0oZR4YtnYcW18DYPVReRviqJKfi9bz2d85 fwVTAzFSaP26I7BRq9C51OzImuSaR9UFBSaw0DcoZFe2mH0MNC/rXYGKOk8vw0loW2yy +me6VuUGcvAlmbv0BpZcul1xkCFJJKbLc/snXD/FCAb1ZGdq75YqKm7lrxbBs8noC1WK vth4it0NIj3ugcb2VBkBJtmeUJiJOTJ/wt82hg7HhaQQ6GxKscPjX6xwFQN9aL/Bkgk5 j+jpn0eiPPK80cWGJKymfsgZn/c/89n63P2PnEP1Ee8AeThgnd0r53CykVzdv/O74ou4 UCQA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i1si9775666pgq.528.2019.03.26.23.12.24; Tue, 26 Mar 2019 23:12:39 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732789AbfC0GKd (ORCPT + 99 others); Wed, 27 Mar 2019 02:10:33 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60370 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726810AbfC0GKd (ORCPT ); Wed, 27 Mar 2019 02:10:33 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id BABB2315009D; Wed, 27 Mar 2019 06:10:32 +0000 (UTC) Received: from ovpn-118-18.phx2.redhat.com (ovpn-118-18.phx2.redhat.com [10.3.118.18]) by smtp.corp.redhat.com (Postfix) with ESMTP id F34A05C231; Wed, 27 Mar 2019 06:10:31 +0000 (UTC) Message-ID: <29827fcdcdd4fb46b680a6bd184b44fca638666e.camel@redhat.com> Subject: Re: [PATCH 03/17] fpga: dfl: fme: support 512bit data width PR From: Scott Wood To: Wu Hao Cc: Alan Tull , Moritz Fischer , linux-fpga@vger.kernel.org, linux-kernel , linux-api@vger.kernel.org, Ananda Ravuri , Xu Yilun Date: Wed, 27 Mar 2019 01:10:31 -0500 In-Reply-To: <20190327043743.GA20968@hao-dev> References: <1553483264-5379-1-git-send-email-hao.wu@intel.com> <1553483264-5379-4-git-send-email-hao.wu@intel.com> <127a9356a7bf597d35dd361f2b16bf80460f0370.camel@redhat.com> <655bf2991a4f8bf6a473c91218d6dba7748520aa.camel@redhat.com> <580c6c604d3915c105f076fc7f22ab5da98598fc.camel@redhat.com> <20190327043743.GA20968@hao-dev> Organization: Red Hat Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.41]); Wed, 27 Mar 2019 06:10:32 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2019-03-27 at 12:37 +0800, Wu Hao wrote: > On Tue, Mar 26, 2019 at 04:22:34PM -0500, Scott Wood wrote: > > On Tue, 2019-03-26 at 14:33 -0500, Alan Tull wrote: > > > On Mon, Mar 25, 2019 at 5:58 PM Scott Wood wrote: > > > > > > > > Hi Scott, > > > > > > > On Mon, 2019-03-25 at 17:53 -0500, Scott Wood wrote: > > > > > On Mon, 2019-03-25 at 11:07 +0800, Wu Hao wrote: > > > > > > +#else > > > > > > +static inline void copy512(void *src, void __iomem *dst) > > > > > > +{ > > > > > > + WARN_ON_ONCE(1); > > > > > > +} > > > > > > +#endif > > > > > Likewise, this will be called if a revision 2 device is used on non- > > > > > x86 > > > > > (or on x86 with an old binutils). The driver should fall back to > > > > > 32- > > > > > bit > > > > > in such cases. > > Unfortunately revision 2 is only for integrated FPGA solution, and it > doesn't > support any fallback solution (original 32bit data partial reconfiguration > is > not supported any more), so driver has to WARN in such path. From the commit message it seemed like this was just an optimization, not something necessary to support revision 2. If there's no way to program the device without AVX512, then printing an error message and returning an error to userspace would be better than WARN_ON, since it's not actually a kernel bug. -Scott