devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Michal Simek <michal.simek@xilinx.com>,
	Alex Helms <alexander.helms.jy@renesas.com>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-clk@vger.kernel.org>, <linux-renesas-soc@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>
Cc: <robh+dt@kernel.org>, <sboyd@kernel.org>,
	<mturquette@baylibre.com>, <geert+renesas@glider.be>,
	<david.cater.jc@renesas.com>
Subject: Re: [PATCH v8 0/2] Renesas 8T49N241 device driver
Date: Fri, 4 Feb 2022 11:00:23 +0100	[thread overview]
Message-ID: <94993d27-948c-bf41-869f-c050a2efe0f2@xilinx.com> (raw)
In-Reply-To: <008026a5-a9a5-0d13-867d-fc99e95af09b@xilinx.com>

Hi,

On 2/4/22 10:36, Michal Simek wrote:
> Hi,
> 
> 
> On 10/21/21 23:31, Alex Helms wrote:
>> Changes in v8:
>>   * Use __ffs instead of ffs
>>   * Change from 64 bit to 32 bit division
>>   * Minor math changes to avoid possible overflow
>> Changes in v7:
>>   * Rebase on v5.15-rc6
>>   * Rename renesas24x_* functions to r8t49n24x_*
>>   * Implement determine_rate instead of round_rate
>>   * Implement prepare/unprepare
>>   * Use devm_clk_get_optional and ensure clk0, clk1, and xtal are attempted 
>> before dev_err_probe
>>   * Use ffs() in __renesas_bits_to_shift
>>   * Remove regmap read/write retry
>>   * More consistent debug logging
>>   * Resolved many C related naming and initialization issues
>> Changes in v6:
>>   * Rebase on v5.15-rc1
>>   * Ensure Rob's Reviewed-by tag is included
>> Changes in v5:
>>   * Rebase on v5.14-rc2
>>   * Move driver files from clk/renesas to clk
>> Changes in v4:
>>   * Add vendor prefix to dt binding compatible property
>>   * Remove clock-names description in dt binding
>>   * Remove redundant 'input-' prefix on clock names
>>   * Clarify the settings property in dt binding, add data type
>>   * Fix define spacing
>> Changes in v3:
>>   * Clarify settings property in device tree bindings schema is optional
>> Changes in v2:
>>   * Correct missing semicolon in 8t49n24x-core.c
>>
>> Alex Helms (2):
>>    dt-bindings: Add binding for Renesas 8T49N241
>>    clk: Add ccf driver for Renesas 8T49N241
>>
>>   .../bindings/clock/renesas,8t49n241.yaml      | 190 +++++
>>   MAINTAINERS                                   |   7 +
>>   drivers/clk/8t49n24x-core.c                   | 752 ++++++++++++++++++
>>   drivers/clk/8t49n24x-core.h                   | 242 ++++++
>>   drivers/clk/8t49n24x.c                        | 565 +++++++++++++
>>   drivers/clk/Kconfig                           |  21 +
>>   drivers/clk/Makefile                          |   2 +
>>   7 files changed, 1779 insertions(+)
>>   create mode 100644 
>> Documentation/devicetree/bindings/clock/renesas,8t49n241.yaml
>>   create mode 100644 drivers/clk/8t49n24x-core.c
>>   create mode 100644 drivers/clk/8t49n24x-core.h
>>   create mode 100644 drivers/clk/8t49n24x.c
>>
>>
>> base-commit: 519d81956ee277b4419c723adfb154603c2565ba
> 
> DT binding has been already reviewed and driver itself was sent long time ago.
> What's the problem now?
> 
> sboyd: Can you please review or pick it up?
> 
> Arnd: IIRC someone told me that if there is no activity it could go via your 
> tree too.

I saw that kernel bot reported 3 issues. I have fixed them and send v9 and 
hopefully this can go in.

Thanks,
Michal


      reply	other threads:[~2022-02-04 10:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21 21:31 [PATCH v8 0/2] Renesas 8T49N241 device driver Alex Helms
2021-10-21 21:31 ` [PATCH v8 1/2] dt-bindings: Add binding for Renesas 8T49N241 Alex Helms
2021-10-21 21:31 ` [PATCH v8 2/2] clk: Add ccf driver " Alex Helms
2021-11-03 14:57   ` Dan Carpenter
2022-02-04  9:36 ` [PATCH v8 0/2] Renesas 8T49N241 device driver Michal Simek
2022-02-04 10:00   ` Michal Simek [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=94993d27-948c-bf41-869f-c050a2efe0f2@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=alexander.helms.jy@renesas.com \
    --cc=arnd@arndb.de \
    --cc=david.cater.jc@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@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).