All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <amsfield22@gmail.com>
To: Varsha Rao <rvarsha016@gmail.com>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] Re: Trouble with IIO dummy build.
Date: Tue, 14 Mar 2017 19:54:14 -0700	[thread overview]
Message-ID: <20170315025412.GA5522@d830.WORKGROUP> (raw)
In-Reply-To: <e64c8df1-dce6-42e3-b186-1c85380a2734@googlegroups.com>

On Tue, Mar 14, 2017 at 07:07:54PM -0700, Varsha Rao wrote:
> Hello,
> 
> I am again having issues with dummy modules compilation. I am unable to 
> create sub directory after mounting.
> 
>  $ sudo mount -t configfs none /config
>  $ sudo mkdir /config/iio/devices/dummy/my_dummy_device
>   mkdir: cannot create directory 
> ‘/config/iio/devices/dummy/my_dummy_device’: Invalid argument
>  
>  I have the following permissions set for the file.
> 
>  drwxr-xr-x.  3 root root    0 Mar 15 07:06 .
>  dr-xr-xr-x. 19 root root 4096 Mar 14 23:55 ..
>  drwxr-xr-x.  3 root root    0 Mar 15 07:06 iio
> 
>  I can create sub directory if the directory is not mounted.
>  I  also have iio files created in  /sys/kernel/config, even though I have 
> not mounted it.  
>  $ ls -al /sys/kernel/config/
>   total 0
>  drwxr-xr-x.  3 root root 0 Mar 15 07:06 .
>  drwxr-xr-x. 11 root root 0 Mar 15 06:28 ..
>  drwxr-xr-x.  3 root root 0 Mar 15 07:06 iio
>  
>  As earlier these commands worked, don't know if this is causing the 
> problem.
>  I tried to mkdir in /config after unmounting  /sys/kernel/config, it did 
> not work.
>  $ cat /etc/mtab | grep "config"
>  configfs /sys/kernel/config configfs rw,relatime 0 0
>  none /config configfs rw,relatime 0 0
>  
>  I am able to run the following commands successfully.
>   sudo modprobe iio_dummy_evgen
>   sudo modprobe iio_dummy
>   sudo mount -t configfs none /config
>   ls -l /sys/bus/iio/devices/iio_evgen/
> 
>  I am using fedora 25 x86_64 with kernel version 4.11.0-rc1+.

Varsha, 

Do you still have the patch applied?
per Daniel's previous email:

 http://marc.info/?l=linux-iio&m=148907643001389&w=2
 if you use CONFIG_IIO_SW_DEVICE=m

 You can workaround the patch above if you select
 CONFIG_IIO_SW_DEVICE=y


alisons

>  
>  $ cat .config | grep IIO
> # CONFIG_SENSORS_IIO_HWMON is not set
> CONFIG_DVB_USB_FRIIO=m
> # IIO staging drivers
> CONFIG_IIO=m
> CONFIG_IIO_BUFFER=y
> CONFIG_IIO_BUFFER_CB=m
> CONFIG_IIO_KFIFO_BUF=m
> CONFIG_IIO_TRIGGERED_BUFFER=m
> CONFIG_IIO_CONFIGFS=m
> CONFIG_IIO_TRIGGER=y
> CONFIG_IIO_CONSUMERS_PER_TRIGGER=2
> CONFIG_IIO_SW_DEVICE=m
> CONFIG_IIO_SW_TRIGGER=m
> CONFIG_IIO_ST_ACCEL_3AXIS=m
> CONFIG_IIO_ST_ACCEL_I2C_3AXIS=m
> CONFIG_IIO_ST_ACCEL_SPI_3AXIS=m
> # Hid Sensor IIO Common
> CONFIG_HID_SENSOR_IIO_COMMON=m
> CONFIG_HID_SENSOR_IIO_TRIGGER=m
> # CONFIG_IIO_SSP_SENSORHUB is not set
> CONFIG_IIO_ST_SENSORS_I2C=m
> CONFIG_IIO_ST_SENSORS_SPI=m
> CONFIG_IIO_ST_SENSORS_CORE=m
> # IIO dummy driver
> CONFIG_IIO_DUMMY_EVGEN=m
> CONFIG_IIO_SIMPLE_DUMMY=m
> CONFIG_IIO_SIMPLE_DUMMY_EVENTS=y
> CONFIG_IIO_SIMPLE_DUMMY_BUFFER=y
> CONFIG_IIO_ST_GYRO_3AXIS=m
> CONFIG_IIO_ST_GYRO_I2C_3AXIS=m
> CONFIG_IIO_ST_GYRO_SPI_3AXIS=m
> # CONFIG_IIO_ST_LSM6DSX is not set
> CONFIG_IIO_ADIS_LIB=m
> CONFIG_IIO_ADIS_LIB_BUFFER=y
> CONFIG_IIO_ST_MAGN_3AXIS=m
> CONFIG_IIO_ST_MAGN_I2C_3AXIS=m
> CONFIG_IIO_ST_MAGN_SPI_3AXIS=m
> # CONFIG_IIO_HRTIMER_TRIGGER is not set
> CONFIG_IIO_INTERRUPT_TRIGGER=m
> CONFIG_IIO_TIGHTLOOP_TRIGGER=m
> # CONFIG_IIO_SYSFS_TRIGGER is not set
> # CONFIG_IIO_ST_PRESS is not set
> 
>  Any ideas?
>  
>  Thanks,
>  Varsha
> 
> -- 
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/e64c8df1-dce6-42e3-b186-1c85380a2734%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



  reply	other threads:[~2017-03-15  2:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-11 14:26 Trouble with IIO dummy build Varsha Rao
2017-03-11 15:19 ` Narcisa Vasile
2017-03-11 16:36   ` Varsha Rao
2017-03-11 17:53 ` [Outreachy kernel] " Daniel Baluta
2017-03-12  9:28   ` Varsha Rao
2017-03-15  2:07 ` Varsha Rao
2017-03-15  2:54   ` Alison Schofield [this message]
2017-03-15  8:44     ` [Outreachy kernel] " Varsha Rao
2017-03-15 11:57   ` Daniel Baluta
2017-03-15 14:58     ` Varsha Rao
2017-03-15 15:04       ` Daniel Baluta
2017-03-15 15:44         ` Varsha Rao
2017-03-15 15:54           ` Daniel Baluta
2017-03-15 16:31             ` Varsha Rao
2017-03-15 22:00               ` Ioana Ciornei
2017-03-16  2:16                 ` Varsha Rao

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=20170315025412.GA5522@d830.WORKGROUP \
    --to=amsfield22@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=rvarsha016@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.