On Thursday, February 2, 2017 at 4:16:24 AM UTC-6, Drew Fustini wrote:
>
> I've created this patch which seems to have done the trick without
> messing with sysfs. It adds pm_runtime_get_sync() before read or
> write to eQEP memory mapped registers:
>
Robert - I've raised a pull request with
On Tue, Jan 31, 2017 at 5:47 AM, Drew Fustini wrote:
> On Mon, Jan 30, 2017 at 8:40 PM, Robert Nelson
> wrote:
>> Once you enable the power control, it's it acting the same as v4.4.x was?
>
> Yes, it does read position ok.
I've created this patch
Thanks Drew.
On Tue, Jan 31, 2017 at 9:08 PM, Drew Fustini wrote:
> On Tue, Jan 31, 2017 at 9:28 PM, William Hermans
> wrote:
> > Drew, do you have a complete gist on how you set this all up ? Mark Yoder
> > was interested in the wqep module a while back,
On Tue, Jan 31, 2017 at 9:28 PM, William Hermans wrote:
> Drew, do you have a complete gist on how you set this all up ? Mark Yoder
> was interested in the wqep module a while back, but I do not thnk he was
> able to figure it out completely. Also, from a personal project /
On Tue, Jan 31, 2017 at 4:47 AM, Drew Fustini wrote:
> On Mon, Jan 30, 2017 at 8:40 PM, Robert Nelson
> wrote:
> > Once you enable the power control, it's it acting the same as v4.4.x was?
>
> Yes, it does read position ok.
>
> # uname -r
>
On Mon, Jan 30, 2017 at 8:40 PM, Robert Nelson wrote:
> Once you enable the power control, it's it acting the same as v4.4.x was?
Yes, it does read position ok.
# uname -r
4.9.6-ti-r17
# cat /sys/devices/platform/ocp/48304000.epwmss/48304180.eqep/power/control
On Mon, Jan 30, 2017 at 3:40 PM, Drew Fustini wrote:
> On Mon, Jan 30, 2017 at 1:02 PM, Drew Fustini wrote:
>> Thanks for the assistance, Franklin. Here is the patch that is applied:
>>
On Mon, Jan 30, 2017 at 1:02 PM, Drew Fustini wrote:
> Thanks for the assistance, Franklin. Here is the patch that is applied:
> https://github.com/RobertCNelson/ti-linux-kernel-dev/tree/ti-linux-4.9.y/patches/drivers/ti/eqep
>
> The boot log is in this gist and also
So one thing I noticed is that the eqep node isn't adding any clocks
compared to EHRPWM and ECAP. So I would be curious if adding the
following entries to the eqep node may solve. I don't really remember
how we came up with this
clocks = <_root_clk_div>;
clock-names = "fck";
>From what I
On Mon, Jan 30, 2017 at 10:56 AM, Franklin S Cooper Jr wrote:
> So one thing I noticed is that the eqep node isn't adding any clocks
> compared to EHRPWM and ECAP. So I would be curious if adding the
> following entries to the eqep node may solve. I don't really remember
> how we
On Sun, Jan 29, 2017 at 3:13 AM, Drew Fustini wrote:
> eqep was working for me in 4.4.x but I get a segmentation fault when I
> read the sysfs position file:
> # cat /sys/devices/platform/ocp/48304000.epwmss/48304180.eqep/position
> [ 1858.108446] Unhandled fault: external
On Wed, Nov 2, 2016 at 11:23 AM,
Robert Nelson wrote:
> I've just added a forward port of the eqep driver.. One of the big
> changes, the eqep clock should be enabled/setup via the device-tree,
> instead of the driver..
>
> [ 36.292972] eqep 48300180.eqep: ver. 1.0
> [
I'd say about a month or two, to fully transition for all devices..
I've been testing v4.9.x-rcX's on a good number of boards on my test
farm. Just starting to see uptime's that mirror v4.4.x for
stability..
Regards,
On Thu, Dec 8, 2016 at 10:17 PM, Baozhu Zuo wrote:
>
On Tue, Nov 1, 2016 at 10:19 AM, Robert Nelson
wrote:
> On Tue, Nov 1, 2016 at 5:08 AM, Pantelis Antoniou
> wrote:
> > Hi Robert,
>
> . . .
>> pru: nothing yet..
> >>
> >
> > I should have something for this in the next couple of week or
Am Dienstag, 1. November 2016 18:20:02 UTC+1 schrieb RobertCNelson:
>
> On Tue, Nov 1, 2016 at 5:08 AM, Pantelis Antoniou
> wrote:
> > Hi Robert,
> > ...
> > I should have something for this in the next couple of week or so.
> >
> > Heavy rework, and I’d
On Tue, Nov 1, 2016 at 4:00 PM, Robert Nelson wrote:
> Status:
>
> 4.9.0-rc3-ti-r1:
>
> BBB - okay - HDMI video
> BBG - okay
> BBGW - broken wlan0 - bluetooth okay
> BBBW - broken wlan0 - bluetooth okay - HDMI video
> BLUE - broken wlan0 - bluetooth okay
>
>
On Tue, Nov 1, 2016 at 4:00 PM, Robert Nelson wrote:
> Status:
>
> 4.9.0-rc3-ti-r1:
>
> BBB - okay - HDMI video
> BBG - okay
> BBGW - broken wlan0 - bluetooth okay
> BBBW - broken wlan0 - bluetooth okay - HDMI video
> BLUE - broken wlan0 - bluetooth okay
>
>
Status:
4.9.0-rc3-ti-r1:
BBB - okay - HDMI video
BBG - okay
BBGW - broken wlan0 - bluetooth okay
BBBW - broken wlan0 - bluetooth okay - HDMI video
BLUE - broken wlan0 - bluetooth okay
v4.9.0-rc3-ti-r2 (staged *1)
BBGW - wlan0 works
BBBW - wlan0 works
BLUE - wlan0 works
1:
On Tue, Nov 1, 2016 at 12:19 PM, Robert Nelson wrote:
> On Tue, Nov 1, 2016 at 5:08 AM, Pantelis Antoniou
> wrote:
>> Hi Robert,
>>
>>
>>> On Oct 31, 2016, at 23:46 , Robert Nelson wrote:
>>>
>>> Hey Everyone,
>>>
On Tue, Nov 1, 2016 at 5:08 AM, Pantelis Antoniou
wrote:
> Hi Robert,
>
>
>> On Oct 31, 2016, at 23:46 , Robert Nelson wrote:
>>
>> Hey Everyone,
>>
>> Over the weekend, TI imported and tagged there first v4.9.x branch:
>>
>>
20 matches
Mail list logo