From: Greg KH <gregkh@linuxfoundation.org>
To: Vadim Pasternak <vadimp@mellanox.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"geert@linux-m68k.org" <geert@linux-m68k.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"kvalo@codeaurora.org" <kvalo@codeaurora.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"jiri@resnulli.us" <jiri@resnulli.us>
Subject: Re: [patch v1] x86/platform/mellanox: introduce support for Mellanox systems platform
Date: Mon, 12 Sep 2016 09:04:57 +0200 [thread overview]
Message-ID: <20160912070457.GA4590@kroah.com> (raw)
In-Reply-To: <AM5PR0501MB2097F4FF64CD69BD634B8CCEA2FF0@AM5PR0501MB2097.eurprd05.prod.outlook.com>
On Mon, Sep 12, 2016 at 06:44:03AM +0000, Vadim Pasternak wrote:
>
>
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@linuxfoundation.org]
> > Sent: Monday, September 12, 2016 9:13 AM
> > To: Vadim Pasternak <vadimp@mellanox.com>
> > Cc: tglx@linutronix.de; mingo@redhat.com; hpa@zytor.com;
> > davem@davemloft.net; geert@linux-m68k.org; akpm@linux-foundation.org;
> > kvalo@codeaurora.org; mchehab@kernel.org; linux@roeck-us.net;
> > x86@kernel.org; linux-kernel@vger.kernel.org; platform-driver-
> > x86@vger.kernel.org; jiri@resnulli.us
> > Subject: Re: [patch v1] x86/platform/mellanox: introduce support for Mellanox
> > systems platform
> >
> > On Mon, Sep 12, 2016 at 06:29:58AM +0000, vadimp@mellanox.com wrote:
> > > From: Vadim Pasternak <vadimp@mellanox.com>
> > >
> > > Enable system support for the Mellanox Technologies platform, which
> > > provides support for the next Mellanox basic systems: "msx6710",
> > > "msx6720", "msb7700", "msn2700", "msx1410", "msn2410", "msb7800",
> > > "msn2740", "msn2100" and also various number of derivative systems
> > > from the above basic types.
> >
> > What does "system support" mean?
> >
> > Why can't this just be a "normal" PCI driver, as you are just accessing a PCI
> > device and doing something with it, seems odd to claim it is a "platform" driver.
> >
>
> This driver also activates probes to create i2c platform driver and muxes.
And how does it do that? Through the PCI device?
> For ARM and PPC based systems I can activate such stuff through dts.
> To be honest I don't know what is the right way to do such things for
> x86 systems.
How is it found in a x86 system, in ACPI?
> If I will move PCI related stuff to separate driver, could you suggest
> some right location for that?
Depends on what it does.
> For example, could I have the code like in f.e. in
> arch/x86/platform/ts5500/ts5500.c as a platform initialization code?
How does it talk to the hardware for this?
thanks,
greg k-h
next prev parent reply other threads:[~2016-09-12 7:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 6:29 vadimp
2016-09-12 4:41 ` H. Peter Anvin
2016-09-12 4:52 ` Vadim Pasternak
2016-09-12 5:34 ` Guenter Roeck
2016-09-12 6:11 ` Greg KH
2016-09-12 6:12 ` Greg KH
2016-09-12 6:44 ` Vadim Pasternak
2016-09-12 7:04 ` Greg KH [this message]
2016-09-12 7:23 ` Vadim Pasternak
2016-09-12 7:40 ` Greg KH
2016-09-12 7:48 ` Vadim Pasternak
2016-09-12 8:17 ` Greg KH
2016-09-12 8:21 ` Vadim Pasternak
2016-09-12 8:34 ` Greg KH
2016-09-12 8:44 ` Vadim Pasternak
2016-09-12 9:14 ` Geert Uytterhoeven
2016-09-12 10:21 ` Greg KH
2016-09-12 10:55 ` Geert Uytterhoeven
2016-09-12 11:00 ` Ingo Molnar
2016-09-13 7:27 ` Vadim Pasternak
2016-09-13 8:12 ` Greg KH
2016-09-13 8:18 ` Vadim Pasternak
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=20160912070457.GA4590@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=hpa@zytor.com \
--cc=jiri@resnulli.us \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mchehab@kernel.org \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vadimp@mellanox.com \
--cc=x86@kernel.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
Powered by JetHome