[v2,19/20] spi: sh-msiof: Document r8a77470 bindings
diff mbox series

Message ID 1554969262-15028-20-git-send-email-cv-dong@jinso.co.jp
State Not Applicable
Headers show
Series
  • Add more support to the RZ/G1C (r8a77470) SoC
Related show

Checks

Context Check Description
robh/checkpatch success

Commit Message

Cao Van Dong April 11, 2019, 7:54 a.m. UTC
Document SoC specific bindings for R-Car RZ/G1C(r8a77470) SoC.

Signed-off-by: Cao Van Dong <cv-dong@jinso.co.jp>
---
 Documentation/devicetree/bindings/spi/sh-msiof.txt | 1 +
 1 file changed, 1 insertion(+)

Comments

Simon Horman April 12, 2019, 11:10 a.m. UTC | #1
Hi Dong-san,

On Thu, Apr 11, 2019 at 04:54:21PM +0900, Cao Van Dong wrote:
> Document SoC specific bindings for R-Car RZ/G1C(r8a77470) SoC.

I think it is worth mentioning that no driver change is required as the
renesas,rcar-gen2-msiof fallback compatibility string will activate the
correct code.

> Signed-off-by: Cao Van Dong <cv-dong@jinso.co.jp>

I think this patch should be reposted including the following recipients:

Rob Herring <robh+dt@kernel.org>
Mark Rutland <mark.rutland@arm.com>
linux-spi@vger.kernel.org

As well as the following who are already included:

Mark Brown <broonie@kernel.org>
devicetree@vger.kernel.org
linux-renesas-soc@vger.kernel.org

> ---
>  Documentation/devicetree/bindings/spi/sh-msiof.txt | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/spi/sh-msiof.txt b/Documentation/devicetree/bindings/spi/sh-msiof.txt
> index 37cf695..18e14ee 100644
> --- a/Documentation/devicetree/bindings/spi/sh-msiof.txt
> +++ b/Documentation/devicetree/bindings/spi/sh-msiof.txt
> @@ -4,6 +4,7 @@ Required properties:
>  - compatible           : "renesas,msiof-r8a7743" (RZ/G1M)
>  			 "renesas,msiof-r8a7744" (RZ/G1N)
>  			 "renesas,msiof-r8a7745" (RZ/G1E)
> +			 "renesas,msiof-r8a77470" (RZ/G1C)
>  			 "renesas,msiof-r8a774a1" (RZ/G2M)
>  			 "renesas,msiof-r8a774c0" (RZ/G2E)
>  			 "renesas,msiof-r8a7790" (R-Car H2)
> -- 
> 2.7.4
>
Geert Uytterhoeven April 30, 2019, 8:32 a.m. UTC | #2
Hi Mark,

On Mon, Apr 15, 2019 at 10:53 AM Mark Brown <broonie@kernel.org> wrote:
> The patch
>
>    spi: sh-msiof: Document r8a77470 bindings
>
> has been applied to the spi tree at
>
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.2
>
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent to Linus during
> the next merge window (or sooner if it is a bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
>
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
>
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
>
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
>
> Thanks,
> Mark
>
> From efc3d5b2e79bd5470fa4a333933867d7b934a3e6 Mon Sep 17 00:00:00 2001
> From: Cao Van Dong <cv-dong@jinso.co.jp>
> Date: Thu, 11 Apr 2019 16:54:21 +0900
> Subject: [PATCH] spi: sh-msiof: Document r8a77470 bindings
>
> Document SoC specific bindings for R-Car RZ/G1C(r8a77470) SoC.
>
> Signed-off-by: Cao Van Dong <cv-dong@jinso.co.jp>
> Signed-off-by: Mark Brown <broonie@kernel.org>

Is their any specific reason this was dropped from spi/for-next again?
Upon closer look, the following seem to have been dropped as well, compared
to last week:

$ git cherry -v spi/for-next 96a9209ae8ebb4e8
+ 0e530e4eba5e9003af83c6afda833c64c7fcae08 spi: spi-mem: Fix build
error without CONFIG_SPI_MEM
+ d4a91044e241d8f87fb990b673549a7d2f9cacc4 spi: spi-mem: Make
spi_mem_default_supports_op() static inline
+ 2c54c4a640ed4dc9db03693641a1a651535f05f1 spi: pxa2xx: use a module
softdep for dw_dmac
+ bf0c999f7f0e8934c8db8261fb67a38770fffac2 spi: pxa2xx: fix SCR
(divisor) calculation
+ efc3d5b2e79bd5470fa4a333933867d7b934a3e6 spi: sh-msiof: Document
r8a77470 bindings
+ ac533755d3cb2db003785f9f770646295643bee1 spi: Remove one needless
transfer speed fall back case
+ 179f7949c0663f1923564acf0e626d459ea80047 spi: Remove warning in
spi_split_transfers_maxsize()
+ 8ed2e1a50e74a08adce3fe0207be1649b2b13a83 spi: Release spi_res after
finalizing message
+ 316e60af88bc81780a01c0f5b431affe0e679686 spi/trace: Cap buffer
contents at 64 bytes
+ 3f6e3f7843a6a1667ed890ca51a1388fc7bf3429 spi: tegra114: fix PIO transfer
+ 5127b4d69f96793dfabb602b133dc19d1aa36880 spi: pxa2xx: Add support
for Intel Comet Lake
+ bee5c20b7323a7af027d1b4ba538137b518ad232 dt-bindings: spi:
spi-mt65xx: add support for MT8516
+ 4b490710d4d24f95e95a07baac6f3f98bb94cf3b spi: expand mode support
+ ad1ac1fa0b24b40281eeccdc1d7b085e77639357 spi/spi-bcm2835: Split
transfers that exceed DLEN

Thanks!

Gr{oetje,eeting}s,

                        Geert
Mark Brown May 2, 2019, 1:36 a.m. UTC | #3
On Tue, Apr 30, 2019 at 10:32:56AM +0200, Geert Uytterhoeven wrote:

> Is their any specific reason this was dropped from spi/for-next again?
> Upon closer look, the following seem to have been dropped as well, compared
> to last week:

No...   something seems to have been eaten by the scripting at some
point which is a bit worrying, especially since git didn't notice a
forced push anywhere.

Patch
diff mbox series

diff --git a/Documentation/devicetree/bindings/spi/sh-msiof.txt b/Documentation/devicetree/bindings/spi/sh-msiof.txt
index 37cf695..18e14ee 100644
--- a/Documentation/devicetree/bindings/spi/sh-msiof.txt
+++ b/Documentation/devicetree/bindings/spi/sh-msiof.txt
@@ -4,6 +4,7 @@  Required properties:
 - compatible           : "renesas,msiof-r8a7743" (RZ/G1M)
 			 "renesas,msiof-r8a7744" (RZ/G1N)
 			 "renesas,msiof-r8a7745" (RZ/G1E)
+			 "renesas,msiof-r8a77470" (RZ/G1C)
 			 "renesas,msiof-r8a774a1" (RZ/G2M)
 			 "renesas,msiof-r8a774c0" (RZ/G2E)
 			 "renesas,msiof-r8a7790" (R-Car H2)