From: <Codrin.Ciubotariu@microchip.com>
To: <Horatiu.Vultur@microchip.com>
Cc: <robh+dt@kernel.org>, <Nicolas.Ferre@microchip.com>,
<alexandre.belloni@bootlin.com>,
<Ludovic.Desroches@microchip.com>, <linux-i2c@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] i2c: at91: Add support for programmable clock source
Date: Wed, 13 Oct 2021 13:10:25 +0000 [thread overview]
Message-ID: <bdbc47b1-e98e-b2c2-61a4-86a3edecff3b@microchip.com> (raw)
In-Reply-To: <20211013114144.7j4scdaq2rjfmiwn@soft-dev3-1.localhost>
> I think actually I will drop this patch series because apparently
> lan966x works fine also with the peripheral clock. So then no changes
> are required.
>
> If you think is worth it, I can do another version with the proposed
> changes.
Probably not until we have an implemented good reason to use GCLK.
Best regards,
Codrin
next prev parent reply other threads:[~2021-10-13 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 14:07 [PATCH 0/2] i2c: at91: Add support for programmable clock source Horatiu Vultur
2021-10-12 14:07 ` [PATCH 1/2] dt-bindings: i2c: at91: Extend compatible list for lan966x Horatiu Vultur
2021-10-22 23:37 ` Rob Herring
2021-10-12 14:07 ` [PATCH 2/2] i2c: at91: add support for brsrcclk Horatiu Vultur
2021-10-13 8:49 ` [PATCH 0/2] i2c: at91: Add support for programmable clock source Codrin.Ciubotariu
2021-10-13 11:41 ` Horatiu Vultur - M31836
2021-10-13 13:10 ` Codrin.Ciubotariu [this message]
2021-11-05 21:47 ` Wolfram Sang
2021-11-08 8:35 ` Codrin.Ciubotariu
2021-11-08 9:29 ` Horatiu Vultur - M31836
2021-11-29 10:06 ` Wolfram Sang
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=bdbc47b1-e98e-b2c2-61a4-86a3edecff3b@microchip.com \
--to=codrin.ciubotariu@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).