From: Rob Herring <robh@kernel.org>
To: Jacopo Mondi <jacopo+renesas@jmondi.org>
Cc: niklas.soderlund@ragnatech.se, laurent.pinchart@ideasonboard.com,
horms@verge.net.au, geert@glider.be, mchehab@kernel.org,
sakari.ailus@linux.intel.com, hans.verkuil@cisco.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v3 8/8] ARM: dts: rcar-gen2: Remove unused VIN properties
Date: Wed, 30 May 2018 22:17:43 -0500 [thread overview]
Message-ID: <20180531031743.GA8607@rob-hp-laptop> (raw)
In-Reply-To: <1527606359-19261-9-git-send-email-jacopo+renesas@jmondi.org>
On Tue, May 29, 2018 at 05:05:59PM +0200, Jacopo Mondi wrote:
> The 'bus-width' and 'pclk-sample' properties are not parsed by the VIN
> driver and only confuse users. Remove them in all Gen2 SoC that use
> them.
>
> Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
> ---
> v3:
> - remove bus-width from dt-bindings example
> ---
> Documentation/devicetree/bindings/media/rcar_vin.txt | 1 -
> arch/arm/boot/dts/r8a7790-lager.dts | 3 ---
> arch/arm/boot/dts/r8a7791-koelsch.dts | 3 ---
> arch/arm/boot/dts/r8a7791-porter.dts | 1 -
> arch/arm/boot/dts/r8a7793-gose.dts | 3 ---
> arch/arm/boot/dts/r8a7794-alt.dts | 1 -
> arch/arm/boot/dts/r8a7794-silk.dts | 1 -
> 7 files changed, 13 deletions(-)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-05-31 3:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 15:05 [PATCH v3 0/8] media: rcar-vin: Brush endpoint properties Jacopo Mondi
2018-05-29 15:05 ` [PATCH v3 1/8] dt-bindings: media: rcar-vin: Describe optional ep properties Jacopo Mondi
2018-05-31 3:13 ` Rob Herring
2018-05-29 15:05 ` [PATCH v3 2/8] dt-bindings: media: Document data-enable-active property Jacopo Mondi
2018-05-31 3:14 ` Rob Herring
2018-06-01 10:29 ` Sakari Ailus
2018-06-01 14:58 ` jacopo mondi
2018-06-01 22:35 ` Sakari Ailus
2018-05-29 15:05 ` [PATCH v3 3/8] media: v4l2-fwnode: parse 'data-enable-active' prop Jacopo Mondi
2018-06-04 12:08 ` Niklas Söderlund
2018-05-29 15:05 ` [PATCH v3 4/8] dt-bindings: media: rcar-vin: Add 'data-enable-active' Jacopo Mondi
2018-05-31 3:16 ` Rob Herring
2018-06-04 12:10 ` Niklas Söderlund
2018-05-29 15:05 ` [PATCH v3 5/8] media: rcar-vin: Handle data-enable polarity Jacopo Mondi
2018-06-04 12:13 ` Niklas Söderlund
2018-05-29 15:05 ` [PATCH v3 6/8] dt-bindings: rcar-vin: Add 'hsync-as-de' custom prop Jacopo Mondi
2018-05-31 3:17 ` Rob Herring
2018-06-04 12:19 ` Niklas Söderlund
2018-06-12 13:29 ` jacopo mondi
2018-05-29 15:05 ` [PATCH v3 7/8] media: rcar-vin: Handle 'hsync-as-de' property Jacopo Mondi
2018-05-29 15:05 ` [PATCH v3 8/8] ARM: dts: rcar-gen2: Remove unused VIN properties Jacopo Mondi
2018-05-31 3:17 ` Rob Herring [this message]
2018-06-04 12:23 ` Niklas Söderlund
2018-06-05 7:49 ` Simon Horman
2018-06-05 8:12 ` jacopo mondi
2018-06-05 8:23 ` Geert Uytterhoeven
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=20180531031743.GA8607@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@glider.be \
--cc=hans.verkuil@cisco.com \
--cc=horms@verge.net.au \
--cc=jacopo+renesas@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=sakari.ailus@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox