From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] rtc: armada38x: Followed the new recommendation for errata implementation
Date: Wed, 21 Dec 2016 10:44:49 +0100 [thread overview]
Message-ID: <20161221094449.gllgbgroopxmtnmp@piout.net> (raw)
In-Reply-To: <87tw9xiri9.fsf@free-electrons.com>
On 21/12/2016 at 10:02:54 +0100, Gregory CLEMENT wrote :
> Hi Alexandre,
>
> On mer., d?c. 21 2016, Alexandre Belloni <alexandre.belloni@free-electrons.com> wrote:
>
>
> I agree with all your remark expect one, see below:
> [...]
> >> rtc_update_irq(rtc->rtc_dev, 1, event);
> >>
> >> return IRQ_HANDLED;
> >> @@ -221,6 +282,11 @@ static __init int armada38x_rtc_probe(struct platform_device *pdev)
> >> if (!rtc)
> >> return -ENOMEM;
> >>
> >> + rtc->val_to_freq = devm_kcalloc(&pdev->dev, SAMPLE_NR,
> >> + sizeof(struct value_to_freq), GFP_KERNEL);
> >> + if (!rtc->val_to_freq)
> >> + return -ENOMEM;
> >> +
> >
> > The whole struct armada38x_rtc is already allocated just before. Maybe
> > you can put the whole array inside the structure instead of doing a new
> > allocation.
>
> Actually it was done on purpose. Indeed the same RTC IP is used in the
> Armada 3700 (a patch is coming soon), and for this IP this issue was
> fixed and we do not need to store 100 read. That's why I want to
> allocate the array only if needed.
>
Fair enough
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-12-21 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 11:25 [PATCH v2] rtc: armada38x: Followed the new recommendation for errata implementation Gregory CLEMENT
2016-12-21 0:43 ` Alexandre Belloni
2016-12-21 9:02 ` Gregory CLEMENT
2016-12-21 9:44 ` Alexandre Belloni [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=20161221094449.gllgbgroopxmtnmp@piout.net \
--to=alexandre.belloni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox