linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: Sachin Kamat
	<sachin.kamat-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
	"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-samsung-soc
	<linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Sachin Kamat <spk.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Kukjin Kim <kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
	Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Subject: Re: [PATCH 1/1] i2c: Kconfig: Enable HSI2C for Exynos5 platform
Date: Wed, 16 Jul 2014 19:40:02 +0200	[thread overview]
Message-ID: <20140716174002.GG2759@katana> (raw)
In-Reply-To: <CAD=FV=WzPxT4okEur8C2G=FZK=zq3EsyCv9aAJwZ1PDkfoOcpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2122 bytes --]

On Wed, Jun 25, 2014 at 10:55:31AM -0700, Doug Anderson wrote:
> Sachin,
> 
> On Wed, Jun 25, 2014 at 3:02 AM, Sachin Kamat <sachin.kamat-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org> wrote:
> > All Exynos5 platforms have HSI2C controllers and are needed by
> > various IPs connected to the boards based on these SoCs. Thus
> > select this by default for Exynos5 platforms.
> >
> > Signed-off-by: Sachin Kamat <sachin.kamat-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> > Cc: Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
> > ---
> >  drivers/i2c/busses/Kconfig |    4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
> > index 9f7d5859cf65..c7918cffe790 100644
> > --- a/drivers/i2c/busses/Kconfig
> > +++ b/drivers/i2c/busses/Kconfig
> > @@ -465,9 +465,9 @@ config I2C_EG20T
> >  config I2C_EXYNOS5
> >         tristate "Exynos5 high-speed I2C driver"
> >         depends on ARCH_EXYNOS5 && OF
> > +       default y
> >         help
> > -         Say Y here to include support for high-speed I2C controller in the
> > -         Exynos5 based Samsung SoCs.
> > +         High-speed I2C controller on Exynos5 based Samsung SoCs.
> >
> >  config I2C_GPIO
> >         tristate "GPIO-based bitbanging I2C"
> > --
> > 1.7.9.5
> 
> This seems reasonable to me and I will also take the blame for
> suggesting this.  It's hard to imagine running a real exynos5 system
> without I2C.  One could argue that on an exynos5250 the high speed I2C
> controller is not mandatory (since all the ports can be muxed to use
> the old controller) but on newer exynos5 products you're expected to
> have the main PMIC on one of the i2c ports.  An exynos system without
> access to its PMIC will just sorta limp by.
> 
> ...but I've added Arnd to this thread as he expressed some
> reservations about this type of thing, so we'll see what he says.

Ping. Arnd? I have no strong opinion and would take this patch...

> 
> Reviewed-by: Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2014-07-16 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 10:02 [PATCH 1/1] i2c: Kconfig: Enable HSI2C for Exynos5 platform Sachin Kamat
     [not found] ` <1403690523-1863-1-git-send-email-sachin.kamat-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-06-25 10:20   ` Kukjin Kim
2014-06-25 17:55 ` Doug Anderson
     [not found]   ` <CAD=FV=WzPxT4okEur8C2G=FZK=zq3EsyCv9aAJwZ1PDkfoOcpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-16 17:40     ` Wolfram Sang [this message]
2014-07-25 11:36       ` Sachin Kamat
2014-08-01 16:17         ` Wolfram Sang
2014-08-04 21:21 ` 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=20140716174002.GG2759@katana \
    --to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sachin.kamat-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
    --cc=spk.linux-Re5JQEeQqe8AvxtiuMwx3w@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).