Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / Atom feed
From: Michael Trensch <MTrensch@hilscher.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Ladislav Michl <ladis@linux-mips.org>
Cc: Olof Johansson <olof@lixom.net>,
	Robert Schwebel <r.schwebel@pengutronix.de>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: Re: Hilscher NetX mach-netx refactorings
Date: Mon, 14 Jan 2019 12:26:28 +0100
Message-ID: <b5e70ac4-4cf8-9abe-ec30-7d225089caf0@hilscher.com> (raw)
In-Reply-To: <CACRpkdZ7KSmgTYP8a_RUJAWKzuc652OZ420Lq4ZnzkCuESLZ2Q@mail.gmail.com>

Hi all,

I am working for Hilscher and responsible with my group for linux
running on our new SoCs (netX4000 currently), due to a corporate
guideline all public mail addresses for github projects is set to
github@hilscher.com to distribute them to the proper department.

Maybe I can shed some light into this matter.

On 13.01.2019 13:14, 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:
>>
>> 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

This work is not combatible with the mainlined netx platform, which is
netX100/500, but for a new netX SoC, called netX 4000. Currently we have
not had any plans or schedule to get it mainline yet, as we needed to
get it finished first. That does not mean we don't want it to become
mainline. This surely depends on the number of requests that arise for
this specific SoC.

More information on the netX 4000 SoC itself can be found here:
https://www.hilscher.com/products/product-groups/network-controller/asics/netx-4000/

When trying to bring it mainline, I see, at the current point, some more
work arising, as we needed to patch some mainline sources due to some
chip specialties like:
  * nbpfaxi: static-wired-dma-channels ->
https://github.com/Hilscher/netx4000-linux/commit/a3fb58c531caf0da1d8eba90171bc4a8ce2d1da3.
I don't know if such a patch is legit or if it should be more universal
  * nand specialities from a pl353 driver starting at ->
https://github.com/Hilscher/netx4000-linux/commit/f7da2b259b71439a0c6662af8697292fe2c3afda
  *  Device-tree files are currently hosted in yocto recipes
(https://github.com/Hilscher/meta-hilscher-netx4000/tree/master/files/dts)
to prevent maintenance / syncing issues on our side
  * CAN driver which is taken / ported from rza1_can ->
https://github.com/Hilscher/netx4000-linux/commit/46ca8736f44bf8000ac41717efb77f188db1f68e
https://github.com/Hilscher/netx4000-linux/commit/f08e62e0c114b5e8037e44979317f6e777671140
  * Framebuffer display driver ->
https://github.com/Hilscher/netx4000-linux/commit/ceee73345214504bf8e7c2a9124519e55e2b2b79

> 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 wonder if anyone has contacts into the company so we can
>> work together with them to include them into mainline Linux.
>
> They have a mail address github@hilscher.com, let's knock
> on the door and see if somebody answers it :D
>
It indeed is hacky, and derived from a patch found on the mailing list /
patchwork to get it quickly working for one of our customers, who is not
using any delays at all.
As already stated somewhere, the problem indeed is the missing modem
control signals, due to pin count limitations and lack of more pin
function multiplexers, on some uarts on this chip. That's why they need
to be emulated via GPIOs. More or less, when it comes to delays the
PL011s modem control line would need to be set manually as well.

> 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.
>

The netX4000 platform is only built using a device tree. The device tree
files were sometime ago moved out of the kernel into our yocto layer to
reduce maintenance and have a single location. I know this conflicts
with mainlining.
I don't know what needs additionally to be done for working
multiplatform support.

Mit freundlichen Grüßen / Best regards

Michael Trensch
--
Michael Trensch | netX System
Phone: +49 (0) 6190 9907-0 | Fax: +49 (0) 6190 9907-50

Hilscher Gesellschaft für Systemautomation mbH   |  Rheinstrasse 15  |  65795 Hattersheim  |  Germany  |  www.hilscher.com<http://www.hilscher.com>
Sitz der Gesellschaft / place of business: Hattersheim  |  Geschäftsführer / managing director: Dipl.-Ing. Hans-Jürgen Hilscher
Handelsregister / commercial register: Frankfurt B 26873  |  Ust. Idnr. / VAT No.: DE113852715
Registergericht / register court: Amtsgericht Frankfurt/Main

Important Information:
This e-mail message including its attachments contains confidential and legally protected information solely intended for the addressee. If you are not the intended addressee of this message, please contact the addresser immediately and delete this message including its attachments. The unauthorized dissemination, copying and change of this e-mail are strictly forbidden. The addresser shall not be liable for the content of such changed e-mails.

Wichtiger Hinweis:
Diese E-Mail einschließlich ihrer Anhänge enthält vertrauliche und rechtlich geschützte Informationen, die nur für den Adressaten bestimmt sind. Sollten Sie nicht der bezeichnete Adressat sein, so teilen Sie dies bitte dem Absender umgehend mit und löschen Sie diese Nachricht und ihre Anhänge. Die unbefugte Weitergabe, das Anfertigen von Kopien und jede Veränderung der E-Mail ist untersagt. Der Absender haftet nicht für Inhalte von veränderten E-Mails.

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

  parent 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
2019-01-13 22:39       ` Linus Walleij
2019-01-14 11:26     ` Michael Trensch [this message]
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=b5e70ac4-4cf8-9abe-ec30-7d225089caf0@hilscher.com \
    --to=mtrensch@hilscher.com \
    --cc=arnd@arndb.de \
    --cc=kernel@pengutronix.de \
    --cc=ladis@linux-mips.org \
    --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