From: "Boris Lysov" <arzamas-16@mail.ee>
To: linux-mediatek@lists.infradead.org
Subject: [RFC] Question about contributing mt6577 support but SMP doesn't work
Date: Sat, 30 Jan 2021 03:55:57 +0200 [thread overview]
Message-ID: <1611971757.6014bcadd6ece@posti.mail.ee> (raw)
Hello! I'm working on bringing the initial support for mt6577 into
the mainline kernel. I've got the base set of hardware to work: timers,
and few interrupt controllers, and all 4 UARTs, and PL310 cache
controller. My test device boots mainline successfully and runs stable!
I'm having issues with getting SMP to work. mt6577 is a dual-core SoC,
and broken SMP means half of the processing power is unavailable. I
tried to use the existing SMP bring-up code located in
arch/arm/mach-mediatek/platsmp.c , but it didn't work albeit all
specified registers were correct. I also tried porting the SMP init
code from the downstream mediatek kernel, but it never worked either.
My question is: could I still contribute my device support patches
despite literally 50% of the CPU not working? I *strongly* doubt they
would be accepted because of it, but on the other hand devices with
mt6577 (and other compatible SoCs like mt8317) are still able to boot
and run bare mainline kernel on a single core. I ran out of ideas on
how to make that pesky 2nd core come up online with my poor knowledge.
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
reply other threads:[~2021-01-30 1:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1611971757.6014bcadd6ece@posti.mail.ee \
--to=arzamas-16@mail.ee \
--cc=linux-mediatek@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.