From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm: Updates of soc drivers for v4.15-next
Date: Wed, 20 Dec 2017 20:16:37 +0100 [thread overview]
Message-ID: <7044d4f3-1e0b-3485-0963-170a792ff4f2@gmail.com> (raw)
Hi Arnd and Olof,
Please take the following patches into account.
Thanks,
Matthias
---
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git
tags/v4.15-next-soc
for you to fetch changes up to 579c60686a086f250c82c76778eb1839394e54ef:
soc: mediatek: add MT2712 scpsys support (2017-12-20 18:30:29 +0100)
----------------------------------------------------------------
- change kconfig entry for armv7 SoCs to be more generic
- add support for mt2701 scpsys driver
binding documentation
extend driver to allow the bus protection to overwrite the register
----------------------------------------------------------------
Sean Wang (1):
ARM: mediatek: use more generic prompts for SoCs with ARMv7
weiyi.lu at mediatek.com (4):
dt-bindings: soc: add MT2712 power dt-bindings
soc: mediatek: extend bus protection API
soc: mediatek: add dependent clock jpgdec/audio for scpsys
soc: mediatek: add MT2712 scpsys support
.../devicetree/bindings/soc/mediatek/scpsys.txt | 3 +
arch/arm/mach-mediatek/Kconfig | 2 +-
drivers/soc/mediatek/mtk-infracfg.c | 26 +++-
drivers/soc/mediatek/mtk-scpsys.c | 140 ++++++++++++++++++---
include/dt-bindings/power/mt2712-power.h | 26 ++++
include/linux/soc/mediatek/infracfg.h | 7 +-
6 files changed, 181 insertions(+), 23 deletions(-)
create mode 100644 include/dt-bindings/power/mt2712-power.h
next reply other threads:[~2017-12-20 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 19:16 Matthias Brugger [this message]
2017-12-21 10:19 ` [GIT PULL] arm: Updates of soc drivers for v4.15-next Matthias Brugger
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=7044d4f3-1e0b-3485-0963-170a792ff4f2@gmail.com \
--to=matthias.bgg@gmail.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).