From: Pavel Machek <pavel@ucw.cz>
To: "Dr. H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Marek Belisko <marek@goldelico.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Pawel Moll <Pawel.Moll@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
NeilBrown <neilb@suse.de>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation: devicetree: Add bindings for Wi2Wi w2sg0004 gps
Date: Mon, 27 Oct 2014 10:31:26 +0100 [thread overview]
Message-ID: <20141027093126.GC9807@amd> (raw)
In-Reply-To: <FDDD1C99-81F9-4933-815A-CC686A19115E@goldelico.com>
> > I think we just disagree about implementing a version that “works” in a quite specific
> > setup (there are necessary assumptions about OMAP pinmux and omap-serial) with
> > existing APIs versus a general one that might need a lot of changes outside the driver
> > and introduce new APIs.
>
> After re-thinking what we have discussed so far (and considering other recommendations
> I have received off-list) I currently see these options/questions:
>
> * who could modify the serial drivers and APIs so that this driver can become
> a subnode (“bus client”) of an UART? How long does it take to
> become available?
I believe that is called "tty line discipline".
> * would it be an option to simply rename the driver to “w2sg0004-power”
> to make clear that it is not at all related to the UART data communication
> channel but only controlling the power of the w2sg0004 chip?
Sounds sane.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-10-27 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1413491183-15018-1-git-send-email-marek@goldelico.com>
[not found] ` <1413491183-15018-2-git-send-email-marek@goldelico.com>
[not found] ` <20141017093714.GB4202@leverpostej>
[not found] ` <D65FF64A-856F-47EC-B3DE-7F2FCE505087@goldelico.com>
[not found] ` <20141017110043.GA5335@leverpostej>
[not found] ` <27AD2801-6410-44E3-9E0C-911D73E6A457@goldelico.com>
[not found] ` <20141020093536.GA25360@leverpostej>
[not found] ` <7A9F8C73-6CBD-435A-934C-14A80FFE452F@goldelico.com>
2014-10-24 9:32 ` [PATCH 2/2] Documentation: devicetree: Add bindings for Wi2Wi w2sg0004 gps Dr. H. Nikolaus Schaller
2014-10-27 9:31 ` Pavel Machek [this message]
2014-11-02 10:15 ` Dr. H. Nikolaus Schaller
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=20141027093126.GC9807@amd \
--to=pavel@ucw.cz \
--cc=Pawel.Moll@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=hns@goldelico.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=marek@goldelico.com \
--cc=mark.rutland@arm.com \
--cc=neilb@suse.de \
--cc=robh+dt@kernel.org \
/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