From: Anatolij Gustschin <agust@denx.de>
To: Alan Tull <atull@kernel.org>
Cc: linux-fpga@vger.kernel.org, Moritz Fischer <mdf@kernel.org>
Subject: Re: [PATCH] fpga: altera-cvp: output expected CvP VSE_PCIE_EXT_CAP_ID in error case
Date: Fri, 16 Nov 2018 01:08:17 +0100 [thread overview]
Message-ID: <20181116010817.155391d3@crub> (raw)
In-Reply-To: <CANk1AXRnahbsdbe7_XWvQudG_+Kr0exZgk2J4ay0sjM0b=bGBg@mail.gmail.com>
Hi Alan,
On Thu, 15 Nov 2018 16:28:10 -0600
Alan Tull atull@kernel.org wrote:
>On Tue, Nov 6, 2018 at 3:58 PM Anatolij Gustschin <agust@denx.de> wrote:
>
>Hi Anatolij,
>
>>
>> Output VSE_PCIE_EXT_CAP_ID register address and expected register
>> value in error message to give more info when analyzing issues
>> with loaded periphery image.
>>
>> Signed-off-by: Anatolij Gustschin <agust@denx.de>
>> ---
>> drivers/fpga/altera-cvp.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/fpga/altera-cvp.c b/drivers/fpga/altera-cvp.c
>> index 381d0c42450f..08c0080092da 100644
>> --- a/drivers/fpga/altera-cvp.c
>> +++ b/drivers/fpga/altera-cvp.c
>> @@ -413,7 +413,10 @@ static int altera_cvp_probe(struct pci_dev *pdev,
>> */
>> pci_read_config_word(pdev, VSE_PCIE_EXT_CAP_ID, &val);
>> if (val != VSE_PCIE_EXT_CAP_ID_VAL) {
>> - dev_err(&pdev->dev, "Wrong EXT_CAP_ID value 0x%x\n", val);
>> + dev_err(&pdev->dev,
>> + "Wrong VSE_PCIE_EXT_CAP_ID value 0x%04x at 0x%x, "
>> + "expected: 0x%04x\n",
>> + val, VSE_PCIE_EXT_CAP_ID, VSE_PCIE_EXT_CAP_ID_VAL);
>
>This patch adds error print info which is printing out constants.
>Wouldn't the user just be able to look at the source and know what was
>expected? I may be missing something here.
People dealing with different FPGAs asked me to add this, they didn't
want to lookup it in the code.
Thanks,
Anatolij
prev parent reply other threads:[~2018-11-16 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 21:58 [PATCH] fpga: altera-cvp: output expected CvP VSE_PCIE_EXT_CAP_ID in error case Anatolij Gustschin
2018-11-15 22:28 ` Alan Tull
2018-11-16 0:08 ` Anatolij Gustschin [this message]
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=20181116010817.155391d3@crub \
--to=agust@denx.de \
--cc=atull@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=mdf@kernel.org \
/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