From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Wed, 23 May 2018 10:11:17 +0200
Subject: searching for a missing driver
In-Reply-To: <17499481527058909@web27g.yandex.ru>
References: <20180523022551.GA2481@hle-laptop.local>
 <20180523060521.GA15885@kroah.com>
 <6501821527056791@web16o.yandex.ru>
 <20180523064824.GA28954@kroah.com>
 <17499481527058909@web27g.yandex.ru>
Message-ID: <20180523081117.GA7247@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Wed, May 23, 2018 at 10:01:49AM +0300, Ozgur Kara wrote:
> 
> 
> 23.05.2018, 09:48, "Greg KH" <greg@kroah.com>:
> > On Wed, May 23, 2018 at 09:26:31AM +0300, Ozgur Kara wrote:
> >> ?I think seen the drivers/staging section in the kernel source.
> >
> > Yes, starting out with drivers/staging/*/TODO is always a good idea.
> >
> >> ?for example, some new generation embedded modules and electronic devices don't work on Linux.
> >
> > Really? Like what?
> 
> For example kernel's no have drivers for some sensors, I also couldn't identify the PCI card for automation and no driver in the kernel.
> 
> CP-168U RS232 PCI Card

Odss are, this "just works" if it is a normal serial port card.  If not,
it should be trivial to get working.

> Wireless Nozzle Reader MTI125
> NXP MPU6050
> MPU6050
> 
> I hope I'm not wrong :)

We have loads of iio drivers in the kernel, try digging based on the PCI
id values.  For example, look at drivers/iio/imu/inv_mpu6050/ :)

But yes, sensors are a great way to get involved in driver writing, they
are usually pretty simple and all they need are to be hooked up to the
iio interface.  A data sheet is usually needed to determine the units
and values the sensors provide, but those should not be hard to come by.

good luck!

greg k-h