From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Eddie James <eajames@linux.vnet.ibm.com>,
linux-i2c <linux-i2c@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Wolfram Sang <wsa@the-dreams.de>,
Rob Herring <robh+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Mark Rutland <mark.rutland@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v8 0/7] i2c: Add FSI-attached I2C master algorithm
Date: Fri, 01 Jun 2018 09:33:49 +1000 [thread overview]
Message-ID: <5683dded80ecabef532d2e285e5fc98e29f59510.camel@kernel.crashing.org> (raw)
In-Reply-To: <CAHp75Vec+KZCkjcs3qpB=qLmaTon=yTLyu7S_tDrMGcobHW5eQ@mail.gmail.com>
On Thu, 2018-05-31 at 09:29 +0300, Andy Shevchenko wrote:
> > If you have specific issues with how this is done, please express them
> > clearly. It's quite possible that there's some better way to do what
> > Eddie is doing here, but without *construtive* feedback this is
> > pointless.
>
> It feels like you duplicate approach which is done in OF generic case.
> That is my concern. Though, if Wolfram is telling that is OK, I have
> no objections.
THe OF generic case is about discovering slaves underneath a port, not
ports inside of a mulit-port master.
I am not aware of a generic mechanism for the latter. We *could* make
the ports sub-devices but it gets messy then to arbitrate the
communication and deal with the common part. I've seen (and written)
multi-port masters in the past that use a similar approach to what
Eddie's doing and it works fine.
> > I'm disappointed here because we have an example of somebody rather new
> > producing what is overall pretty damn good code,
>
> That is true. His code much better than many I have seen before
Thanks. Also thanks for taking the time to review.
> > despite a few corner
> > issues, and being (again) treated like crap.
>
> Sorry for that, life is harsh.
>
> > This isn't the right way to operate, and I believe this has been made
> > clear many times before.
>
> Yes.
Cheers,
Ben.
prev parent reply other threads:[~2018-05-31 23:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 21:07 Eddie James
2018-05-30 21:07 ` [PATCH v8 1/7] dt-bindings: i2c: Add FSI-attached I2C master dt binding documentation Eddie James
2018-05-30 21:07 ` [PATCH v8 2/7] i2c: Add FSI-attached I2C master algorithm Eddie James
2018-05-30 21:07 ` [PATCH v8 3/7] i2c: fsi: Add port structures Eddie James
2018-05-30 21:07 ` [PATCH v8 4/7] i2c: fsi: Add abort and hardware reset procedures Eddie James
2018-05-30 21:42 ` Andy Shevchenko
2018-05-30 21:07 ` [PATCH v8 5/7] i2c: fsi: Add transfer implementation Eddie James
2018-05-31 6:50 ` Andy Shevchenko
2018-05-30 21:07 ` [PATCH v8 6/7] i2c: fsi: Add I2C master locking Eddie James
2018-05-30 21:07 ` [PATCH v8 7/7] i2c: fsi: Add bus recovery Eddie James
2018-05-30 21:31 ` [PATCH v8 0/7] i2c: Add FSI-attached I2C master algorithm Andy Shevchenko
2018-05-30 22:42 ` Benjamin Herrenschmidt
2018-05-31 6:29 ` Andy Shevchenko
2018-05-31 23:33 ` Benjamin Herrenschmidt [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=5683dded80ecabef532d2e285e5fc98e29f59510.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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
all inboxes | Powered by JetHome®