From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Daniel Drake <drake@endlessm.com>
Cc: Tomasz Figa <t.figa@samsung.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org, Kukjin Kim <kgene.kim@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>, Tomasz Figa <tomasz.figa@gmail.com>
Subject: Re: [PATCH 0/3] Deterministic UART numbering on Samsung SoCs
Date: Wed, 9 Jul 2014 14:23:33 +0100 [thread overview]
Message-ID: <20140709142333.503a9e39@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <CAD8Lp45MvDLsxehayx8uuGt3w3O0vGskiFjb1vdvtOyOv2nG2w@mail.gmail.com>
> I like the sound of going to the standard ttyS notation and only
> providing ports for ones that exist, but is this userspace-visible
ttyS is 8250 compatible UARTS.
If the Samsung is not an 8250 compatible UART then it doesn't belong as
ttyS from the kernel perspective.
How your udev handles it is up to you.
Alan
next prev parent reply other threads:[~2014-07-09 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 11:24 Tomasz Figa
2014-06-26 11:24 ` [PATCH 1/3] Documentation: devicetree: Update samsung UART bindings Tomasz Figa
2014-06-26 11:24 ` [PATCH 2/3] serial: samsung: Consider DT alias when probing ports Tomasz Figa
2014-06-26 11:24 ` [PATCH 3/3] ARM: dts: SAMSUNG: Add aliases of UART nodes Tomasz Figa
2014-06-26 11:39 ` [PATCH 0/3] Deterministic UART numbering on Samsung SoCs Russell King - ARM Linux
2014-06-26 12:02 ` Tomasz Figa
2014-07-08 8:32 ` Daniel Drake
2014-07-08 8:40 ` Tomasz Figa
2014-07-09 13:23 ` One Thousand Gnomes [this message]
2014-07-23 6:30 ` Daniel Drake
Reply instructions:
You may reply publicly 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=20140709142333.503a9e39@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=devicetree@vger.kernel.org \
--cc=drake@endlessm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=t.figa@samsung.com \
--cc=tomasz.figa@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®