From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] few minor fixes for omaps
Date: Fri, 24 Jan 2020 11:45:26 -0800 [thread overview]
Message-ID: <pull-1579895109-287828@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 03729cfa0d543bc996bf959e762ec999afc8f3d2:
soc: ti: wkup_m3_ipc: Fix race condition with rproc_boot (2019-12-17 15:18:36 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-fixes-whenever-signed
for you to fetch changes up to b0b03951544534d6d9ad4aa2787eefec988fff20:
ARM: dts: am43x-epos-evm: set data pin directions for spi0 and spi1 (2020-01-23 08:12:04 -0800)
----------------------------------------------------------------
Few minor fixes for omaps
Looks like we have wrong default memory size for beaglebone black,
it has at least 512 MB of RAM and not 256 MB. This causes an issue
when booted with GRUB2 that does not seem to pass memory info to
the kernel.
And for am43x-epos-evm the SPI pin directions need to be configured
for SPI to work.
----------------------------------------------------------------
Matwey V. Kornilov (1):
ARM: dts: am335x-boneblack-common: fix memory size
Raag Jadav (1):
ARM: dts: am43x-epos-evm: set data pin directions for spi0 and spi1
arch/arm/boot/dts/am335x-boneblack-common.dtsi | 5 +++++
arch/arm/boot/dts/am43x-epos-evm.dts | 2 ++
2 files changed, 7 insertions(+)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2020-01-24 19:45 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=pull-1579895109-287828@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=soc@kernel.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).