From: Marco Pagani <marpagan@redhat.com>
To: Xu Yilun <yilun.xu@intel.com>
Cc: Moritz Fischer <mdf@kernel.org>, Wu Hao <hao.wu@intel.com>,
Tom Rix <trix@redhat.com>,
linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org
Subject: Re: [RFC PATCH v6 3/4] fpga: add an initial KUnit suite for the FPGA Region
Date: Fri, 9 Jun 2023 12:41:27 +0200 [thread overview]
Message-ID: <4567c582-490b-37d4-d95c-987b4a892fab@redhat.com> (raw)
In-Reply-To: <ZIMLWqTT5ikCbY8g@yilunxu-OptiPlex-7050>
On 2023-06-09 13:22, Xu Yilun wrote:
> On 2023-05-31 at 11:54:04 +0200, Marco Pagani wrote:
>> The suite tests the programming of an FPGA Region with a Bridge
>> and the function for finding a particular Region.
>>
>> Signed-off-by: Marco Pagani <marpagan@redhat.com>
>> ---
>> drivers/fpga/tests/fpga-region-test.c | 186 ++++++++++++++++++++++++++
>> 1 file changed, 186 insertions(+)
>> create mode 100644 drivers/fpga/tests/fpga-region-test.c
>>
>> diff --git a/drivers/fpga/tests/fpga-region-test.c b/drivers/fpga/tests/fpga-region-test.c
>> new file mode 100644
>> index 000000000000..81b271088240
>> --- /dev/null
>> +++ b/drivers/fpga/tests/fpga-region-test.c
>> @@ -0,0 +1,186 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +/*
>> + * KUnit test for the FPGA Region
>> + *
>> + * Copyright (C) 2023 Red Hat, Inc.
>> + *
>> + * Author: Marco Pagani <marpagan@redhat.com>
>> + */
>> +
>> +#include <linux/types.h>
>> +#include <linux/module.h>
>> +#include <kunit/test.h>
>> +#include <linux/platform_device.h>
>> +#include <linux/fpga/fpga-mgr.h>
>> +#include <linux/fpga/fpga-bridge.h>
>> +#include <linux/fpga/fpga-region.h>
>> +
>> +struct mgr_stats {
>> + u32 write_count;
>> +};
>> +
>> +struct bridge_stats {
>> + u32 enable_count;
>> +};
>> +
>> +struct test_ctx {
>> + struct fpga_manager *mgr;
>> + struct platform_device *mgr_pdev;
>> + struct fpga_bridge *bridge;
>> + struct platform_device *bridge_pdev;
>> + struct fpga_region *region;
>> + struct platform_device *region_pdev;
>> + struct bridge_stats bridge_stats;
>> + struct mgr_stats mgr_stats;
>> +};
>> +
>> +static int op_write(struct fpga_manager *mgr, const char *buf, size_t count)
>> +{
>> + struct mgr_stats *stats = mgr->priv;
>> +
>> + stats->write_count++;
>
> Could you add some comments to explain why only implement the write op
> to help region test? and why not choose write_complete or other callback?
Sure, I'll do that in the next version.
Thanks,
Marco
> Thanks,
> Yilun
>
[...]
next prev parent reply other threads:[~2023-06-09 10:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 9:54 [RFC PATCH v6 0/4] fpga: add initial KUnit tests for the subsystem Marco Pagani
2023-05-31 9:54 ` [RFC PATCH v6 1/4] fpga: add an initial KUnit suite for the FPGA Manager Marco Pagani
2023-05-31 9:54 ` [RFC PATCH v6 2/4] fpga: add an initial KUnit suite for the FPGA Bridge Marco Pagani
2023-05-31 9:54 ` [RFC PATCH v6 3/4] fpga: add an initial KUnit suite for the FPGA Region Marco Pagani
2023-06-03 19:11 ` Xu Yilun
2023-06-05 16:58 ` Marco Pagani
2023-06-06 11:00 ` Xu Yilun
2023-06-07 15:57 ` Marco Pagani
2023-06-09 11:09 ` Xu Yilun
2023-06-09 10:35 ` Marco Pagani
2023-06-09 11:22 ` Xu Yilun
2023-06-09 10:41 ` Marco Pagani [this message]
2023-05-31 9:54 ` [RFC PATCH v6 4/4] fpga: add configuration for the KUnit test suites Marco Pagani
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=4567c582-490b-37d4-d95c-987b4a892fab@redhat.com \
--to=marpagan@redhat.com \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=trix@redhat.com \
--cc=yilun.xu@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;
as well as URLs for NNTP newsgroup(s).