linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
To: krzk@kernel.org
Cc: kgene@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
	linux@armlinux.org.uk, pawel.mikolaj.chmiel@gmail.com,
	xc-racer2@live.ca, linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] ARM: dts: s5pv210: aries: Enable more drivers present on Samsung Aries based devices
Date: Fri, 28 Dec 2018 17:18:13 +0100	[thread overview]
Message-ID: <20181228161819.18931-1-pawel.mikolaj.chmiel@gmail.com> (raw)

This patchset enables more drivers for devices present on
 Samsung Aries based devices.

First patch switches fimd to correct variant, which wasn't
 present at moment of adding aries dts.

Next two patches removes hardcoded bootargs from dts files
 for galaxys and fascinate4g, because now we have working bootloader
 which can pass those values.

One of the patches also reserves memory for Samsung S5P MFC
 video codec, so it's possible to use it.

Last two patches adds and enables more drivers.

Jonathan Bakker (1):
  ARM: dts: s5pv210: aries: Support for more devices present on Aries

Paweł Chmiel (5):
  ARM: dts: s5pv210: Use correct fimd variant
  ARM: dts: s5pv210: galaxys: Remove hardcoded bootargs
  ARM: dts: s5pv210: fascinate4g: Remove hardcoded bootargs
  ARM: dts: s5pv210: aries: Add reserved memory for mfc
  ARM: defconfig: s5pv210: Enable more drivers present on Samsung Aries

 arch/arm/boot/dts/s5pv210-aries.dtsi      | 90 +++++++++++++++++++++++
 arch/arm/boot/dts/s5pv210-fascinate4g.dts |  7 --
 arch/arm/boot/dts/s5pv210-galaxys.dts     |  7 --
 arch/arm/boot/dts/s5pv210.dtsi            |  2 +-
 arch/arm/configs/s5pv210_defconfig        | 41 ++++++++---
 5 files changed, 121 insertions(+), 26 deletions(-)

-- 
2.17.1


             reply	other threads:[~2018-12-28 16:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-28 16:18 Paweł Chmiel [this message]
2018-12-28 16:18 ` [PATCH 1/6] ARM: dts: s5pv210: Use correct fimd variant Paweł Chmiel
2018-12-31 11:37   ` Krzysztof Kozlowski
2019-01-07 20:28   ` Krzysztof Kozlowski
2018-12-28 16:18 ` [PATCH 2/6] ARM: dts: s5pv210: galaxys: Remove hardcoded bootargs Paweł Chmiel
2019-01-07 19:20   ` Krzysztof Kozlowski
2018-12-28 16:18 ` [PATCH 3/6] ARM: dts: s5pv210: fascinate4g: " Paweł Chmiel
2019-01-07 19:20   ` Krzysztof Kozlowski
2018-12-28 16:18 ` [PATCH 4/6] ARM: dts: s5pv210: aries: Add reserved memory for mfc Paweł Chmiel
2018-12-31 11:44   ` Krzysztof Kozlowski
2018-12-28 16:18 ` [PATCH 5/6] ARM: dts: s5pv210: aries: Support for more devices present on Aries Paweł Chmiel
2018-12-31 13:35   ` Krzysztof Kozlowski
2019-01-08 16:53     ` Paweł Chmiel
2018-12-28 16:18 ` [PATCH 6/6] ARM: defconfig: s5pv210: Enable more drivers present on Samsung Aries Paweł Chmiel
2018-12-31 13:22   ` Krzysztof Kozlowski

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=20181228161819.18931-1-pawel.mikolaj.chmiel@gmail.com \
    --to=pawel.mikolaj.chmiel@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kgene@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=xc-racer2@live.ca \
    /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).