[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190504075502.GA11133@kroah.com>
Date: Sat, 4 May 2019 09:55:02 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Dragan Cvetic <draganc@...inx.com>
Cc: "arnd@...db.de" <arnd@...db.de>, Michal Simek <michals@...inx.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Derek Kiernan <dkiernan@...inx.com>
Subject: Re: [PATCH V3 02/12] misc: xilinx-sdfec: add core driver
On Fri, May 03, 2019 at 04:41:21PM +0000, Dragan Cvetic wrote:
> Hi Greg,
>
> Please find my inline comments below,
>
> Regards
> Dragan
>
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@...uxfoundation.org]
> > Sent: Thursday 2 May 2019 18:20
> > To: Dragan Cvetic <draganc@...inx.com>
> > Cc: arnd@...db.de; Michal Simek <michals@...inx.com>; linux-arm-kernel@...ts.infradead.org; robh+dt@...nel.org;
> > mark.rutland@....com; devicetree@...r.kernel.org; linux-kernel@...r.kernel.org; Derek Kiernan <dkiernan@...inx.com>
> > Subject: Re: [PATCH V3 02/12] misc: xilinx-sdfec: add core driver
> >
> > On Sat, Apr 27, 2019 at 11:04:56PM +0100, Dragan Cvetic wrote:
> > > +#define DRIVER_NAME "xilinx_sdfec"
> > > +#define DRIVER_VERSION "0.3"
> >
> > Version means nothing with the driver in the kernel tree, please remove
> > it.
>
> Will be removed. Thank you.
>
> >
> > > +#define DRIVER_MAX_DEV BIT(MINORBITS)
> >
> > Why this number? Why limit yourself to any number?
> >
>
> There can be max 8 devices for this driver. I'll change to 8.
>
> > > +
> > > +static struct class *xsdfec_class;
> >
> > Do you really need your own class?
>
> When writing a character device driver, my goal is to create and register an instance
> of that structure associated with a struct file_operations, exposing a set of operations
> to the user-space. One of the steps to make this goal is Create a class for a devices,
> visible in /sys/class/.
Why do you need a class? Again, why not just use the misc_device api,
that seems much more relevant here and will make the code a lot simpler.
thanks,
greg k-h
Powered by blists - more mailing lists