Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp346891yba; Wed, 3 Apr 2019 09:48:50 -0700 (PDT) X-Google-Smtp-Source: APXvYqwALfz77EiXcqc7xjlxvFWKSs9YMFOhoh1VxJcML1UyYG1KHbwiPnAj978m701TU2f43Srg X-Received: by 2002:a63:7152:: with SMTP id b18mr705603pgn.186.1554310130329; Wed, 03 Apr 2019 09:48:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554310130; cv=none; d=google.com; s=arc-20160816; b=RvwIxkZ15SYpzm+gP/JhSacCcBTBZ7REydjwHZf3b0GnlB4Buml/wRMEMxERohhOIc VKBxBYA67ODjl5vqwpVHmMeBlNfcRSRT+P9UItn1QfGTj3sTT7QPFtLznPvBJOcPa/B5 K3GtImWopWC1sVxcFd/2rnVNqjmHwl8Yke0Ythp5HeHO07FKxh2gMIIzPekfJ0lF7dsr EOC0KrLU6+9Ie1c5lMcIEy97oeukXdMXpPnqA7rlmz7a6aqN72sStO9qLHhea/+YchwO dMCSNKOJg3vQlmH61ji27bBKrh6ZT1tP84yl5Yhya2jaFagjHi504sa3NsIPraR9gV1Y 6+Jw== 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; bh=K8u+qJVWk3puiAbwA2MiT4s2T0KxTnWEgSl/MPXNyZQ=; b=ZHgKDVYyRoYzJEHoinJ8ES0jLJp0gqPw3wZGNDO0g0fpjB3lBJUCd9zUAPhulF+ejf gXb2cDZ5miz0U/KcvBKNZJE+npIO/nOfJ4KlcJN3jKGZA0JlTvQog8CeLnxcjabxctY/ fdU+Xo5iwBTRxLC9NT9R1JuiSAJEEJxZNtHs0hxZC6P9hL4YoTojgQVBsyZN6TtNgApI Fsp/oYN9bdWtJvLQbizWQX5i0ZTPiomsszZckALPpT7yeYgO3swldILfs2X8Kq3D8+Jy ScbIjFSC3ZH9c1ISU6Y+j9BGjk4wKCjAh3BaNoHNQ08rzZ2jTpxfTSMPENkLNhsmozGD AHTg== 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f11si14019087pgf.406.2019.04.03.09.48.35; Wed, 03 Apr 2019 09:48:50 -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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726531AbfDCQrp (ORCPT + 99 others); Wed, 3 Apr 2019 12:47:45 -0400 Received: from mail-ot1-f67.google.com ([209.85.210.67]:47065 "EHLO mail-ot1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726155AbfDCQro (ORCPT ); Wed, 3 Apr 2019 12:47:44 -0400 Received: by mail-ot1-f67.google.com with SMTP id s24so16003952otk.13; Wed, 03 Apr 2019 09:47:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=K8u+qJVWk3puiAbwA2MiT4s2T0KxTnWEgSl/MPXNyZQ=; b=CvalVmyRjCG0dXYLDL5v8Bpo6N1MoqVLwOuKk0O8JLPzuHZtZghSqHcTy+X713fa86 dPep6HIcKrBMN004c2U8SFkoj31SYTKuN5WtvMfTuN/Jl8CwOv1uanNUPJ3eJ7O+VZsV p/JJw9wYIDcb8JvxGGtbvcInJIvGUIBcFWbNuW2qROiQUs4agAEWBYyviGFjaS1aC2gf I9V5jqjG2UDahm6wuoeaUpTszt6kOgngHJzAgrIb7LmrPHJAqOA6qsb7HMouWsgzXHYg MYqXpfoFYAZQBS1NyhrPZzNCIOGsF95vfFP791fRZ/So/yQSgpUbMli7YTp0Fm7SuMlR opow== X-Gm-Message-State: APjAAAVXJXCrtP3qLRyFUtI6w6N2ii+75neSyOgivS39ZaYpnvWXR2+E l+IoOfNkvnJDzVHt3BKW9j4= X-Received: by 2002:a05:6830:1654:: with SMTP id h20mr382165otr.149.1554310063637; Wed, 03 Apr 2019 09:47:43 -0700 (PDT) Received: from localhost ([130.164.62.212]) by smtp.gmail.com with ESMTPSA id k25sm6905368otj.72.2019.04.03.09.47.43 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 03 Apr 2019 09:47:43 -0700 (PDT) Date: Wed, 3 Apr 2019 09:47:42 -0700 From: Moritz Fischer To: Richard Gong Cc: Moritz Fischer , atull@kernel.org, linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org, Richard Gong Subject: Re: [PATCHv1] fpga: mgr: add FPGA configuration log Message-ID: <20190403164742.GC5752@archbook> References: <1554243943-25507-1-git-send-email-richard.gong@linux.intel.com> <20190403142022.GB5752@archbook> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Richard, On Wed, Apr 03, 2019 at 11:43:26AM -0500, Richard Gong wrote: > Hi Moritz, > > > On 4/3/19 9:20 AM, Moritz Fischer wrote: > > Hi Richard, > > > > On Tue, Apr 02, 2019 at 05:25:43PM -0500, richard.gong@linux.intel.com wrote: > > > From: Richard Gong > > > > > > Add a log for user to know FPGA configuration is successful > > > > > > Signed-off-by: Richard Gong > > > --- > > > drivers/fpga/fpga-mgr.c | 1 + > > > 1 file changed, 1 insertion(+) > > > > > > diff --git a/drivers/fpga/fpga-mgr.c b/drivers/fpga/fpga-mgr.c > > > index c386681..559e046 100644 > > > --- a/drivers/fpga/fpga-mgr.c > > > +++ b/drivers/fpga/fpga-mgr.c > > > @@ -151,6 +151,7 @@ static int fpga_mgr_write_complete(struct fpga_manager *mgr, > > > } > > > mgr->state = FPGA_MGR_STATE_OPERATING; > > > + dev_info(&mgr->dev, "Successfully programming FPGA\n"); > > > > That info is available in FPGA manager's sysfs status entry, if at all > > I'd make this a dev_dbg(). > > > > From my end I don't see how we need this really. > > We got requests from the field and they want to see a log to get know if > FPGA configuration is successfully completed. They don't want use any > additional command to get status. > > This log is useful for the user who performs FPGA configuration. > > I think we need use dev_info, since dev_dbg is not enabled by fault for most > build. Well basically it boils down to: $ dmesg | grep "Sucessfully" vs $ cat /sys/class/fpga.../status Personally not in favor of extra messages, but if we do it we should change the message to "Sucessfully programmed FPGA". I think making it a dbg message is a good trade-off ... Moritz