On 02/08/2013 03:07 AM, Samuel Ortiz wrote:
> On Fri, Feb 08, 2013 at 02:36:16AM -0800, Darren Hart wrote:
>> On 02/08/2013 12:49 AM, Samuel Ortiz wrote:
Well, this happens when the driver in question gets removed by another
driver.
>>> removed by another driver ? I'm not sure I
On Fri, Feb 08, 2013 at 02:36:16AM -0800, Darren Hart wrote:
> On 02/08/2013 12:49 AM, Samuel Ortiz wrote:
> >> Well, this happens when the driver in question gets removed by another
> >> driver.
> > removed by another driver ? I'm not sure I understand what that means.
>
> In my case, the
On 02/08/2013 12:49 AM, Samuel Ortiz wrote:
> Hi Darren,
>
> On Thu, Feb 07, 2013 at 11:08:03PM -0800, Darren Hart wrote:
>> On 02/07/2013 08:40 PM, Darren Hart wrote:
>>>
>>>
>>> On 02/07/2013 02:09 AM, Linus Walleij wrote:
On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart wrote:
> Is
Hi Darren,
On Thu, Feb 07, 2013 at 11:08:03PM -0800, Darren Hart wrote:
> On 02/07/2013 08:40 PM, Darren Hart wrote:
> >
> >
> > On 02/07/2013 02:09 AM, Linus Walleij wrote:
> >> On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart wrote:
> >>
> >>> Is it that some other driver has claimed these GPIO
Hi Darren,
On Thu, Feb 07, 2013 at 11:08:03PM -0800, Darren Hart wrote:
On 02/07/2013 08:40 PM, Darren Hart wrote:
On 02/07/2013 02:09 AM, Linus Walleij wrote:
On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart dvh...@linux.intel.com wrote:
Is it that some other driver has claimed these
On 02/08/2013 12:49 AM, Samuel Ortiz wrote:
Hi Darren,
On Thu, Feb 07, 2013 at 11:08:03PM -0800, Darren Hart wrote:
On 02/07/2013 08:40 PM, Darren Hart wrote:
On 02/07/2013 02:09 AM, Linus Walleij wrote:
On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart dvh...@linux.intel.com wrote:
Is it
On Fri, Feb 08, 2013 at 02:36:16AM -0800, Darren Hart wrote:
On 02/08/2013 12:49 AM, Samuel Ortiz wrote:
Well, this happens when the driver in question gets removed by another
driver.
removed by another driver ? I'm not sure I understand what that means.
In my case, the gpio-sch probe
On 02/08/2013 03:07 AM, Samuel Ortiz wrote:
On Fri, Feb 08, 2013 at 02:36:16AM -0800, Darren Hart wrote:
On 02/08/2013 12:49 AM, Samuel Ortiz wrote:
Well, this happens when the driver in question gets removed by another
driver.
removed by another driver ? I'm not sure I understand what that
On 02/07/2013 08:40 PM, Darren Hart wrote:
>
>
> On 02/07/2013 02:09 AM, Linus Walleij wrote:
>> On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart wrote:
>>
>>> Is it that some other driver has claimed these GPIO lines? If so, how do
>>> I determine which one?
>>
>> Yes I think that could be it, the
On 02/07/2013 02:09 AM, Linus Walleij wrote:
> On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart wrote:
>
>> Is it that some other driver has claimed these GPIO lines? If so, how do
>> I determine which one?
>
> Yes I think that could be it, the driver would need to call
> gpio_export() for it to
On 02/07/2013 02:09 AM, Linus Walleij wrote:
> On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart wrote:
>
>> Is it that some other driver has claimed these GPIO lines? If so, how do
>> I determine which one?
>
> Yes I think that could be it, the driver would need to call
> gpio_export() for it to
On 02/07/2013 02:09 AM, Linus Walleij wrote:
> On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart wrote:
>
>> Is it that some other driver has claimed these GPIO lines? If so, how do
>> I determine which one?
>
> Yes I think that could be it, the driver would need to call
> gpio_export() for it to
On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart wrote:
> Is it that some other driver has claimed these GPIO lines? If so, how do
> I determine which one?
Yes I think that could be it, the driver would need to call
gpio_export() for it to also be accessible in sysfs.
Configure in debugfs and check
On 02/07/2013 02:09 AM, Linus Walleij wrote:
On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart dvh...@linux.intel.com wrote:
Is it that some other driver has claimed these GPIO lines? If so, how do
I determine which one?
Yes I think that could be it, the driver would need to call
On 02/07/2013 02:09 AM, Linus Walleij wrote:
On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart dvh...@linux.intel.com wrote:
Is it that some other driver has claimed these GPIO lines? If so, how do
I determine which one?
Yes I think that could be it, the driver would need to call
On 02/07/2013 08:40 PM, Darren Hart wrote:
On 02/07/2013 02:09 AM, Linus Walleij wrote:
On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart dvh...@linux.intel.com wrote:
Is it that some other driver has claimed these GPIO lines? If so, how do
I determine which one?
Yes I think that could be it,
On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart dvh...@linux.intel.com wrote:
Is it that some other driver has claimed these GPIO lines? If so, how do
I determine which one?
Yes I think that could be it, the driver would need to call
gpio_export() for it to also be accessible in sysfs.
Configure
On 02/07/2013 02:09 AM, Linus Walleij wrote:
On Thu, Feb 7, 2013 at 1:58 AM, Darren Hart dvh...@linux.intel.com wrote:
Is it that some other driver has claimed these GPIO lines? If so, how do
I determine which one?
Yes I think that could be it, the driver would need to call
I'm working with a TunnelCreek + EG20T platform which has two GPIO drivers:
gpio-sch - for the CPU GPIO lines
gpio-pch - for the EG20T GPIO lines
I can see the PCH GPIO lines in /sys/class/gpio, but not the CPU lines:
# dmesg | grep -i gpio
pch_gpio :03:00.2: enabling device ( -> 0002)
I'm working with a TunnelCreek + EG20T platform which has two GPIO drivers:
gpio-sch - for the CPU GPIO lines
gpio-pch - for the EG20T GPIO lines
I can see the PCH GPIO lines in /sys/class/gpio, but not the CPU lines:
# dmesg | grep -i gpio
pch_gpio :03:00.2: enabling device ( - 0002)
20 matches
Mail list logo
