All of lore.kernel.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: linux-riscv@lists.infradead.org
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>, kernel-team@android.com
Subject: More K210 Support
Date: Wed,  8 Apr 2020 09:57:38 -0700	[thread overview]
Message-ID: <20200408165802.167546-1-palmer@dabbelt.com> (raw)

* Builds a table of device trees, keyed by mvendorid/marchid/mimpid.  This
  allows multiple device trees to be built into the kernel.  I don't really
  like maintaining the two lists (one in C and one in assembly) or having that
  function in the table, but it's the best I could come up with.
* "handles" PMP traps by just skipping the PMP setup phase.

I don't actually have a K210 so I can't test any of this.  I also couldn't find
the K210 identifiers listed anywhere online, so someone will have to dig them
out of the board.

I also didn't spend any time thinking through how we free these device trees,
but given that .dtb.init.rodata already exists as a section I'm just guessing
that's were we're supposed to put them.




             reply	other threads:[~2020-04-08 16:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 16:57 Palmer Dabbelt [this message]
2020-04-08 16:57 ` [PATCH 1/3] RISC-V: Allow device trees to be built into the kernel Palmer Dabbelt
2020-04-08 16:57 ` [PATCH 2/3] RISC-V: K210: Add a built-in device tree Palmer Dabbelt
2020-04-09  2:19   ` Damien Le Moal
2020-04-08 16:57 ` [PATCH 3/3] RISC-V: Skip setting up PMPs on traps Palmer Dabbelt
2020-04-13  9:06   ` Damien Le Moal
2020-04-13  1:45 ` More K210 Support Damien Le Moal
2020-04-20 20:28   ` Palmer Dabbelt
2020-04-20 22:25     ` Damien Le Moal
2020-04-24 18:31       ` Palmer Dabbelt
2020-04-17  4:55 ` Damien Le Moal

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=20200408165802.167546-1-palmer@dabbelt.com \
    --to=palmer@dabbelt.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=kernel-team@android.com \
    --cc=linux-riscv@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.