From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 1/3] serial: sh-sci: Add OF support
Date: Thu, 07 Mar 2013 05:51:58 +0000 [thread overview]
Message-ID: <201303070551.59191.arnd@arndb.de> (raw)
In-Reply-To: <20130306152857.GJ14275@linux-sh.org>
On Wednesday 06 March 2013, Paul Mundt wrote:
> Now that we have split things out in to regtype for the compat string we
> may be able to get away with selecting defaults that match the regtype
> and drop it from the binding (assuming all future parts remain relatively
> sane), but it would still complicate things if we were to ever do DT
> support for legacy CPUs. It's not enough to tie to the port type, as
> there are plenty of cases where the port type uses a non-standard algo on
> some CPU subtypes (although things are pretty consistent for the arm side
> so far).
Maybe we could document it as an optional property that we may use for the
legacy CPUs if necessary, but put it into the ARM dts files or into
the driver implementation for the time being.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/3] serial: sh-sci: Add OF support
Date: Thu, 7 Mar 2013 05:51:58 +0000 [thread overview]
Message-ID: <201303070551.59191.arnd@arndb.de> (raw)
In-Reply-To: <20130306152857.GJ14275@linux-sh.org>
On Wednesday 06 March 2013, Paul Mundt wrote:
> Now that we have split things out in to regtype for the compat string we
> may be able to get away with selecting defaults that match the regtype
> and drop it from the binding (assuming all future parts remain relatively
> sane), but it would still complicate things if we were to ever do DT
> support for legacy CPUs. It's not enough to tie to the port type, as
> there are plenty of cases where the port type uses a non-standard algo on
> some CPU subtypes (although things are pretty consistent for the arm side
> so far).
Maybe we could document it as an optional property that we may use for the
legacy CPUs if necessary, but put it into the ARM dts files or into
the driver implementation for the time being.
Arnd
next prev parent reply other threads:[~2013-03-07 5:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 11:30 [PATCH v6 1/3] serial: sh-sci: Add OF support Bastian Hecht
2013-03-06 11:30 ` Bastian Hecht
2013-03-06 11:30 ` [PATCH v6 2/3] ARM: mach-shmobile: r8a7740: Add DT names to clock list Bastian Hecht
2013-03-06 11:30 ` Bastian Hecht
2013-03-06 11:30 ` [PATCH v6 3/3] ARM: mach-shmobile: r8a7740: Setup the serial devices using DT Bastian Hecht
2013-03-06 11:30 ` Bastian Hecht
2013-03-06 12:10 ` [PATCH v6 1/3] serial: sh-sci: Add OF support Laurent Pinchart
2013-03-06 12:10 ` Laurent Pinchart
2013-03-06 12:25 ` Laurent Pinchart
2013-03-06 12:25 ` Laurent Pinchart
2013-03-06 15:29 ` Paul Mundt
2013-03-06 15:29 ` Paul Mundt
2013-03-06 16:33 ` Bastian Hecht
2013-03-06 16:33 ` Bastian Hecht
2013-03-07 5:51 ` Arnd Bergmann [this message]
2013-03-07 5:51 ` Arnd Bergmann
2013-03-07 10:26 ` Bastian Hecht
2013-03-07 10:26 ` Bastian Hecht
2013-03-11 22:32 ` Laurent Pinchart
2013-03-11 22:32 ` Laurent Pinchart
2013-03-12 8:20 ` Paul Mundt
2013-03-12 8:20 ` Paul Mundt
2013-03-12 13:24 ` Laurent Pinchart
2013-03-12 13:24 ` Laurent Pinchart
2013-03-19 15:10 ` Bastian Hecht
2013-03-19 15:10 ` Bastian Hecht
2013-03-27 10:17 ` Laurent Pinchart
2013-03-27 10:17 ` Laurent Pinchart
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=201303070551.59191.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.