From: ludovic.desroches@microchip.com (Ludovic Desroches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] i2c: at91: slave mode support
Date: Mon, 30 Jul 2018 09:14:43 +0200 [thread overview]
Message-ID: <20180730071443.clib3swtsommj7jk@M43218.corp.atmel.com> (raw)
In-Reply-To: <20180720224141.lawanibd7v4hmbym@ninjato>
On Sat, Jul 21, 2018 at 12:41:41AM +0200, Wolfram Sang wrote:
> > [Ludovic Desroches]
> > Changes in v3:
> > - rebase (cherry-pick was enough)
>
> Thanks for the rebase. I wonder, though, I recall to had more
> complicated issues. However...
>
> > - fix checkpatch errors
> > - tests:
> > - hangs with a SAMA5D4 (master and slave on different busses) after about
> > 100 transfers. It's the firs time I do this test.
> > - some mismatches with a SAMA5D4 as slave and a SAMA5D2 as master
> > I don't know if it's a regression. I don't remember having seen this
> > behavior previously.
> > I think it's worth taking those patches even if there are some possible
> > bugs. It'll allow to get more people using it and so to consolidate the
> > slave mode support.
>
> I really want to see those patches go upstream, too. But I am also not a
> big fan of delivering the user something with known issues. Especially
> not when they affect the main feature to be added. My rationale here is
> that someone who is able to fix the issues remaining will also be able
> to pick up and apply patches.
>
> Maybe, maybe if it was to be enabled by a special
> I2C_AT91_SLAVE_EXPERIMANTEL symbol with lots of explanations. I need to
> think twice about that, though.
>
I understand your point. The experimental mentionning could be a good
trade-off. Let me know once you make up your mind.
> Speaking of Kconfig, I think this series needs to place a
>
> select I2C_SLAVE
>
> somewhere.
>
Ok I'll update it if we go further with this set of patches.
Regards
Ludovic
next prev parent reply other threads:[~2018-07-30 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 9:40 [PATCH v3 0/3] i2c: at91: slave mode support Ludovic Desroches
2018-07-16 9:40 ` [PATCH v3 1/3] i2c: at91: segregate master mode specific code from probe and init func Ludovic Desroches
2018-07-16 9:40 ` [PATCH v3 2/3] i2c: at91: split driver into core and master file Ludovic Desroches
2018-07-16 9:40 ` [PATCH v3 3/3] i2c: at91: added slave mode support Ludovic Desroches
2018-07-20 22:41 ` [PATCH v3 0/3] i2c: at91: " Wolfram Sang
2018-07-30 7:14 ` Ludovic Desroches [this message]
2018-12-11 19:28 ` Wolfram Sang
2018-12-21 16:16 ` Ludovic Desroches
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=20180730071443.clib3swtsommj7jk@M43218.corp.atmel.com \
--to=ludovic.desroches@microchip.com \
--cc=linux-arm-kernel@lists.infradead.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