linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thor Thayer <thor.thayer@linux.intel.com>
To: James Morse <james.morse@arm.com>
Cc: bp@alien8.de, mchehab@kernel.org, linux-edac@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] EDAC, altera: Move Stratix10 SDRAM ECC to peripheral
Date: Thu, 25 Jul 2019 18:29:04 -0500	[thread overview]
Message-ID: <e88c9dd7-13af-4696-c5c1-653aaa13e805@linux.intel.com> (raw)
In-Reply-To: <eb7a1e75-2de9-cb60-bf8f-77cd1e71255f@arm.com>

Hi James,

On 7/25/19 7:46 AM, James Morse wrote:
> Hi Thor,
> 
> On 12/07/2019 19:28, thor.thayer@linux.intel.com wrote:
>> From: Thor Thayer <thor.thayer@linux.intel.com>
>>
>> ARM32 SoCFPGAs had separate IRQs for SDRAM. ARM64 SoCFPGAs
>> send all DBEs to SError so filtering by source is necessary.
>>
>> The Stratix10 SDRAM ECC is a better match with the generic
>> Altera peripheral ECC framework because the linked list can
>> be searched to find the ECC block offset and printout
>> the DBE Address.
> 
> 
>> diff --git a/drivers/edac/altera_edac.c b/drivers/edac/altera_edac.c
>> index c2e693e34d43..09a80b53acea 100644
>> --- a/drivers/edac/altera_edac.c
>> +++ b/drivers/edac/altera_edac.c
> 
>> @@ -2231,13 +2275,15 @@ static int altr_edac_a10_probe(struct platform_device *pdev)
>>   		    of_device_is_compatible(child, "altr,socfpga-dma-ecc") ||
>>   		    of_device_is_compatible(child, "altr,socfpga-usb-ecc") ||
>>   		    of_device_is_compatible(child, "altr,socfpga-qspi-ecc") ||
>> +#ifdef CONFIG_EDAC_ALTERA_SDRAM
>> +		    of_device_is_compatible(child, "altr,sdram-edac-s10") ||
>> +#endif
>>   		    of_device_is_compatible(child, "altr,socfpga-sdmmc-ecc"))
> 
> I'm just curious: This list looks suspiciously like the altr_edac_a10_device_of_match[]
> list. Is there a reason it can't use of_match_device() here?
> 
Good point. Yes, it does look very much like the match list. Although 
of_match_device() doesn't fit with the available parameters (device 
pointer), your question prompted me to look closer and I noticed 
of_match_node() is perfect.

I'll create a version 3 with this change.

Thanks for reviewing!

>>   
>>   			altr_edac_a10_device_add(edac, child);
>>   
>>   #ifdef CONFIG_EDAC_ALTERA_SDRAM
>> -		else if ((of_device_is_compatible(child, "altr,sdram-edac-a10")) ||
>> -			 (of_device_is_compatible(child, "altr,sdram-edac-s10")))
>> +		else if (of_device_is_compatible(child, "altr,sdram-edac-a10"))
>>   			of_platform_populate(pdev->dev.of_node,
>>   					     altr_sdram_ctrl_of_match,
>>   					     NULL, &pdev->dev);
> 
> 
> Acked-by: James Morse <james.morse@arm.com>
> 
> 
> Thanks,
> 
> James
> 


      reply	other threads:[~2019-07-25 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 18:28 [PATCHv2] EDAC, altera: Move Stratix10 SDRAM ECC to peripheral thor.thayer
2019-07-25 12:46 ` James Morse
2019-07-25 23:29   ` Thor Thayer [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=e88c9dd7-13af-4696-c5c1-653aaa13e805@linux.intel.com \
    --to=thor.thayer@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=james.morse@arm.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@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).