From: Matthias Brugger <matthias.bgg@gmail.com>
To: Daniel Palmer <daniel@0x0f.com>, linux-arm-kernel@lists.infradead.org
Subject: Re: Mainlining support for MStar ARMv7 SoCs; Where to start?
Date: Tue, 10 Sep 2019 16:59:38 +0200 [thread overview]
Message-ID: <71d30e3f-65b3-0f0e-4078-f917b5d1f075@gmail.com> (raw)
In-Reply-To: <CAFr9PXkDNy7Xh+0rLqsoSfBF5suddB_tTeFxVZfBeJz2Feq-YQ@mail.gmail.com>
Hi Daniel,
On 10/09/2019 16:18, Daniel Palmer wrote:
> Hi all,
>
> I've been working independently on support for MStar's ARMv7 SoCs for
> a few months now
> and I'm at the point where it's probably good enough for general consumption.
>
> Right now I'm sitting on a bunch of commits that adds the new machine,
> adds support for the clocks, pinctrl etc all the way up to mmc host,
> ethernet and usb. I'm sure I can't drop all of that in one go but I'm
> unsure of what the initial set of commits should look like. For
> instance does it matter if the new machine is added but it's totally
> unusable because there is no support for the clocks or should I put
> together a package that is the minimum needed to get to a shell?
>
I think a shell is the minimum you should get to.
So my take would be to send basic DTS (and clocks, if needed) so that you can
boot into a shell, even using a initramfs.
For the rest I'd propose to send each driver as a independent series. If you
want to add the DTS patch which adds the driver to your board, then make sure to
notice that it is based on the basic support.
Hope that helps.
Regards,
Matthias
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-10 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 14:18 Mainlining support for MStar ARMv7 SoCs; Where to start? Daniel Palmer
2019-09-10 14:59 ` Matthias Brugger [this message]
2019-09-10 15:10 ` Chen-Yu Tsai
2019-09-10 16:59 ` Daniel Palmer
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=71d30e3f-65b3-0f0e-4078-f917b5d1f075@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=daniel@0x0f.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;
as well as URLs for NNTP newsgroup(s).