From: Caleb James DeLisle <cjd@cjdns.fr>
To: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>,
linux-mips@vger.kernel.org
Cc: conor+dt@kernel.org, daniel.lezcano@kernel.org,
devicetree@vger.kernel.org, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org, naseefkm@gmail.com,
robh@kernel.org, tglx@kernel.org, grandmaster@al2klimov.de
Subject: Re: [PATCH v9 5/5] clocksource/timer-econet-en751221: Support EN751627 without percpu IRQ
Date: Thu, 15 Oct 2026 10:30:03 +0200 [thread overview]
Message-ID: <77600922-a335-4bfd-a3ad-035a516ce307@cjdns.fr> (raw)
In-Reply-To: <08095630-fd5f-49f9-b502-d5b2b33c60f4@oss.qualcomm.com>
On 15/10/2026 09:21, Daniel Lezcano wrote:
> On 10/14/26 22:36, Caleb James DeLisle wrote:
>> Hello Daniel,
>>
>> Thank you for the review.
>>
>>
>> On 14/10/2026 20:43, Daniel Lezcano wrote:
>>>
>>> Hi Caleb,
>>>
>>> with the help of a LLM, I got the following two issues with the changes
>>>
>>> On 9/18/26 17:36, Caleb James DeLisle wrote:
>>>> EN751627 is based on the 1004Kc which uses a different interrupt
>>>> number
>>>> for each CPU timer. Support both this and the EN751221 which uses a
>>>> single percpu interrupt.
>>>>
>>>> Signed-off-by: Caleb James DeLisle <cjd@cjdns.fr>
>>>> ---
>
> [ ... ]
>
>>> The binding requires four interrupts and two register blocks for
>>> EN751627, but the driver sizes its resource arrays from NR_CPUS and
>>> rejects DTs exceeding those sizes. Consequently, a UP kernel
>>> (NR_CPUS=1) or an SMP kernel configured for two CPUs rejects a valid
>>> EN751627 DT before registering any timer.
>>>
>>
>> This is a fair point, and I suppose a reasonable thing to do here is
>> instead set num_blocks = ARRAY_SIZE(econet_timer.membase) so we just
>> don't use the other blocks. I can send an updated patchset with that.
>
> IMO, econet_timer.irqs[] and econet_timer.membase[] should just be big
> enough to store all nodes without using NR_CPUS.
>
> Given you have num_irqs and num_blocks, why not just kzalloc them ?
That works for me, I'll re-send it like that then.
Thanks,
Caleb
prev parent reply other threads:[~2026-10-15 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 15:36 [PATCH v9 0/5] clocksource/timer-econet-en751221: Support irq number per timer Caleb James DeLisle
2026-09-18 15:36 ` [PATCH v9 1/5] clocksource/timer-econet-en751221: fix refcount leak Caleb James DeLisle
2026-09-18 15:36 ` [PATCH v9 2/5] dt-bindings: timer: econet: Update EN751627 for multi-IRQ Caleb James DeLisle
2026-09-18 15:36 ` [PATCH v9 3/5] clocksource/timer-econet-en751221: Init teardown on error if possible Caleb James DeLisle
2026-09-18 15:36 ` [PATCH v9 4/5] clocksource/timer-econet-en751221: Disable IRQ until cevt registered Caleb James DeLisle
2026-09-18 15:36 ` [PATCH v9 5/5] clocksource/timer-econet-en751221: Support EN751627 without percpu IRQ Caleb James DeLisle
2026-10-14 18:43 ` Daniel Lezcano
2026-10-14 20:36 ` Caleb James DeLisle
2026-10-15 7:21 ` Daniel Lezcano
2026-10-15 8:30 ` Caleb James DeLisle [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=77600922-a335-4bfd-a3ad-035a516ce307@cjdns.fr \
--to=cjd@cjdns.fr \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@kernel.org \
--cc=daniel.lezcano@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=grandmaster@al2klimov.de \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=naseefkm@gmail.com \
--cc=robh@kernel.org \
--cc=tglx@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
all inboxes | Powered by JetHome®