From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Ezequiel Garcia
<ezequiel-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org>
Cc: Walter Lozano
<walter-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org>,
mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
Romain.Baeriswyl-ux6zf3SgZrrQT0dZR+AlfA@public.gmane.org,
atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org,
raymond.tan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
carlpeng008-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC] i2c: designware: Avoid initcall and initialize the driver like a regular one
Date: Tue, 23 Dec 2014 16:26:21 +0100 [thread overview]
Message-ID: <20141223152621.GA3692@katana> (raw)
In-Reply-To: <549982BE.3080500-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2319 bytes --]
> >> This guarantees it will probe after GPIOs drivers.
BTW this is not true to the best of my knowledge. It will make that
"very likely" but not "guarantee" anything. So, the race window is
smaller but it is still there. You need a proper fix anyhow.
> >> Platforms based on devicetree won't be affected by this change.
> >
> > Huh, why is that?
> >
>
> Unless I'm missing something here, our beloved DeviceTree guarantees to
> model the dependency between I2C slaves devices and the I2C master their
> connected to.
Frankly, you are missing quite some things here. The I2C core registers
the clients when a master gets registered. No difference between
platform and DT here.
> So, a machine fully-based on DeviceTree would never attempt to use the I2C
> bus without first registering the master, right?
Neither would platform, that would be quite a bug.
> This means there won't be any early users of the I2C platform driver in this
> scenario.
There won't be with platform as well. But I think you are missing the
point. We are a *consumer* of GPIOs here. All of the above has nothing
to do with GPIO controllers being already available.
> >> Legacy platforms, relying on the I2C being available early, might need
> >> to implement proper defered mechanisms to overcome potential problems.
> >
> > NAK. We can't say "Let's cause a regression to force people to fix
> > things that used to work" IMO. You exactly pointed out the problem that using
> > subsys_initcall() creates.
> >
> > What about fixing the drivers you use to support deferred probing when
> > acquitin the irq?
> >
>
> Maybe we can fix the legacy ones instead. However, a quick look shows there
> aren't any!
>
> $ git grep i2c_designware
> drivers/i2c/busses/i2c-designware-pcidrv.c:MODULE_ALIAS("i2c_designware-pci");
> drivers/i2c/busses/i2c-designware-platdrv.c:MODULE_ALIAS("platform:i2c_designware");
> drivers/i2c/busses/i2c-designware-platdrv.c: .name = "i2c_designware",
>
> Looks like this patch is pretty harmless.
In-tree you are right. Out-of-tree, you probably aren't. I wouldn't care
about the latter if that would block a real bugfix. But since the above
patch is not the proper fix IMO, I prefer being stable here.
Regards,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-23 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 18:15 [RFC] i2c: designware: Avoid initcall and initialize the driver like a regular one Walter Lozano
[not found] ` <1419272149-28716-1-git-send-email-walter-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org>
2014-12-22 19:02 ` Wolfram Sang
2014-12-23 12:53 ` Walter Lozano
2014-12-23 14:57 ` Ezequiel Garcia
[not found] ` <549982BE.3080500-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org>
2014-12-23 15:26 ` Wolfram Sang [this message]
2014-12-23 15:32 ` Ezequiel Garcia
[not found] ` <54998B1A.9020208-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org>
2014-12-23 16:23 ` Wolfram Sang
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=20141223152621.GA3692@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=Romain.Baeriswyl-ux6zf3SgZrrQT0dZR+AlfA@public.gmane.org \
--cc=atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org \
--cc=carlpeng008-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=ezequiel-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=raymond.tan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=walter-30ULvvUtt6G51wMPkGsGjgyUoB5FGQPZ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).