From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2] edac: synopsys: Added EDAC support for zynq ddr ecc controller
Date: Thu, 10 Apr 2014 08:01:36 +0200 [thread overview]
Message-ID: <534633C0.9090905@monstr.eu> (raw)
In-Reply-To: <20140408204047.GQ30077@pd.tnic>
Hi Borislav and Punnaiah,
some comments below.
>> diff --git a/drivers/edac/synopsys_edac.c b/drivers/edac/synopsys_edac.c
>> new file mode 100644
>> index 0000000..7cec331
>> --- /dev/null
>> +++ b/drivers/edac/synopsys_edac.c
>> @@ -0,0 +1,614 @@
>> +/*
>> + * Synopsys DDR ECC Driver
>> + * This driver is based on ppc4xx_edac.c drivers
>> + *
>> + * Copyright (C) 2012 - 2014 Xilinx, Inc.
>
> The same question to you: are you going to maintain this driver? If so,
> please consider adding yourself to the MAINTAINERS file so that people
> reporting issues with it can send you a note.
Just add it to Zynq maintainer fragment as we are doing for non zynq/xilinx
drivers.
>> +/**
>> + * struct synopsys_edac_priv - DDR memory controller private instance data
>> + * @baseaddr: Base address of the DDR controller
>> + * @ce_count: Correctable Error count
>> + * @ue_count: Uncorrectable Error count
>> + */
>> +struct synopsys_edac_priv {
>> + void __iomem *baseaddr;
>> + u32 ce_count;
>> + u32 ue_count;
>> +};
>> +
>> +/**
>
> Why do we need the kernel-doc annotation for all those static functions?
I don't want to fight on this but having documentation help with reading
the code. I also don't think that only non static functions are documented.
I can't see any problem to have kernel-doc for static functions.
At least the is the first time when someone saying that only some functions
should be documented.
> Also, drop the "synopsys_edac_" prefix of all static functions - that'll
> slim up the code even further.
I don't think this is good to do. When we remove this prefix entirely
it is bigger chance that the same function name will be used by another driver.
It is not a problem with linking but the same functions names will be listed
in System.map which will complicate debugging.
For ARM multiplatform kernel I think that it is almost must to use
vendor prefixes for all platform/driver code.
All drivers can use instead of name_probe just probe but I don't think
this is the right way to go.
The rest was commented by Punnaiah.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140410/7a6702b1/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Michal Simek <monstr@monstr.eu>
To: Borislav Petkov <bp@alien8.de>
Cc: Punnaiah Choudary Kalluri <punnaiah.choudary.kalluri@xilinx.com>,
dougthompson@xmission.com, linux-edac@vger.kernel.org,
michal.simek@xilinx.com, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, rob@landley.net, sorenb@xilinx.com,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kpc528@gmail.com,
kalluripunnaiahchoudary@gmail.com, punnaia@xilinx.com
Subject: Re: [RFC PATCH v2] edac: synopsys: Added EDAC support for zynq ddr ecc controller
Date: Thu, 10 Apr 2014 08:01:36 +0200 [thread overview]
Message-ID: <534633C0.9090905@monstr.eu> (raw)
In-Reply-To: <20140408204047.GQ30077@pd.tnic>
[-- Attachment #1: Type: text/plain, Size: 2452 bytes --]
Hi Borislav and Punnaiah,
some comments below.
>> diff --git a/drivers/edac/synopsys_edac.c b/drivers/edac/synopsys_edac.c
>> new file mode 100644
>> index 0000000..7cec331
>> --- /dev/null
>> +++ b/drivers/edac/synopsys_edac.c
>> @@ -0,0 +1,614 @@
>> +/*
>> + * Synopsys DDR ECC Driver
>> + * This driver is based on ppc4xx_edac.c drivers
>> + *
>> + * Copyright (C) 2012 - 2014 Xilinx, Inc.
>
> The same question to you: are you going to maintain this driver? If so,
> please consider adding yourself to the MAINTAINERS file so that people
> reporting issues with it can send you a note.
Just add it to Zynq maintainer fragment as we are doing for non zynq/xilinx
drivers.
>> +/**
>> + * struct synopsys_edac_priv - DDR memory controller private instance data
>> + * @baseaddr: Base address of the DDR controller
>> + * @ce_count: Correctable Error count
>> + * @ue_count: Uncorrectable Error count
>> + */
>> +struct synopsys_edac_priv {
>> + void __iomem *baseaddr;
>> + u32 ce_count;
>> + u32 ue_count;
>> +};
>> +
>> +/**
>
> Why do we need the kernel-doc annotation for all those static functions?
I don't want to fight on this but having documentation help with reading
the code. I also don't think that only non static functions are documented.
I can't see any problem to have kernel-doc for static functions.
At least the is the first time when someone saying that only some functions
should be documented.
> Also, drop the "synopsys_edac_" prefix of all static functions - that'll
> slim up the code even further.
I don't think this is good to do. When we remove this prefix entirely
it is bigger chance that the same function name will be used by another driver.
It is not a problem with linking but the same functions names will be listed
in System.map which will complicate debugging.
For ARM multiplatform kernel I think that it is almost must to use
vendor prefixes for all platform/driver code.
All drivers can use instead of name_probe just probe but I don't think
this is the right way to go.
The rest was commented by Punnaiah.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-04-10 6:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 5:23 [RFC PATCH v2] edac: synopsys: Added EDAC support for zynq ddr ecc controller Punnaiah Choudary Kalluri
2014-03-17 5:23 ` Punnaiah Choudary Kalluri
2014-03-17 5:23 ` Punnaiah Choudary Kalluri
2014-04-03 15:00 ` Michal Simek
2014-04-03 15:00 ` Michal Simek
2014-04-08 20:40 ` Borislav Petkov
2014-04-08 20:40 ` Borislav Petkov
2014-04-09 6:04 ` punnaiah choudary kalluri
2014-04-09 6:04 ` punnaiah choudary kalluri
2014-04-09 6:04 ` punnaiah choudary kalluri
2014-04-09 11:03 ` Borislav Petkov
2014-04-09 11:03 ` Borislav Petkov
2014-04-09 17:45 ` punnaiah choudary kalluri
2014-04-09 17:45 ` punnaiah choudary kalluri
2014-04-09 17:48 ` Borislav Petkov
2014-04-09 17:48 ` Borislav Petkov
2014-04-10 6:01 ` Michal Simek [this message]
2014-04-10 6:01 ` Michal Simek
2014-04-10 9:21 ` Borislav Petkov
2014-04-10 9:21 ` Borislav Petkov
2014-04-10 9:49 ` Michal Simek
2014-04-10 9:49 ` Michal Simek
2014-04-10 9:49 ` Michal Simek
2014-04-10 10:00 ` Borislav Petkov
2014-04-10 10:00 ` Borislav Petkov
2014-04-10 10:05 ` Borislav Petkov
2014-04-10 10:05 ` Borislav Petkov
2014-04-10 10:11 ` Michal Simek
2014-04-10 10:11 ` Michal Simek
2014-04-10 10:11 ` Michal Simek
2014-04-10 10:10 ` Michal Simek
2014-04-10 10:10 ` Michal Simek
2014-04-10 10:10 ` Michal Simek
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=534633C0.9090905@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.