From: <Claudiu.Beznea@microchip.com>
To: <michael@walle.cc>
Cc: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] ARM: dts: lan966x: add clock gating register
Date: Wed, 20 Jul 2022 06:52:04 +0000 [thread overview]
Message-ID: <3bca9670-4aeb-9171-6ac5-5c0508448840@microchip.com> (raw)
In-Reply-To: <9a3a5d9633cd8397f98cf2c4056e9864@walle.cc>
On 19.07.2022 16:24, Michael Walle wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> Hi Claudiu,
>
> Am 2022-07-12 09:22, schrieb Claudiu.Beznea@microchip.com:
>> On 11.07.2022 10:15, Claudiu Beznea - M18063 wrote:
>>> On 07.07.2022 16:24, Michael Walle wrote:
>>>> EXTERNAL EMAIL: Do not click links or open attachments unless you
>>>> know the content is safe
>>>>
>>>> The clock controller supports an optional clock gating register. This
>>>> is
>>>> necessary to expose the USB device clock, for example. Add it.
>>>>
>>>> Signed-off-by: Michael Walle <michael@walle.cc>
>>>
>>> Applied to at91-dt, thanks!
>>
>> Actually, I will postpone this until [1] is accepted as current driver
>> may
>> fail if this patch is applied.
>
> Which was picked today :)
Yes. It's on at91-dt again, thanks!
>
> -michael
prev parent reply other threads:[~2022-07-20 6:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 13:24 Michael Walle
2022-07-07 13:25 ` [PATCH v2 2/2] ARM: dts: kswitch-d10: enable the USB device port Michael Walle
2022-07-11 7:15 ` Claudiu.Beznea
2022-07-11 7:15 ` [PATCH v2 1/2] ARM: dts: lan966x: add clock gating register Claudiu.Beznea
2022-07-12 7:22 ` Claudiu.Beznea
2022-07-19 13:24 ` Michael Walle
2022-07-20 6:52 ` Claudiu.Beznea [this message]
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=3bca9670-4aeb-9171-6ac5-5c0508448840@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--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®