From: Richard Gong <richard.gong@linux.intel.com>
To: Moritz Fischer <mdf@kernel.org>
Cc: atull@kernel.org, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org,
Richard Gong <richard.gong@intel.com>
Subject: Re: [PATCHv1] fpga: mgr: add FPGA configuration log
Date: Wed, 3 Apr 2019 11:43:26 -0500 [thread overview]
Message-ID: <ee94981a-6562-9d26-ddc2-967596589599@linux.intel.com> (raw)
In-Reply-To: <20190403142022.GB5752@archbook>
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 <richard.gong@intel.com>
>>
>> Add a log for user to know FPGA configuration is successful
>>
>> Signed-off-by: Richard Gong <richard.gong@intel.com>
>> ---
>> 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
>
next prev parent reply other threads:[~2019-04-03 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 22:25 richard.gong
2019-04-03 14:20 ` Moritz Fischer
2019-04-03 16:29 ` Alan Tull
2019-04-03 16:43 ` Richard Gong [this message]
2019-04-03 16:47 ` Moritz Fischer
2019-04-03 18:05 ` Alan Tull
2019-04-03 18:37 ` Alan Tull
2019-04-03 20:08 ` Moritz Fischer
2019-04-03 21:57 ` Alan Tull
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee94981a-6562-9d26-ddc2-967596589599@linux.intel.com \
--to=richard.gong@linux.intel.com \
--cc=atull@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=richard.gong@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome