From: <Claudiu.Beznea@microchip.com>
To: <linus.walleij@linaro.org>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <Nicolas.Ferre@microchip.com>,
<alexandre.belloni@bootlin.com>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/7] pinctrl: at91: add compatibles for SAM9X60 pin controller
Date: Thu, 31 Jan 2019 16:16:18 +0000 [thread overview]
Message-ID: <e23b96ad-b920-4caf-d774-2c5c43d7cea8@microchip.com> (raw)
In-Reply-To: <20190131123310.wwikkuiniqlcg445@M43218.corp.atmel.com>
On 31.01.2019 14:33, Ludovic Desroches wrote:
> On Thu, Jan 31, 2019 at 01:29:33PM +0100, Claudiu Beznea - M18063 wrote:
>> From: Claudiu Beznea <claudiu.beznea@microchip.com>
>>
>> Add compatibles for SAM9X60 pin controller.
>>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
>> ---
>> drivers/pinctrl/pinctrl-at91.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/pinctrl/pinctrl-at91.c b/drivers/pinctrl/pinctrl-at91.c
>> index 46443b97d811..5456a2692b8c 100644
>> --- a/drivers/pinctrl/pinctrl-at91.c
>> +++ b/drivers/pinctrl/pinctrl-at91.c
>> @@ -1215,6 +1215,7 @@ static const struct of_device_id at91_pinctrl_of_match[] = {
>> { .compatible = "atmel,sama5d3-pinctrl", .data = &sama5d3_ops },
>> { .compatible = "atmel,at91sam9x5-pinctrl", .data = &at91sam9x5_ops },
>> { .compatible = "atmel,at91rm9200-pinctrl", .data = &at91rm9200_ops },
>> + { .compatible = "microchip,sam9x60-pictrl", .data = &sam9x60_ops },
>
> Typo s/microchip,sam9x60-pictrl/microchip,sam9x60-pinctrl
Thank you, Ludovic! I'll send a v2.
>
>> { /* sentinel */ }
>> };
>>
>> @@ -1757,6 +1758,7 @@ static const struct gpio_chip at91_gpio_template = {
>> static const struct of_device_id at91_gpio_of_match[] = {
>> { .compatible = "atmel,at91sam9x5-gpio", .data = &at91sam9x5_ops, },
>> { .compatible = "atmel,at91rm9200-gpio", .data = &at91rm9200_ops },
>> + { .compatible = "microchip,sam9x60-gpio", .data = &sam9x60_ops },
>> { /* sentinel */ }
>> };
>>
>> --
>> 2.7.4
>>
>
next prev parent reply other threads:[~2019-01-31 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 12:29 [PATCH 0/7] add support " Claudiu.Beznea
2019-01-31 12:29 ` [PATCH 1/7] pinctrl: at91: add option to use drive strength bits Claudiu.Beznea
2019-01-31 12:29 ` [PATCH 2/7] pinctrl: at91: add drive strength support for SAM9X60 Claudiu.Beznea
2019-01-31 12:29 ` [PATCH 3/7] pinctrl: at91: add compatibles for SAM9X60 pin controller Claudiu.Beznea
2019-01-31 12:33 ` Ludovic Desroches
2019-01-31 16:16 ` Claudiu.Beznea [this message]
2019-01-31 12:29 ` [PATCH 4/7] dt-bindings: add documentation for banks Claudiu.Beznea
2019-01-31 12:29 ` [PATCH 5/7] dt-bindings: add bindings for SAM9X60 Claudiu.Beznea
2019-01-31 12:36 ` Ludovic Desroches
2019-01-31 12:29 ` [PATCH 6/7] pinctrl: at91: add slewrate support " Claudiu.Beznea
2019-01-31 12:29 ` [PATCH 7/7] dt-bindings: add documentation for slew rate Claudiu.Beznea
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=e23b96ad-b920-4caf-d774-2c5c43d7cea8@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®