From: Thor Thayer <thor.thayer@linux.intel.com>
To: Dinh Nguyen <dinguyen@kernel.org>,
bp@alien8.de, robh+dt@kernel.org, mark.rutland@arm.com,
mchehab@kernel.org, james.morse@arm.com
Cc: devicetree@vger.kernel.org, linux-edac@vger.kernel.org
Subject: Re: [PATCH 3/4] EDAC, altera: Skip DB IRQ for Stratix10
Date: Fri, 1 Feb 2019 10:51:55 -0600 [thread overview]
Message-ID: <4dbb757b-e44a-a0e0-d2c1-b7018f3df471@linux.intel.com> (raw)
In-Reply-To: <86856ea5-815b-6c21-f54a-d5dc0373361a@kernel.org>
Hi Dinh,
On 2/1/19 9:37 AM, Dinh Nguyen wrote:
> Hi Thor,
>
> On 1/29/19 4:03 PM, thor.thayer@linux.intel.com wrote:
>> From: Thor Thayer <thor.thayer@linux.intel.com>
>>
>> Stratix10 Double Bit errors are configured as SErrors
>> so skip the Double Bit IRQ initialization if Stratix10.
>>
>> Signed-off-by: Thor Thayer <thor.thayer@linux.intel.com>
>> ---
>> drivers/edac/altera_edac.c | 31 ++++++++++++++++++-------------
>> 1 file changed, 18 insertions(+), 13 deletions(-)
>>
>> diff --git a/drivers/edac/altera_edac.c b/drivers/edac/altera_edac.c
>> index c89d82aa2776..6a460c742e3f 100644
>> --- a/drivers/edac/altera_edac.c
>> +++ b/drivers/edac/altera_edac.c
>> @@ -1924,20 +1924,25 @@ static int altr_edac_a10_device_add(struct altr_arria10_edac *edac,
>> goto err_release_group1;
>> }
>>
>> - altdev->db_irq = irq_of_parse_and_map(np, 1);
>> - if (!altdev->db_irq) {
>> - edac_printk(KERN_ERR, EDAC_DEVICE, "Error allocating DBIRQ\n");
>> - rc = -ENODEV;
>> - goto err_release_group1;
>> - }
>> - rc = devm_request_irq(edac->dev, altdev->db_irq, prv->ecc_irq_handler,
>> - IRQF_ONESHOT | IRQF_TRIGGER_HIGH,
>> - ecc_name, altdev);
>> - if (rc) {
>> - edac_printk(KERN_ERR, EDAC_DEVICE, "No DBERR IRQ resource\n");
>> - goto err_release_group1;
>> + /* Arria10 has double bit error IRQs. Stratix10 uses SErrors */
>> + if (socfpga_is_a10()) {
>
> I see that there are socfpga_is_a10() and socfpga_is_s10() sprinkled
> around the driver. Since you're adding a specific binding for s10, would
> it make sense to remove these functions? I've gotten comments in the
> past from ARM maintainers that we want to avoid looking up platforms at
> runtime and make the differentiation at load time.
>
> Dinh
>
If there were larger differences between the Arria10 and Stratix10 then
I'd agree. The differences between Arria10 and Stratix10 are minor
because the ECC blocks are similar.
Since all the different families of Altera EDACs are in the same file, I
think the runtime allocation is warranted especially since these checks
are in the initialization functions. The interrupt handling functions
are clean.
If the maintainers have a strong preference for separate functions, I
can make that change but the Stratix10 functions will be very similar to
the Arria10 functions resulting in a much larger file.
My preference would be to keep the method in this patch but of course,
I'll follow the consensus of the maintainers.
Thanks for the review and comment!
Thor
next prev parent reply other threads:[~2019-02-01 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 22:03 [PATCH 0/4] Update Stratix10 EDAC Bindings thor.thayer
2019-01-29 22:03 ` [PATCH 1/4] Documentation: dt: edac: Fix Stratix10 IRQ bindings thor.thayer
2019-01-29 22:03 ` [PATCH 2/4] Documentation: dt: edac: Add Stratix10 Peripheral bindings thor.thayer
2019-01-29 22:03 ` [PATCH 3/4] EDAC, altera: Skip DB IRQ for Stratix10 thor.thayer
2019-02-01 15:37 ` Dinh Nguyen
2019-02-01 16:51 ` Thor Thayer [this message]
2019-01-29 22:03 ` [PATCH 4/4] arm64: dts: stratix10: Use new Stratix10 EDAC bindings thor.thayer
2019-02-19 18:53 ` [PATCH 0/4] Update Stratix10 EDAC Bindings Thor Thayer
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=4dbb757b-e44a-a0e0-d2c1-b7018f3df471@linux.intel.com \
--to=thor.thayer@linux.intel.com \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).