All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Caesar Wang <wxt@rock-chips.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
	Sonny Rao <sonnyrao@chromium.org>,
	shawn.lin@rock-chips.com, dianders@chromium.org,
	linux-rockchip@lists.infradead.org,
	Russell King <linux@arm.linux.org.uk>,
	devicetree@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
	linux-kernel@vger.kernel.org,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 6/9] ARM: dts: add pl330-broken-no-flushp quirk for rk3036 SoCs
Date: Tue, 09 Feb 2016 18:29:50 +0100	[thread overview]
Message-ID: <1488837.V2iXLjBOmC@phil> (raw)
In-Reply-To: <1453460812-8498-7-git-send-email-wxt@rock-chips.com>

Am Freitag, 22. Januar 2016, 19:06:49 schrieb Caesar Wang:
> Pl330 integrated in rk3036 platform that doesn't support
> DMAFLUSHP function. So we add 'arm,pl330-broken-no-flushp' quirk
> for rk3036.
> 
> Signed-off-by: Caesar Wang <wxt@rock-chips.com>

applied the 3 (4/9, 5/9, 6/9) dts patches to my dts32 branch for 4.6
(after fixing the patch subjects to match the general style-convention)

WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 6/9] ARM: dts: add pl330-broken-no-flushp quirk for rk3036 SoCs
Date: Tue, 09 Feb 2016 18:29:50 +0100	[thread overview]
Message-ID: <1488837.V2iXLjBOmC@phil> (raw)
In-Reply-To: <1453460812-8498-7-git-send-email-wxt@rock-chips.com>

Am Freitag, 22. Januar 2016, 19:06:49 schrieb Caesar Wang:
> Pl330 integrated in rk3036 platform that doesn't support
> DMAFLUSHP function. So we add 'arm,pl330-broken-no-flushp' quirk
> for rk3036.
> 
> Signed-off-by: Caesar Wang <wxt@rock-chips.com>

applied the 3 (4/9, 5/9, 6/9) dts patches to my dts32 branch for 4.6
(after fixing the patch subjects to match the general style-convention)

  reply	other threads:[~2016-02-09 17:30 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 11:06 [PATCH v7 0/9] Fix broken DMAFLUSHP on Rockchips platform Caesar Wang
2016-01-22 11:06 ` Caesar Wang
2016-01-22 11:06 ` Caesar Wang
2016-01-22 11:06 ` [PATCH v7 1/9] dmaengine: pl330: support burst mode for dev-to-mem and mem-to-dev transmit Caesar Wang
2016-02-09  3:32   ` Vinod Koul
2016-02-09  3:32     ` Vinod Koul
2016-01-22 11:06 ` [PATCH v7 2/9] dt/bindings: arm-pl330: add description of arm, pl330-broken-no-flushp Caesar Wang
2016-01-22 11:06   ` Caesar Wang
2016-01-22 22:29   ` Rob Herring
2016-01-22 22:29     ` Rob Herring
2016-02-09  3:32   ` Vinod Koul
2016-02-09  3:32     ` Vinod Koul
2016-01-22 11:06 ` [PATCH v7 3/9] dmaengine: pl330: add quirk for broken no flushp Caesar Wang
2016-01-22 11:06   ` Caesar Wang
2016-02-09  3:33   ` Vinod Koul
2016-01-22 11:06 ` [PATCH v7 4/9] ARM: dts: Add arm, pl330-broken-no-flushp quirk for rk3288 platform Caesar Wang
2016-01-22 11:06   ` Caesar Wang
2016-01-22 11:06   ` Caesar Wang
2016-01-22 11:06 ` [PATCH v7 5/9] ARM: dts: Add arm, pl330-broken-no-flushp quirk for rk3xxx platform Caesar Wang
2016-01-22 11:06   ` Caesar Wang
2016-01-22 11:06   ` Caesar Wang
2016-01-22 11:06 ` [PATCH v7 6/9] ARM: dts: add pl330-broken-no-flushp quirk for rk3036 SoCs Caesar Wang
2016-01-22 11:06   ` Caesar Wang
2016-01-22 11:06   ` Caesar Wang
2016-02-09 17:29   ` Heiko Stuebner [this message]
2016-02-09 17:29     ` Heiko Stuebner
2016-01-22 11:06 ` [PATCH v7 7/9] dmaengine: core: expose max burst capability to clients Caesar Wang
2016-01-22 11:06   ` Caesar Wang
2016-02-09  3:33   ` Vinod Koul
2016-02-09  3:33     ` Vinod Koul
2016-01-22 11:06 ` [PATCH v7 8/9] dmaengine: pl330: add max burst for dmaengine Caesar Wang
2016-02-09  3:34   ` Vinod Koul
2016-01-22 11:06 ` [PATCH v7 9/9] spi: rockchip: modify DMA max burst to 1 Caesar Wang
2016-01-22 11:06   ` Caesar Wang
2016-01-22 11:06   ` Caesar Wang
2016-02-09  3:34   ` Vinod Koul
2016-02-09  3:34     ` Vinod Koul
2016-02-01  6:56 ` [PATCH v7 0/9] Fix broken DMAFLUSHP on Rockchips platform Caesar Wang
2016-02-01  6:56   ` Caesar Wang
2016-02-01  6:56   ` Caesar Wang
2016-02-08  3:11   ` Vinod Koul
2016-02-08  3:11     ` Vinod Koul
2016-02-08  3:11     ` Vinod Koul
2016-02-08  9:27     ` Heiko Stuebner
2016-02-08  9:27       ` Heiko Stuebner
2016-02-08  9:27       ` Heiko Stuebner
2016-02-08 13:14       ` Vinod Koul
2016-02-08 13:14         ` Vinod Koul
2016-02-08 13:14         ` Vinod Koul
2016-02-08 14:02         ` Mark Brown
2016-02-08 14:02           ` Mark Brown
2016-02-08 14:02           ` Mark Brown
2016-02-08 22:21         ` Heiko Stuebner
2016-02-08 22:21           ` Heiko Stuebner
2016-02-09  3:21           ` Vinod Koul
2016-02-09  3:21             ` Vinod Koul
2016-02-09  3:21             ` Vinod Koul

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=1488837.V2iXLjBOmC@phil \
    --to=heiko@sntech.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=sonnyrao@chromium.org \
    --cc=vinod.koul@intel.com \
    --cc=wxt@rock-chips.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.