From: Matthias Brugger <matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: John Crispin <blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
Subject: Re: MT7623 Wifi SoC support questions
Date: Fri, 03 Jul 2015 15:44:43 +0200 [thread overview]
Message-ID: <14968847.0a6uI5oGvX@ubix> (raw)
In-Reply-To: <5593C939.1020004-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
On Wednesday, July 01, 2015 01:04:25 PM John Crispin wrote:
> Hi all,
>
> I am currently busy making the linux-mediatek support work on the MT7623
> made by Mediatek/Ralink so we can add support to OpenWrt.
>
> This SoC looks very similar to the MT8127. The main differences are that
> it uses a MT6232 pmic and has pcie/ethernet.
>
> I already managed to get lots of drivers up and running based on what
> has been posted on this list. If do however have a few questions.
It's good to hear, that you can take profit out of this effort. It clearly shows
the value of getting a SoC mainline.
>
> * I noticed that ARM_ARCH_TIMER is not selected in v4.1 If I only
> register the mtk_timer, SMP comes up but the 3 extra cores seem to get
> no timer irqs and the whole system seems to run very slow. Selecting
> ARM_ARCH_TIMER makes the system boot fine. Is mtk_timer enough for other
> MTK SoCs to work ?
I think the basic problem, at least with mt6589 was, that the cntfreq register
was not set correctly by the bootloader, which made the ARM_ARCH_TIMER
unusable.
Apart from that I think, the ARM_ARCH_TIMER will get turned off in some deep
idle state, so that you need mtk_timer (I'm not sure if this holds for mt7623
as well).
>
> * The MT7623 has a 7 port PWM that looks different to the display-pwm
> driver that was posted. This PWM has an old and new mode. Oldmode looks
> like classic period/duty cyle config, while the new mode has lots of
> complexe features. the kernel PWM subsystem can only handle oldmode
> style config right now so i was going to add a driver. is anyone working
> on this already ? is this core mt7623 specific or do other SoCs have it
> aswell ? The registers i have here are called PWMX_CON, PWMX_HDURATION,
> PWMX_LDURATION, PWMX_GDURATION ....
>
I it seems that this PWM is present in other SoCs as well.
Best regards,
Matthias
prev parent reply other threads:[~2015-07-03 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 11:04 MT7623 Wifi SoC support questions John Crispin
[not found] ` <5593C939.1020004-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2015-07-03 13:44 ` Matthias Brugger [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=14968847.0a6uI5oGvX@ubix \
--to=matthias.bgg-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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