Hi Rafal,
On Mon, Sep 4, 2023 at 10:34 AM Rafał Miłecki wrote:
> I'm clueless at this point.
> Maybe someone can come up with an idea of actual issue & ideally a
> solution.
Damn this is frustrating.
> 2. Clock (arm,armv7-timer)
>
> While comparing main clock in Broadcom's SDK with upstream
On Wed, Nov 29, 2023 at 10:20 PM Rafał Miłecki wrote:
> Here comes more interesting experiment though. Putting there:
>
> if (!(foo++ % 1)) {
> pr_info("[%s] arm_pm_idle:%ps\n", __func__, arm_pm_idle);
> }
>
> doesn't seem to help.
>
>
> Putting following however seems to make
I made a second attempt on debugging some longstanding stability issues
affecting BCM53753 SoCs. Those are single CPU core ARM Cortex-A7 boards
with a pretty slow arch timer running at 36,8 kHz.
After 0 to 20 minutes of close to zero activity I experience hangs and I
need to wait a minute for
Hi,
it's a late reply but I didn't find enough determination earlier.
On 8.09.2023 10:10, Linus Walleij wrote:
On Mon, Sep 4, 2023 at 10:34 AM Rafał Miłecki wrote:
I'm clueless at this point.
Maybe someone can come up with an idea of actual issue & ideally a
solution.
Damn this is
Hi Rafał,
On Mon, Sep 4, 2023 at 10:35 AM Rafał Miłecki wrote:
> 2. Clock (arm,armv7-timer)
>
> While comparing main clock in Broadcom's SDK with upstream one I noticed
> a tiny difference: mask value. I don't know it it makes any sense but
> switching from CLOCKSOURCE_MASK(56) to
