Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp334411yba; Wed, 3 Apr 2019 09:33:56 -0700 (PDT) X-Google-Smtp-Source: APXvYqxhVo3KQriVJln67AwPaH5TrSSBXWjww3e0TVGNFieiFy+fIA9uYtzClhoGrNfGINXKVk63 X-Received: by 2002:a63:be02:: with SMTP id l2mr627782pgf.48.1554309236606; Wed, 03 Apr 2019 09:33:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554309236; cv=none; d=google.com; s=arc-20160816; b=ah2SAVRlKzgMvuQ/uW42RywRNShbpW+EPNPfHr89oou5cnxZuky5o9JOonBYMcuTzA 5tRTHfuUTgRjK/GG9kxa4a21ng9g/1lrjgQV7dGCmi0yseCTGDzl00SfutO9ngEHkvt+ o5d6Df0DQW5vXgV5VakpemfeYZkRXHd5sr6KlY5oTCDAqkku4tnjiIuliLZk2gX6Zd9o AH3mMj1zDeBvOK9kYKqlTyfqbQdWikaqE+KFTLUcQCW6shM3Rl2n7zwROQZez2RSyTjy 5dBX3qs/G+adotb641Rinb7qmi+VIvYUwXpigU/IepOWLme6Ximu+OFqQKXU5u4oIAVH D27w== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=Hsxt14iTHa+BdincRk1Oe/8xcW5FHPfrt1SYsa7URdE=; b=HqF1EEFe4TbUOsDCZ8OB8Yuhm1oxmdUPvPqYV9YNiIjYADnvIoVUxdnllWKre7abRO /MWOOsDcMnpajnzhDY4dCp8fWi1qF0vmlIhHrTXkid7sq65wJM4wkmSLZODxXhwNgxbV aWAE4EoGNdtHmk8NbxXSEJKhufd8SNVD1d/cOByQ3qq8cBIfZBuXhCeYz/2c/RuPtvy4 /UQO7O4PS2hTN47ACd/A29yU+Wa9z9DZMHR3qyg33Vb6xw24FLKK3mWUl1g81JHDU2gI 6d1emk2bYWaFPbPOTu6aRudNH54mM91TeH7Sy5NWBBibuYLWn+YoJfuyyazpCLI0P9N5 3hPA== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w17si14134015plp.95.2019.04.03.09.33.40; Wed, 03 Apr 2019 09:33:56 -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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726310AbfDCQc4 (ORCPT + 99 others); Wed, 3 Apr 2019 12:32:56 -0400 Received: from mga18.intel.com ([134.134.136.126]:6970 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725959AbfDCQcz (ORCPT ); Wed, 3 Apr 2019 12:32:55 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Apr 2019 09:32:54 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,305,1549958400"; d="scan'208";a="146303470" Received: from marshy.an.intel.com (HELO [10.122.105.159]) ([10.122.105.159]) by FMSMGA003.fm.intel.com with ESMTP; 03 Apr 2019 09:32:53 -0700 Subject: Re: [PATCHv1] fpga: mgr: add FPGA configuration log To: Moritz Fischer Cc: atull@kernel.org, linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org, Richard Gong References: <1554243943-25507-1-git-send-email-richard.gong@linux.intel.com> <20190403142022.GB5752@archbook> From: Richard Gong Message-ID: Date: Wed, 3 Apr 2019 11:43:26 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190403142022.GB5752@archbook> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. > > Thanks, > Moritz >