From: <Claudiu.Beznea@microchip.com>
To: <alexandre.belloni@bootlin.com>
Cc: mark.rutland@arm.com, vigneshr@ti.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
pmeerw@pmeerw.net, miquel.raynal@bootlin.com,
lee.jones@linaro.org, linux-rtc@vger.kernel.org, lars@metafoo.de,
richard@nod.at, Ludovic.Desroches@microchip.com,
wg@grandegger.com, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, Tudor.Ambarus@microchip.com,
radu_nicolae.pirea@upb.ro, linux-can@vger.kernel.org,
robh+dt@kernel.org, mkl@pengutronix.de, mchehab@kernel.org,
linux-arm-kernel@lists.infradead.org, a.zummo@towertech.it,
richard.genoud@gmail.com, netdev@vger.kernel.org,
Nicolas.Ferre@microchip.com, linux-spi@vger.kernel.org,
vkoul@kernel.org, broonie@kernel.org, knaack.h@gmx.de,
dmaengine@vger.kernel.org, Eugen.Hristev@microchip.com,
jic23@kernel.org
Subject: Re: [PATCH 03/16] dt-bindings: atmel-tcb: add microchip,<chip>-tcb
Date: Fri, 10 Jan 2020 14:29:27 +0000 [thread overview]
Message-ID: <da99fbce-8341-19d2-12c9-144564d70726@microchip.com> (raw)
In-Reply-To: <20200110134001.GD1027187@piout.net>
On 10.01.2020 15:40, Alexandre Belloni wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 08/01/2020 14:55:10+0200, Claudiu Beznea wrote:
>> Add microchip,<chip>-tcb to DT bindings documentation. This is for
>> microchip,sam9x60-tcb.
>>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
>> ---
>> Documentation/devicetree/bindings/mfd/atmel-tcb.txt | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/mfd/atmel-tcb.txt b/Documentation/devicetree/bindings/mfd/atmel-tcb.txt
>> index c4a83e364cb6..e1713e41f6e0 100644
>> --- a/Documentation/devicetree/bindings/mfd/atmel-tcb.txt
>> +++ b/Documentation/devicetree/bindings/mfd/atmel-tcb.txt
>> @@ -1,6 +1,7 @@
>> * Device tree bindings for Atmel Timer Counter Blocks
>> -- compatible: Should be "atmel,<chip>-tcb", "simple-mfd", "syscon".
>> - <chip> can be "at91rm9200" or "at91sam9x5"
>> +- compatible: Should be "atmel,<chip>-tcb", "microchip,<chip>-tcb",
>> + "simple-mfd", "syscon".
>> + <chip> can be "at91rm9200", "at91sam9x5" or "sam9x60"
>
> atmel,sam9x60-tcb, microchip,at91rm9200-tcb and microchip,at91sam9x5-tcb
> are not allowed and the documentation should reflect that.
OK! I'll double check it.
>
> It would probably be easier to do that on top of the yaml conversion
> here:
> https://lore.kernel.org/lkml/20191009224006.5021-2-alexandre.belloni@bootlin.com/
I don't see this integrated in next-20200110. Am I looking at the wrong branch?
>
> --
> Alexandre Belloni, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-01-10 14:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 12:55 [PATCH 00/16] add device tree for SAM9X60 SoC and SAM9X60-EK board Claudiu Beznea
2020-01-08 12:55 ` [PATCH 01/16] dt-bindings: at_xdmac: add entry for microchip compatibles Claudiu Beznea
2020-01-08 12:55 ` [PATCH 02/16] dt-bindings: atmel-can: add microchip,sam9x60-can Claudiu Beznea
2020-01-08 12:55 ` [PATCH 03/16] dt-bindings: atmel-tcb: add microchip,<chip>-tcb Claudiu Beznea
2020-01-10 13:40 ` Alexandre Belloni
2020-01-10 14:29 ` Claudiu.Beznea [this message]
2020-01-10 14:32 ` Alexandre Belloni
2020-01-08 12:55 ` [PATCH 04/16] dt-bindings: atmel-isi: add microchip,sam9x60-isi Claudiu Beznea
2020-01-08 12:55 ` [PATCH 05/16] dt-bindings: at91-sama5d2_adc: add microchip, sam9x60-adc Claudiu Beznea
2020-01-08 12:55 ` [PATCH 06/16] dt-bindings: atmel-matrix: add microchip, sam9x60-matrix Claudiu Beznea
2020-01-08 12:55 ` [PATCH 07/16] dt-bindings: atmel-nand: add microchip,sam9x60-pmecc Claudiu Beznea
2020-01-09 19:16 ` Miquel Raynal
2020-01-08 12:55 ` [PATCH 08/16] dt-bindings: atmel-sysreg: add microchip, sam9x60-ddramc Claudiu Beznea
2020-01-08 12:55 ` [PATCH 09/16] dt-bindings: atmel-smc: add microchip,sam9x60-smc Claudiu Beznea
2020-01-08 12:55 ` [PATCH 10/16] dt-bindings: atmel-gpbr: add microchip,sam9x60-gpbr Claudiu Beznea
2020-01-08 12:55 ` [PATCH 11/16] dt-bindings: atmel, at91rm9200-rtc: add microchip, sam9x60-rtc Claudiu Beznea
2020-01-10 14:30 ` [PATCH 11/16] dt-bindings: atmel,at91rm9200-rtc: add microchip,sam9x60-rtc Alexandre Belloni
2020-01-10 15:02 ` Claudiu.Beznea
2020-01-08 12:55 ` [PATCH 12/16] dt-bindings: spi_atmel: add microchip,sam9x60-spi Claudiu Beznea
2020-01-09 21:31 ` Applied "dt-bindings: spi_atmel: add microchip, sam9x60-spi" to the spi tree Mark Brown
2020-01-08 12:55 ` [PATCH 13/16] dt-bindings: atmel-usart: add microchip,<chip>-usart Claudiu Beznea
2020-01-10 14:31 ` Alexandre Belloni
2020-01-08 12:55 ` [PATCH 14/16] dt-bindings: arm: add sam9x60-ek board Claudiu Beznea
2020-01-08 12:55 ` [PATCH 15/16] ARM: at91/defconfig: enable MMC_SDHCI_OF_AT91 and MICROCHIP_PIT64B Claudiu Beznea
2020-01-08 12:55 ` [PATCH 16/16] ARM: dts: at91: sam9x60: add device tree for soc and board Claudiu Beznea
2020-01-10 16:37 ` Nicolas.Ferre
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=da99fbce-8341-19d2-12c9-144564d70726@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Eugen.Hristev@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=radu_nicolae.pirea@upb.ro \
--cc=richard.genoud@gmail.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
--cc=vkoul@kernel.org \
--cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).