public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Weijie Gao <weijie.gao@mediatek.com>
To: u-boot@lists.denx.de
Subject: [PATCH 08/16] mips: mtmips: rewrite lowlevel codes of mt7628
Date: Thu, 9 Jan 2020 16:41:42 +0800	[thread overview]
Message-ID: <1578559302.5535.22.camel@mcddlt001> (raw)
In-Reply-To: <0956cb55-0855-73b3-f59e-e9a059014f1e@gmail.com>

On Wed, 2020-01-08 at 16:56 +0100, Daniel Schwierzeck wrote:
> 
> Am 08.01.20 um 04:01 schrieb Weijie Gao:
> > This patch rewrites the mtmips architecture with the following changes:
> > 
> > 1. Move MT7628 soc parts into a subfolder.
> > 2. Lock parts of D-Cache as temporary stack.
> > 3. Reimplement DDR initialization in C language.
> > 4. Reimplement DDR calibration in a clear logic.
> > 5. Add full support for auto size detection for DDR1 and DDR2.
> > 6. Use accurate CPU clock depending for timer and delay functions.
> >    Xtal:25MHz -> CPU:575MHz / Xtal:40MHz -> CPU:580MHz.
> > 7. Remove unusable nodes from mt7628a.dtsi
> > 
> > Note:
> > 
> > print_cpuinfo() has incompatible parts with MT7620 so it's moved into
> > mt7628 subfolder.
> 
> could you refactor this patch a little bit and move the following to
> separate patches:
> - the change of sysreset driver
> - the update of global_data.h
> - the update of the device tree files
> - the removal of the deprecated drivers could be done in a separate last
> patch
> 

OK. I'll split them in to separate patches.

  reply	other threads:[~2020-01-09  8:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08  3:01 [PATCH 08/16] mips: mtmips: rewrite lowlevel codes of mt7628 Weijie Gao
2020-01-08 15:56 ` Daniel Schwierzeck
2020-01-09  8:41   ` Weijie Gao [this message]
2020-01-10 14:12 ` Stefan Roese

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=1578559302.5535.22.camel@mcddlt001 \
    --to=weijie.gao@mediatek.com \
    --cc=u-boot@lists.denx.de \
    /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