Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@de.bosch.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
	Simon Horman <horms+renesas@verge.net.au>,
	<linux-renesas-soc@vger.kernel.org>,
	Koji Matsuoka <koji.matsuoka.xm@renesas.com>
Cc: Dirk Behme <dirk.behme@de.bosch.com>
Subject: [PATCH 0/4] ARM: Renesas: R-Car3: Add product register support
Date: Wed, 25 May 2016 10:58:24 +0200	[thread overview]
Message-ID: <1464166708-18320-1-git-send-email-dirk.behme@de.bosch.com> (raw)

Instead of hard coding the product register in rcar_du_crtc.c,
read it based on the device tree.

This patch series is based on

https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git/log/?h=topic/gen3-latest
renesas-drivers-2016-05-17-v4.6
4717ef6d59c3204e385c
Revert "ASoC: simple-card: Add pm callbacks to platform driver"

It's boot tested on r8a7795 Salvator-X and checked that the same
product register value is read without and with this patch series.

Dirk

             reply	other threads:[~2016-05-25  8:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25  8:58 Dirk Behme [this message]
2016-05-25  8:58 ` [PATCH 1/4] ARM: Renesas: R-Car3: Add product register support Dirk Behme
2016-05-25  8:58 ` [PATCH 2/4] arm64: dts: Renesas: R-Car3: Add product register Dirk Behme
2016-05-25  8:58 ` [PATCH 3/4] ARM: Renesas: R-Car3: Add cpu and revision handlers Dirk Behme
2016-05-25  8:58 ` [PATCH 4/4] drm: rcar-du: Use product register framework Dirk Behme
2016-05-27  3:40   ` Magnus Damm
2016-05-27  8:16     ` Dirk Behme
2016-05-27  9:56       ` Magnus Damm
2016-05-27 10:18         ` Dirk Behme
2016-06-01  2:33           ` Magnus Damm
2016-05-26  7:14 ` [PATCH 0/4] ARM: Renesas: R-Car3: Add product register support Geert Uytterhoeven
2016-05-26  7:48   ` Dirk Behme
2016-05-27  3:13     ` Magnus Damm
2016-05-27  7:56       ` Dirk Behme
2016-05-27  8:39         ` Geert Uytterhoeven
2016-05-27  8:44           ` Dirk Behme
2016-05-27  9:00             ` Geert Uytterhoeven
2016-06-01  5:19         ` Magnus Damm
2016-06-01  7:19           ` Dirk Behme
2016-06-01  7:27             ` Geert Uytterhoeven
2016-06-01  7:38               ` Dirk Behme
2016-06-01  8:26                 ` Geert Uytterhoeven
2016-06-01  8:36                   ` Dirk Behme
2016-06-01  8:40                     ` Geert Uytterhoeven
2016-06-01  8:43                       ` Dirk Behme
2016-06-29  7:58           ` Dirk Behme

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=1464166708-18320-1-git-send-email-dirk.behme@de.bosch.com \
    --to=dirk.behme@de.bosch.com \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=koji.matsuoka.xm@renesas.com \
    --cc=linux-renesas-soc@vger.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