From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Avi Fishman <avifishman70@gmail.com>
Cc: Tali Perry <tali.perry1@gmail.com>, Wolfram Sang <wsa@kernel.org>,
Alex Qiu <xqiu@google.com>, Kun Yi <kunyi@google.com>,
Benjamin Fair <benjaminfair@google.com>,
Joel Stanley <joel@jms.id.au>, Tomer Maimon <tmaimon77@gmail.com>,
Linux I2C <linux-i2c@vger.kernel.org>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] i2c: npcm7xx: Support changing bus speed using debugfs.
Date: Thu, 1 Oct 2020 20:40:46 +0300 [thread overview]
Message-ID: <20201001174046.GK3956970@smile.fi.intel.com> (raw)
In-Reply-To: <CAKKbWA4gHobXFGi5CiPnawWoMOi0GFrCbzanuOFZ+Aky6=9Mpg@mail.gmail.com>
On Thu, Oct 01, 2020 at 08:13:49PM +0300, Avi Fishman wrote:
> Hi Andy,
>
> Customers using BMC with complex i2c topology asked us to support
> changing bus frequency at run time, for example same device will
> communicate with one slave at 100Kbp/s and another with 400kbp/s and
> maybe also with smae device at different speed (for example an i2c
> mux).
> This is not only for debug.
The above design is fragile to start with. If you have connected peripheral
devices with different speed limitations and you try to access faster one the
slower ones may block and break the bus which will need recovery.
> Can DT overlay support that?
Probably. DT overlay describes the update in the device topology, including
certain device properties.
P.S. Please do not top post.
> On Thu, Oct 1, 2020 at 6:40 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> >
> > On Thu, Oct 1, 2020 at 8:34 AM Tali Perry <tali.perry1@gmail.com> wrote:
> > > On Wed, Sep 30, 2020 at 12:31 PM Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > >
> > > > On Wed, Sep 30, 2020 at 10:13:42AM +0300, Tali Perry wrote:
> > > > > Systems that can dinamically add and remove slave devices
> > > >
> > > > dynamically
> > > >
> > > > > often need to change the bus speed in runtime.
> > > >
> > > > > This patch exposes the bus frequency to the user.
> > > >
> > > > Expose the bus frequency to the user.
> > > >
> > > > > This feature can also be used for test automation.
> > > >
> > > > In general I think that DT overlays or so should be user rather than this.
> > > > If we allow to change bus speed settings for debugging purposes it might make
> > > > sense to do this on framework level for all drivers which support that (via
> > > > additional callback or so).
> > >
> > > Do you mean adding something like this:
> >
> > Nope. I meant to use DT description for that. I²C core should cope
> > with DT already.
> > I do not understand why you need special nodes for that rather than DT
> > overlay which will change the speed for you.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-10-01 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 7:13 [PATCH v1] i2c: npcm7xx: Support changing bus speed using debugfs Tali Perry
2020-09-30 9:31 ` Andy Shevchenko
2020-10-01 5:32 ` Tali Perry
2020-10-01 15:40 ` Andy Shevchenko
2020-10-01 17:13 ` Avi Fishman
2020-10-01 17:40 ` Andy Shevchenko [this message]
2020-10-01 18:27 ` Alex Qiu
2020-10-01 18:41 ` Avi Fishman
2020-10-01 18:51 ` Andy Shevchenko
2020-10-01 21:11 ` Alex Qiu
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=20201001174046.GK3956970@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=joel@jms.id.au \
--cc=kunyi@google.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=wsa@kernel.org \
--cc=xqiu@google.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