From: Stephen Boyd <sboyd@kernel.org>
To: Tomer Maimon <tmaimon77@gmail.com>,
benjaminfair@google.com, joel@jms.id.au,
krzysztof.kozlowski+dt@linaro.org, mturquette@baylibre.com,
p.zabel@pengutronix.de, robh+dt@kernel.org,
tali.perry1@gmail.com, venture@google.com, yuenn@google.com
Cc: openbmc@lists.ozlabs.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Tomer Maimon <tmaimon77@gmail.com>
Subject: Re: [PATCH v28 2/3] reset: npcm: register npcm8xx clock auxiliary bus device
Date: Thu, 17 Oct 2024 15:23:01 -0700 [thread overview]
Message-ID: <f85d4a18a18859e15989732caff2144f.sboyd@kernel.org> (raw)
In-Reply-To: <20240912191038.981105-3-tmaimon77@gmail.com>
Quoting Tomer Maimon (2024-09-12 12:10:37)
> Add NPCM8xx clock controller auxiliary bus device registration.
>
> The NPCM8xx clock controller is registered as an aux device because the
> reset and the clock controller share the same register region.
>
> Signed-off-by: Tomer Maimon <tmaimon77@gmail.com>
> Tested-by: Benjamin Fair <benjaminfair@google.com>
> Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
> ---
Applied to clk-next
next prev parent reply other threads:[~2024-10-17 22:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 19:10 [PATCH v28 0/3] Introduce Nuvoton Arbel NPCM8XX BMC SoC Tomer Maimon
2024-09-12 19:10 ` [PATCH v28 1/3] dt-bindings: reset: npcm: add clock properties Tomer Maimon
2024-10-17 22:22 ` Stephen Boyd
2024-09-12 19:10 ` [PATCH v28 2/3] reset: npcm: register npcm8xx clock auxiliary bus device Tomer Maimon
2024-10-17 22:23 ` Stephen Boyd [this message]
2025-03-16 15:22 ` Guenter Roeck
2025-03-17 10:39 ` Tomer Maimon
2025-03-17 14:09 ` Guenter Roeck
2025-03-18 6:33 ` Tomer Maimon
2024-09-12 19:10 ` [PATCH v28 3/3] clk: npcm8xx: add clock controller Tomer Maimon
2024-10-17 22:23 ` Stephen Boyd
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=f85d4a18a18859e15989732caff2144f.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=benjaminfair@google.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=openbmc@lists.ozlabs.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.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).