Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Robert Schwebel <r.schwebel@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Olof Johansson <olof@lixom.net>,
	github@hilscher.com,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: Hilscher NetX mach-netx refactorings
Date: Sun, 13 Jan 2019 16:50:47 +0100
Message-ID: <20190113155047.GA12829@lenoch> (raw)
In-Reply-To: <CACRpkdZ7KSmgTYP8a_RUJAWKzuc652OZ420Lq4ZnzkCuESLZ2Q@mail.gmail.com>

Hi Linus,

On Sun, Jan 13, 2019 at 01:14:36PM +0100, Linus Walleij wrote:
> On Sat, Jan 12, 2019 at 1:03 PM Arnd Bergmann <arnd@arndb.de> wrote:
> > On Sat, Jan 12, 2019 at 9:35 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> > >
> > > Hi Sascha, Robert,
> > >
> > > I am looking at refactoring mach-netx to use the new PL11x
> > > DRM driver for the graphics.
> > >
> > > I need to make sure that patches get tested on the hardware
> > > and just want to ascertain that there is an active maintainer that
> > > will be able to test patches I make for this and work on getting
> > > it migrated to DRM before I start spending time on it.
> > >
> > > Are you/pengutronix still actively maintaining this machine and
> > > testing new kernels on netx?
> > >
> > > I guess the second question is whether you have plans to migrate
> > > it to device tree and multiplatform, but I'm mainly thinking about
> > > my own little patches now.
> >
> >
> > On a related note, there does appear to be active work on
> > newer netx machines that were never upstreamed, see
> > https://github.com/Hilscher/netx4000-linux/commits/v4.9-netx4000-stable
> 
> That RS485 addition to PL011 using GPIOs is a bit hacky but
> looks like very useful for industrial applications.
> Ladislav, have you been in contact with Hilscher?

I guess I appeared on Cc list because of commit 797537a45450 ("amba-pl011:
Add RS485 support (ioctl and devicetree)") from above github repo which
is based on my hack originaly done for rPi3 as I got tired of all those
experts implementing 'drive enable' in userspace. That's broken by design
and works only by accident. But as I'm also considering every single
device running from SD card broken by design - it was perfect match ;-)

But seriously, it is indeed needed for industrial applications and
should be done a bit better - I mean regarding those delays in interrupt
context.

> > I wonder if anyone has contacts into the company so we can
> > work together with them to include them into mainline Linux.

I do not own this machine nor I was in contact with Hilscher, but I can
help with mainlining PL011's RS485 support. It is only matter of time
until someone brings some "product" based on RPi claiming "it almost
works, it just needs a bit of fixing" ;-) So having that in mainline
would save some future effort.

> They have a mail address github@hilscher.com, let's knock
> on the door and see if somebody answers it :D
> 
> I'd personally be able to take a stab at converting this machine
> to device tree and multiplatform if I only had access to the
> hardware, as it seems to be in the same class as EP93xx
> and MOXA ART: deployed in industrial systems as we speak.
> 
> Yours,
> Linus Walleij

Best regards,
	ladis

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply index

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-12  8:35 Linus Walleij
2019-01-12 12:03 ` Arnd Bergmann
2019-01-13 12:14   ` Linus Walleij
2019-01-13 15:50     ` Ladislav Michl [this message]
2019-01-13 22:39       ` Linus Walleij
2019-01-14 11:26     ` Michael Trensch
2019-01-14 14:22       ` Linus Walleij
2019-01-15  7:05         ` Michael Trensch
2019-01-15 10:11           ` Arnd Bergmann
2019-01-15 10:14         ` Arnd Bergmann
2019-01-14 10:35 ` Sascha Hauer

Reply instructions:

You may reply publically 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=20190113155047.GA12829@lenoch \
    --to=ladis@linux-mips.org \
    --cc=arnd@arndb.de \
    --cc=github@hilscher.com \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=r.schwebel@pengutronix.de \
    /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

Linux-ARM-Kernel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-arm-kernel/0 linux-arm-kernel/git/0.git
	git clone --mirror https://lore.kernel.org/linux-arm-kernel/1 linux-arm-kernel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-arm-kernel linux-arm-kernel/ https://lore.kernel.org/linux-arm-kernel \
		linux-arm-kernel@lists.infradead.org infradead-linux-arm-kernel@archiver.kernel.org
	public-inbox-index linux-arm-kernel


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.infradead.lists.linux-arm-kernel


AGPL code for this site: git clone https://public-inbox.org/ public-inbox