From: Greg KH <gregkh@linuxfoundation.org>
To: Vadim Pasternak <vadimp@mellanox.com>
Cc: "dvhart@infradead.org" <dvhart@infradead.org>,
"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
"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>,
Michael Shych <michaelsh@mellanox.com>,
"ivecera@redhat.com" <ivecera@redhat.com>
Subject: Re: [PATCH v3 6/7] platform/mellanox: Introduce support for Mellanox register access driver
Date: Sun, 27 May 2018 17:34:45 +0200 [thread overview]
Message-ID: <20180527153445.GA11051@kroah.com> (raw)
In-Reply-To: <HE1PR0502MB375324E5F279A2733339365FA26F0@HE1PR0502MB3753.eurprd05.prod.outlook.com>
On Sun, May 27, 2018 at 03:22:06PM +0000, Vadim Pasternak wrote:
>
>
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@linuxfoundation.org]
> > Sent: Sunday, May 27, 2018 6:14 PM
> > To: Vadim Pasternak <vadimp@mellanox.com>
> > Cc: dvhart@infradead.org; andy.shevchenko@gmail.com; linux-
> > kernel@vger.kernel.org; platform-driver-x86@vger.kernel.org; jiri@resnulli.us;
> > Michael Shych <michaelsh@mellanox.com>; ivecera@redhat.com
> > Subject: Re: [PATCH v3 6/7] platform/mellanox: Introduce support for Mellanox
> > register access driver
> >
> > On Sun, May 27, 2018 at 04:47:43PM +0000, Vadim Pasternak wrote:
> > > Introduce new Mellanox platform driver to allow access to Mellanox
> > > programmable device register space trough sysfs interface.
> > > The driver purpose is to provide sysfs interface for user space for
> > > the registers essential for system control and monitoring.
> > > The sets of registers for sysfs access are supposed to be defined per
> > > system type bases and include the registers related to system resets
> > > operation, system reset causes monitoring and some kinds of mux selection.
> > >
> > > Signed-off-by: Vadim Pasternak <vadimp@mellanox.com>
> > > ---
> > > v1->v2:
> > > Changed added by Vadim:
> > > - Change ---help--- to help in Kconfig, according to new
> > > requirements;
> > > v2->v3:
> > > Comments pointed out by Darren:
> > > - Remove conditional assignment per attribute mode type, because mode
> > > will guard against not permitted access.
> > > Verified by Vadim.
> > > ---
> > > drivers/platform/mellanox/Kconfig | 11 ++
> > > drivers/platform/mellanox/Makefile | 1 +
> > > drivers/platform/mellanox/mlxreg-io.c | 203
> > > ++++++++++++++++++++++++++++++++++
> > > 3 files changed, 215 insertions(+)
> > > create mode 100644 drivers/platform/mellanox/mlxreg-io.c
> > >
> > > diff --git a/drivers/platform/mellanox/Kconfig
> > > b/drivers/platform/mellanox/Kconfig
> > > index 591bccd..ddfae9fc 100644
> > > --- a/drivers/platform/mellanox/Kconfig
> > > +++ b/drivers/platform/mellanox/Kconfig
> > > @@ -23,4 +23,15 @@ config MLXREG_HOTPLUG
> > > This driver handles hot-plug events for the power suppliers, power
> > > cables and fans on the wide range Mellanox IB and Ethernet systems.
> > >
> > > +config MLXREG_IO
> > > + tristate "Mellanox platform register access driver support"
> > > + depends on REGMAP
> > > + depends on HWMON
> > > + help
> > > + This driver allows access to Mellanox programmable device register
> > > + space trough sysfs interface. The sets of registers for sysfs access
> > > + are defined per system type bases and includes the registers related
> > > + to system resets operation, system reset causes monitoring and some
> > > + kinds of mux selection.
> >
> > No Documentation/ABI/ entries for these new sysfs files? Not good :(
> >
>
> Thanks Greg for your comment.
>
> Should I call doc file like:
> Documentation/ABI/stable/sysfs-driver-mlxreg-io
> ?
What ever matches the naming scheme for the driver, yes.
thanks,
greg k-h
next prev parent reply other threads:[~2018-05-27 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 16:47 Vadim Pasternak
2018-05-27 15:13 ` Greg KH
2018-05-27 15:22 ` Vadim Pasternak
2018-05-27 15:34 ` Greg KH [this message]
2018-06-01 16:52 ` Darren Hart
2018-06-02 6:30 ` Vadim Pasternak
2018-05-27 16:47 ` [PATCH v3 7/7] platform/x86: mlx-platform: Add mlxreg-io platform driver activation 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=20180527153445.GA11051@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=dvhart@infradead.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelsh@mellanox.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vadimp@mellanox.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