From: Stephen Boyd <sboyd@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Marek Vasut <marex@denx.de>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/4] clk: rs9: Support device specific dif bit calculation
Date: Mon, 27 Mar 2023 10:56:12 -0700 [thread overview]
Message-ID: <16dcfd98a72c8c4b6bac6e758bd10beb.sboyd@kernel.org> (raw)
In-Reply-To: <20230310075535.3476580-3-alexander.stein@ew.tq-group.com>
Quoting Alexander Stein (2023-03-09 23:55:34)
> The calculation DIFx is BIT(n) +1 is only true for 9FGV0241. With
> additional devices this is getting more complicated.
> Support a base bit for the DIF calculation, currently only devices
> with consecutive bits are supported, e.g. the 6-channel device needs
> additional logic.
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> Reviewed-by: Marek Vasut <marex@denx.de>
> ---
Applied to clk-next
next prev parent reply other threads:[~2023-03-27 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 7:55 [PATCH v3 1/4] clk: rs9: Check for vendor/device ID Alexander Stein
2023-03-10 7:55 ` [PATCH v3 2/4] dt-bindings: clk: rs9: Add 9FGV0441 Alexander Stein
2023-03-27 17:55 ` Stephen Boyd
2023-03-10 7:55 ` [PATCH v3 3/4] clk: rs9: Support device specific dif bit calculation Alexander Stein
2023-03-27 17:56 ` Stephen Boyd [this message]
2023-03-10 7:55 ` [PATCH v3 4/4] clk: rs9: Add support for 9FGV0441 Alexander Stein
2023-03-27 17:56 ` Stephen Boyd
2023-03-27 17:55 ` [PATCH v3 1/4] clk: rs9: Check for vendor/device ID 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=16dcfd98a72c8c4b6bac6e758bd10beb.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marex@denx.de \
--cc=mturquette@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.