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] Fixes for omaps for v5.6-rc cycle
Date: Wed, 18 Mar 2020 16:48:12 -0700 [thread overview]
Message-ID: <pull-1584575254-461940@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit cfb5d65f25959f724081bae8445a0241db606af6:
ARM: dts: dra7: Add bus_dma_limit for L3 bus (2020-03-13 07:40:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.6/fixes-rc6-signed
for you to fetch changes up to dfa7ea303f56a3a8b1ed3b91ef35af2da67ca4ee:
ARM: dts: omap5: Add bus_dma_limit for L3 bus (2020-03-17 10:01:28 -0700)
----------------------------------------------------------------
Few more fixes for omaps
Just few dts fixes:
- A fix droid4 touchscreen stopping working with lost gpio interrupts
- Also limit omap5 dma range similar to what we've recently done for dra7
----------------------------------------------------------------
Roger Quadros (1):
ARM: dts: omap5: Add bus_dma_limit for L3 bus
Tony Lindgren (1):
ARM: dts: omap4-droid4: Fix lost touchscreen interrupts
arch/arm/boot/dts/motorola-mapphone-common.dtsi | 2 +-
arch/arm/boot/dts/omap5.dtsi | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-03-18 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 23:48 Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-13 20:39 [GIT PULL] Fixes for omaps for v5.6-rc cycle Tony Lindgren
2020-03-13 20:47 ` Tony Lindgren
2020-02-28 15:26 Tony Lindgren
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-1584575254-461940@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).