linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Niyas Sait <niyas.sait@huawei.com>
To: Jonathan Cameron <jonathan.cameron@huawei.com>,
	Shimrra Shai <shimmyshai00@gmail.com>
Cc: "heiko@sntech.de" <heiko@sntech.de>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-rockchip@lists.infradead.org"
	<linux-rockchip@lists.infradead.org>,
	"max.schwarz@online.de" <max.schwarz@online.de>
Subject: RE: [PATCH 0/0] (proposed?) Add ACPI binding to Rockchip RK3xxx I2C bus
Date: Mon, 25 Mar 2024 20:11:01 +0000	[thread overview]
Message-ID: <78763d69bae04204b2af37201b09f8b5@huawei.com> (raw)
In-Reply-To: <20240325154150.00003bde@Huawei.com>

> Niyas, could you forward what you had to Shimrra? (I can find it if you don't have it any more).

I am on holiday so only had a chance to skim through the email. By the way, the half-baked patch is here [1]. 

The patch only supports fixed clock sources and require further changes to support multiple clock sources.

I will have a look at the discussions when I am back. Hopefully the patch gives some idea. Feel free to take up the patch and fill any missing bits.

[1] https://github.com/niyas-sait/linux-acpi/blob/main/0001-acpi-add-clock-bindings-for-fixed-clock-resources.patch

Thanks
Niyas


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-03-25 20:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 17:34 [PATCH 0/0] (proposed?) Add ACPI binding to Rockchip RK3xxx I2C bus Shimrra Shai
2024-03-22 10:35 ` Jonathan Cameron
2024-03-22 15:51   ` Shimrra Shai
2024-03-25 15:41     ` Jonathan Cameron
2024-03-25 20:11       ` Niyas Sait [this message]
2024-03-25  0:26   ` Shimrra Shai
2024-03-29 23:25   ` Shimrra Shai

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=78763d69bae04204b2af37201b09f8b5@huawei.com \
    --to=niyas.sait@huawei.com \
    --cc=heiko@sntech.de \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=max.schwarz@online.de \
    --cc=shimmyshai00@gmail.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).