[MinnowBoard] Echo to MinnowBoardMax GPIO export fails

Thu Jan 8 18:20:07 UTC 2015

Darren,

After make defconfig and merge, then diff with my changes…

I have not tried to minimize these. I looked at the ubuntu settings for /dev and made my config the same. I am sure these could be pruned to a min by someone that understand what each one does. I was just trying to get /dev/i2c support.

diff minnow-config .config
1298,1307c1298,1301
< CONFIG_DM_BUFIO=m
< CONFIG_DM_BIO_PRISON=m
< CONFIG_DM_PERSISTENT_DATA=m
< # CONFIG_DM_DEBUG_BLOCK_STACK_TRACING is not set
< CONFIG_DM_CRYPT=m
< CONFIG_DM_SNAPSHOT=m
< CONFIG_DM_THIN_PROVISIONING=m
< CONFIG_DM_CACHE=m
< CONFIG_DM_CACHE_MQ=m
< CONFIG_DM_CACHE_CLEANER=m
---
> # CONFIG_DM_CRYPT is not set
> # CONFIG_DM_SNAPSHOT is not set
> # CONFIG_DM_THIN_PROVISIONING is not set
> # CONFIG_DM_CACHE is not set
1310c1304
< CONFIG_DM_LOG_USERSPACE=m
---
> # CONFIG_DM_LOG_USERSPACE is not set
1313,1320c1307,1312
< CONFIG_DM_MULTIPATH=m
< CONFIG_DM_MULTIPATH_QL=m
< CONFIG_DM_MULTIPATH_ST=m
< CONFIG_DM_DELAY=m
< CONFIG_DM_UEVENT=y
< CONFIG_DM_FLAKEY=m
< CONFIG_DM_VERITY=m
< CONFIG_DM_SWITCH=m
---
> # CONFIG_DM_MULTIPATH is not set
> # CONFIG_DM_DELAY is not set
> # CONFIG_DM_UEVENT is not set
> # CONFIG_DM_FLAKEY is not set
> # CONFIG_DM_VERITY is not set
> # CONFIG_DM_SWITCH is not set
1899,1908c1891,1892
< CONFIG_I2C_CHARDEV=m
< CONFIG_I2C_MUX=m
< 
< #
< # Multiplexer I2C Chip support
< #
< # CONFIG_I2C_MUX_GPIO is not set
< # CONFIG_I2C_MUX_PCA9541 is not set
< # CONFIG_I2C_MUX_PCA954x is not set
< # CONFIG_I2C_MUX_PINCTRL is not set
---
> # CONFIG_I2C_CHARDEV is not set
> # CONFIG_I2C_MUX is not set
1966c1950
< CONFIG_I2C_STUB=m
---
> # CONFIG_I2C_STUB is not set
3980c3964
< CONFIG_LIBCRC32C=m
---
> # CONFIG_LIBCRC32C is not set

On Jan 8, 2015, at 10:59 AM, Darren Hart <dvhart at linux.intel.com> wrote:

> Michael, could you send me the delta to the minnowmax config fragment that
> you would like to see?
> 
> -- 
> Darren Hart
> Intel Open Source Technology Center
> 
> 
> 
> 
> On 1/8/15, 9:41 AM, "Michael Jones" <mike at proclivis.com> wrote:
> 
>> John,
>> 
>> I can send me the outputs tonight. But, my kernel is 3.18.1, merged
>> minnow board max txt file, and hand tweaked to support /dev/i2c. I did
>> not merge or start with the ubuntu config file. So any affect from ubuntu
>> is related to things outside the kernel, or outside the kernel causing
>> the kernel to behave differently. When I used an ubuntu config to build
>> 3.18.1, I had the same behavior as when not using it.
>> 
>> Mike
>> 
>> 
>> On Jan 8, 2015, at 10:37 AM, Darren Hart <dvhart at linux.intel.com> wrote:
>> 
>>> Thank you John,
>>> 
>>> So now we need to sort out if this is some configuration delta that I'm
>>> ignorant of, or if Ubuntu is being clever.
>>> 
>>> For those of you experiencing problems here, do you have anything else
>>> connected to the board? Any GPIO expanders or devices which might have
>>> GPIOs? I'm assuming not, but it's worth checking.
>>> 
>>> On an Ubuntu kernel, can someone send me the output of:
>>> 
>>> $ ls /sys/class/gpio/gpiochip*/
>>> 
>>> Or perhaps:
>>> 
>>> $ tree /sys/class/gpio
>>> 
>>> Thanks,
>>> 
>>> -- 
>>> Darren Hart
>>> Intel Open Source Technology Center
>>> 
>>> 
>>> 
>>> 
>>> On 1/7/15, 5:32 PM, "John Hawley" <john.hawley at intel.com> wrote:
>>> 
>>>> Ok I spent a little bit of time digging into this, it *LOOKS* like
>>>> Ubuntu is offset by +256 vs. stock and/or Fedora kernels.  Not 100%
>>>> sure
>>>> why yet.
>>>> 
>>>> That being said I wrote up a quick script that should discover the
>>>> right
>>>> values for everything and output it to a text console:
>>>> 
>>>> 
>>>> https://github.com/warthog9/minnow-max-extras/blob/master/lse/what_gpio_
>>>> nu
>>>> m.sh
>>>> 
>>>> and I've got a merge request in with it (I'll let Darren have a look at
>>>> it and yell at me about it before it gets merged).
>>>> 
>>>> If you are having problems, can you run that script and let me know if
>>>> the output is right for you?  In the meantime I'll try and dig into why
>>>> the offset.
>>>> 
>>>> - John 'Warthog9' Hawley
>>>> 
>>>> On 01/07/2015 06:51 AM, Michael Jones wrote:
>>>>> Martin,
>>>>> 
>>>>> Very helpful, thanks. I had to think a bit to understand the base of
>>>>> 82
>>>>> and 154.
>>>>> 
>>>>> For others:
>>>>> 
>>>>> For 8x, Code GPIO# = 338 + Linux GPIO# (Chart) - 82
>>>>> For 2x, Code GPIO# = 410 + Linux GPIO# (Chart) - 154
>>>>> 
>>>>> So for the two examples:
>>>>> 
>>>>> 338 + 84 - 82 = 340
>>>>> 
>>>>> and
>>>>> 
>>>>> 410 + 208 - 154 = 464
>>>>> 
>>>>> I¹ll give this a try later this week.
>>>>> 
>>>>> Are there any proper ways to expose the /sys paths for user mode like
>>>>> one can do for /dev/ttyN? Or do people just run their code as root?
>>>>> 
>>>>> Mike
>>>>> 
>>>>> 
>>>>> On Jan 5, 2015, at 7:29 AM, Martin Oldfield
>>>>> <elinux-mbmx-2014-11 at mjoldfield.com> wrote:
>>>>> 
>>>>>> I've also found wildly different GPIO numbers on my Minnowboard Max.
>>>>>> 
>>>>>> You can read about it at
>>>>>> http://www.mjoldfield.com/atelier/2014/12/mbmx-gpio.html.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> View this message in context:
>>>>>> 
>>>>>> http://minnowboard.57273.x6.nabble.com/MinnowBoard-Echo-to-MinnowBoard
>>>>>> Ma
>>>>>> x-GPIO-export-fails-tp903p907.html
>>>>>> Sent from the MinnowBoard mailing list archive at Nabble.com.
>>>>>> _______________________________________________
>>>>>> elinux-MinnowBoard mailing list
>>>>>> elinux-MinnowBoard at lists.elinux.org
>>>>>> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> elinux-MinnowBoard mailing list
>>>>> elinux-MinnowBoard at lists.elinux.org
>>>>> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>>>>> 
>>> 
>>> 
>>> _______________________________________________
>>> elinux-MinnowBoard mailing list
>>> elinux-MinnowBoard at lists.elinux.org
>>> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
>> 
>> 
>> _______________________________________________
>> elinux-MinnowBoard mailing list
>> elinux-MinnowBoard at lists.elinux.org
>> http://lists.elinux.org/mailman/listinfo/elinux-minnowboard
> 
> 