[lkml]   [2017]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch v6 0/3] JTAG driver introduction
On Thu, Aug 24, 2017 at 2:07 PM, Linus Walleij <> wrote:
> On Tue, Aug 22, 2017 at 6:10 PM, Oleksandr Shamray
> <> wrote:
>> SoC which are not equipped with JTAG master interface, can be built
>> on top of JTAG core driver infrastructure, by applying bit-banging of
>> TDI, TDO, TCK and TMS pins within the hardware specific driver.
> I guess you mean it should then use GPIO lines for bit-banging?
> I was wondering about how some JTAG clients like openOCD does
> this in some cases.

Many common uses of OpenOCD leverage USB devices, such as FTDI FT232R,
that have a command queue for bitbanging operations. Managing these
via libusb is ugly but platform-agnostic.

> In my worst nightmare they export GPIO lines using
> the horrid ABI in /sys/gpio/*

While that is certainly horrible (and slow), mapping in the GPIO
registers via /dev/mem strikes me as worse:

> In best case they use the GPIO character device or even
> libgpiod.
> But having a JTAG abstraction inside the kernel that can
> grab a few lines for JTAG defined in a device tree, ACPI DSDT
> or similar makes sense too, as it abstracts the hardware so the
> JTAG client can then just open whatever /dev/jtag0 is on the machine
> and go ahead without having to bother about what GPIO lines
> are connected exactly where.
> Yours,
> Linus Walleij

 \ /
  Last update: 2017-08-24 23:37    [W:0.111 / U:33.812 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site