From: Wolfram Sang <wsa@the-dreams.de>
To: Annaliese McDermond <nh6z@nh6z.net>
Cc: stefan.wahren@i2se.com, f.fainelli@gmail.com,
swarren@wwwdotorg.org, team@nwdigitalradio.com,
Eric Anholt <eric@anholt.net>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2] i2c: bcm2835: Model Divider in CCF
Date: Thu, 16 May 2019 09:58:48 +0200 [thread overview]
Message-ID: <20190516075848.GA1033@kunai> (raw)
In-Reply-To: <4174B26B-4E3A-4CCA-A5ED-BE62A3B5E66A@nh6z.net>
[-- Attachment #1.1: Type: text/plain, Size: 888 bytes --]
Hi Annaliese,
On Wed, May 15, 2019 at 10:37:03PM -0700, Annaliese McDermond wrote:
> I’m just following up on this since I haven’t heard anything since I submitted the
> v2 patch a week ago. Wolfram, does this look like a sane approach? Stefan,
> were my changes in v2 acceptable?
There is a bit of overhead involved, but conceptually it looks like an
elegant solution to me. However, I am not an expert of CCF. Grepping
through kernel sources, I don't see many clocks defined outside
drivers/clk. So, I'd appreciate if we could get some ack/feedback from
one of the CCF experts/maintainers.
> I’m happy to go back to the drawing board to change things if there’s a better
> answer to the problem.
>
> Thanks for everyone’s patience with me trying to work through the proper
> process.
Thanks for working on this one!
Kind regards,
Wolfram
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-16 7:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 7:12 [PATCH v2] i2c: bcm2835: Model Divider in CCF Annaliese McDermond
2019-05-08 7:12 ` Annaliese McDermond
2019-05-16 5:37 ` Annaliese McDermond
2019-05-16 7:58 ` Wolfram Sang [this message]
2019-05-17 1:55 ` Annaliese McDermond
2019-05-27 19:15 ` Wolfram Sang
2019-05-27 20:00 ` Annaliese McDermond
2019-05-27 20:20 ` Wolfram Sang
2019-05-28 22:25 ` Eric Anholt
2019-05-16 10:59 ` Stefan Wahren
2019-05-16 10:59 ` Stefan Wahren
2019-05-28 7:52 ` Stefan Wahren
2019-05-28 7:52 ` Stefan Wahren
2019-05-29 3:01 ` Annaliese McDermond
2019-05-29 4:32 ` Annaliese McDermond
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=20190516075848.GA1033@kunai \
--to=wsa@the-dreams.de \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nh6z@nh6z.net \
--cc=stefan.wahren@i2se.com \
--cc=swarren@wwwdotorg.org \
--cc=team@nwdigitalradio.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 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.