Devicetree
 help / color / mirror / Atom feed
From: Brian Masney <bmasney@redhat.com>
To: "Pavel Löbl" <pavel@loebl.cz>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Add support for Si549 programmable clock
Date: Thu, 30 Jul 2026 12:59:23 -0400	[thread overview]
Message-ID: <amuC68wkwgNL6I4i@redhat.com> (raw)
In-Reply-To: <20260729115310.3490589-1-pavel@loebl.cz>

Hi Pavel,

On Wed, Jul 29, 2026 at 01:53:08PM +0200, Pavel Löbl wrote:
> This adds support for Si549 programmable oscillator. It's almost the
> same as already supported Si544, except it uses different internal
> oscillator frequency.
> 
> So new compatible strings are added, and driver data is extended
> to carry both maximum output frequency and internal xtal frequency.
> 
> Changes in v3:
>   Added missing xo_freq member description as found by kernel test robot:
> 
>   https://lore.kernel.org/oe-kbuild-all/202607291708.qFSxYL2s-lkp@intel.com/

I assumed a pull with v2 for Stephen here:

https://lore.kernel.org/linux-clk/amjbNiVjm5HkPRu9@redhat.com/

I don't know yet if he's going to pull that. In case he pulls that, can
you post a separate patch for just the xo_freq member description so
that we can merge the fix separately?

That way we'll be set either way whatever he decides to do with that
pull.

Thanks,
Brian


      parent reply	other threads:[~2026-07-30 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 11:53 [PATCH v3 0/2] Add support for Si549 programmable clock Pavel Löbl
2026-07-29 11:53 ` [PATCH v3 1/2] dt-bindings: clock: si544: add si549 compatible Pavel Löbl
2026-07-29 12:06   ` sashiko-bot
2026-07-30  6:46   ` Krzysztof Kozlowski
2026-07-29 11:53 ` [PATCH v3 2/2] clk: si544: add support for si549 Pavel Löbl
2026-07-29 12:10   ` sashiko-bot
2026-07-30 16:59 ` Brian Masney [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=amuC68wkwgNL6I4i@redhat.com \
    --to=bmasney@redhat.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=pavel@loebl.cz \
    --cc=robh@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