From: "Daniel Walker (danielwa)" <danielwa@cisco.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Shinichiro Kawasaki" <shinichiro.kawasaki@wdc.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo J�rvinen" <ilpo.jarvinen@linux.intel.com>,
"Klara Modin" <klarasmodin@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Danil Rybakov" <danilrybakov249@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xe-linux-external(mailer list)" <xe-linux-external@cisco.com>
Subject: Re: platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe
Date: Mon, 18 Nov 2024 14:35:44 +0000 [thread overview]
Message-ID: <ZztQwLpoZDZzbi6O@goliath> (raw)
In-Reply-To: <ZztF7FKaBwZKs5dk@smile.fi.intel.com>
On Mon, Nov 18, 2024 at 03:49:32PM +0200, Andy Shevchenko wrote:
> On Mon, Nov 18, 2024 at 01:32:55PM +0000, Daniel Walker (danielwa) wrote:
> > On Mon, Nov 18, 2024 at 03:24:20PM +0200, Andy Shevchenko wrote:
> > > On Mon, Nov 18, 2024 at 12:40:16PM +0000, Daniel Walker (danielwa) wrote:
>
> ...
>
> > > Are you referring to LPC GPIO?
> >
> > I don't know the hardware well enough to say for certain. It's whatever device 8086:19dd is.
>
> This is device which represents p2sb. It's not a GPIO device you are talking
> about for sure. You can send privately more detailed info in case this is shouldn't
> be on public to me to understand what would be the best approach to fix your issue.
Here's a comment,
/* INTEL Denverton GPIO registers are accessible using SBREG_BAR(bar 0) as base */
We have gpio wired to an FPGA and I believe the gpio line is used to reset the
fpga.
So the pci resources attached to 8086:19dd can be used to access gpio of some
type.
I'm not a pci expert but on the 19bb device bar 0 we use the below offset to manipulate
the gpio,
#define INTEL_GPIO_REG_RESET_OFFSET 0xC50578
The comments suggest this is gpio 6. I would seems your reaction would be that
there is no gpio on the 19dd device. Maybe our driver is access gpio thru p2sb
or something like that.
Does the offset above make sense to you in the context of the p2sb ?
Daniel
next prev parent reply other threads:[~2024-11-18 14:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 15:42 Daniel Walker (danielwa)
2024-11-13 16:24 ` Hans de Goede
2024-11-13 16:33 ` Hans de Goede
2024-11-13 16:38 ` Hans de Goede
2024-11-13 17:19 ` Daniel Walker (danielwa)
2024-11-13 17:04 ` Hans de Goede
2024-11-13 17:41 ` Daniel Walker (danielwa)
2024-11-13 18:34 ` Hans de Goede
2024-11-15 11:35 ` Shinichiro Kawasaki
2024-11-15 14:57 ` Daniel Walker (danielwa)
2024-11-18 11:30 ` Shinichiro Kawasaki
2024-11-18 11:42 ` Hans de Goede
2024-11-18 12:14 ` Andy Shevchenko
2024-11-18 12:40 ` Daniel Walker (danielwa)
2024-11-18 13:24 ` Andy Shevchenko
2024-11-18 13:29 ` Hans de Goede
2024-11-18 13:52 ` Andy Shevchenko
2024-11-18 13:32 ` Daniel Walker (danielwa)
2024-11-18 13:49 ` Andy Shevchenko
2024-11-18 14:35 ` Daniel Walker (danielwa) [this message]
2024-11-18 15:55 ` Andy Shevchenko
2024-11-18 16:00 ` Hans de Goede
2024-11-18 16:08 ` Andy Shevchenko
2024-11-18 17:15 ` Daniel Walker (danielwa)
2024-11-19 2:20 ` Shinichiro Kawasaki
2024-11-19 9:37 ` Andy Shevchenko
2024-11-20 4:03 ` Shinichiro Kawasaki
2024-11-19 18:28 ` Hans de Goede
2024-11-19 20:51 ` Daniel Walker (danielwa)
2024-11-20 7:06 ` Shinichiro Kawasaki
2024-11-19 9:41 ` Andy Shevchenko
2024-11-19 14:47 ` Daniel Walker (danielwa)
2024-11-19 15:03 ` Andy Shevchenko
2024-11-13 19:17 ` Andy Shevchenko
2024-11-16 11:34 ` Hans de Goede
2024-11-18 10:05 ` 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=ZztQwLpoZDZzbi6O@goliath \
--to=danielwa@cisco.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=danilrybakov249@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=klarasmodin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=xe-linux-external@cisco.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
Powered by JetHome