From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Kristian Beilke <beilke@posteo.de>,
Sakari Ailus <sakari.ailus@iki.fi>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Alan Cox <alan@linux.intel.com>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [BUG] atomisp_ov2680 not initializing correctly
Date: Thu, 04 Jan 2018 19:47:50 +0200 [thread overview]
Message-ID: <1515088070.7000.703.camel@linux.intel.com> (raw)
In-Reply-To: <20180102183106.79701c0f@alans-desktop>
On Tue, 2018-01-02 at 18:31 +0000, Alan Cox wrote:
> > Patch 0003-atomisp_gmin_platform-tweak-to-drive-axp288.patch gives a
> > little confusion.
> > The PMIC driver should work via ACPI OpRegion macro (and should be
> > enabled in kernel configuration). That's how it supposed to work.
> > The patch seems redundant.
>
> I am fairly sure it is meant to work that way - but it doesn't. At
> least
> not at the moment.
Hmm... At least I see writes to PMIC on my side through OpRegion driver.
(Assuming my ugly hack patches applied)
> > > I see your point, Still it feels, as if this could go somewhere.
> >
> > I hope so, though I didn't try CherryTrail and according to Alan
> > that
> > is what he had tried on.
>
> It's what we are currently trying on. I can fire up the ISP and
> actually
> get interrupts from it, but not much more at this point.
Seems you are ahead of everyone who is trying AtomISP till now.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-01-04 17:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 15:50 [BUG] atomisp_ov2680 not initializing correctly Kristian Beilke
2017-12-19 12:00 ` Sakari Ailus
2017-12-19 20:37 ` Andy Shevchenko
2017-12-20 7:13 ` Kristian Beilke
2017-12-21 12:54 ` Kristian Beilke
2017-12-21 14:23 ` Andy Shevchenko
2017-12-23 0:31 ` Kristian Beilke
2017-12-28 16:03 ` Andy Shevchenko
2017-12-29 19:38 ` Andy Shevchenko
2017-12-30 21:10 ` Alan Cox
2018-01-04 17:52 ` Andy Shevchenko
2018-01-17 13:52 ` Alan Cox
2017-12-31 15:19 ` Kristian Beilke
2018-01-01 12:42 ` Andy Shevchenko
2018-01-02 18:31 ` Alan Cox
2018-01-04 17:47 ` Andy Shevchenko [this message]
2017-12-30 20:57 ` Alan Cox
2018-01-04 17:58 ` Andy Shevchenko
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=1515088070.7000.703.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=beilke@posteo.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.