From: "Krzysztof Wilczyński" <kw@linux.com>
To: Shradha Todi <shradha.t@samsung.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, mturquette@baylibre.com,
sboyd@kernel.org, jingoohan1@gmail.com, lpieralisi@kernel.org,
robh@kernel.org, bhelgaas@google.com,
krzysztof.kozlowski@linaro.org, alim.akhtar@samsung.com,
linux@armlinux.org.uk, m.szyprowski@samsung.com,
manivannan.sadhasivam@linaro.org, pankaj.dubey@samsung.com,
gost.dev@samsung.com
Subject: Re: [PATCH v6 2/2] PCI: exynos: Adapt to clk_bulk_* APIs
Date: Fri, 17 May 2024 20:25:50 +0900 [thread overview]
Message-ID: <20240517112550.GW202520@rocinante> (raw)
In-Reply-To: <20240220084046.23786-3-shradha.t@samsung.com>
Hello,
> There is no need to hardcode the clock info in the driver as driver can
> rely on the devicetree to supply the clocks required for the functioning
> of the peripheral. Get rid of the static clock info and obtain the
> platform supplied clocks. All the clocks supplied is obtained and enabled
> using the devm_clk_bulk_get_all_enable() API.
Applied to controller/exynos, thank you!
[1/1] PCI: exynos: Adapt to use bulk clock APIs
https://git.kernel.org/pci/pci/c/358e579a9da2
Krzysztof
prev parent reply other threads:[~2024-05-17 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240220084109epcas5p3dc6b95a0ed69b63e93f4aa0a6fc919fe@epcas5p3.samsung.com>
2024-02-20 8:40 ` [PATCH v6 0/2] Add helper function to get and enable all bulk clocks Shradha Todi
2024-02-20 8:40 ` [PATCH v6 1/2] clk: Provide managed helper to get and enable " Shradha Todi
2024-02-22 5:15 ` Stephen Boyd
2024-03-05 8:50 ` Dan Carpenter
2024-03-06 12:13 ` Shradha Todi
2024-03-09 0:50 ` Stephen Boyd
2024-03-15 11:34 ` Shradha Todi
2024-03-15 17:39 ` Stephen Boyd
2024-02-20 8:40 ` [PATCH v6 2/2] PCI: exynos: Adapt to clk_bulk_* APIs Shradha Todi
2024-05-17 11:25 ` Krzysztof Wilczyński [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=20240517112550.GW202520@rocinante \
--to=kw@linux.com \
--cc=alim.akhtar@samsung.com \
--cc=bhelgaas@google.com \
--cc=gost.dev@samsung.com \
--cc=jingoohan1@gmail.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lpieralisi@kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mturquette@baylibre.com \
--cc=pankaj.dubey@samsung.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=shradha.t@samsung.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