All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/3] serial: sh-sci: Add OF support
Date: Wed, 06 Mar 2013 10:28:22 +0000	[thread overview]
Message-ID: <201303061028.23084.arnd@arndb.de> (raw)
In-Reply-To: <CABYn4szirgE7jy=49qCR3BuYd9jsWXJ=DrXeCqyuyGP0S2quiQ@mail.gmail.com>

On Wednesday 06 March 2013, Bastian Hecht wrote:
> 2013/3/6 Paul Mundt <lethal@linux-sh.org>:
> > No, we still need to figure out how to generate that baud rate, whether
> > it needs an internal or external clock for driving the rate, etc. The
> > frequency in and of itself doesn't provide this information, and various
> > parts use different algorithms for factoring the baud rate generator,
> > even varying across otherwise identical ports. It's unfortunately not
> > possible to infer anything about the SCBRR algorithm from port type or
> > specified baud rate.
> >
> > The algorithm IDs here are wholly arbitrary anyways, but are the
> > variations I came up with from roughly 60-70 different CPUs.

Ok, I see.

> So if we stick with the notion of the algrithm ID everything is settled now.
> 
> I will prepare a v6 that I will post as the whole patchset and an
> additional incremental patch 1/3 from v3 to v6 for Paul's repo. Then
> we can see if the SCBRR thing needs further discussion and if the rest
> of the patchset is final.

I can't think of anything better either, so let's stick to putting the
algorithm ID into the DT binding.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Bastian Hecht <hechtb@gmail.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
	linux-arm-kernel@lists.infradead.org, linux-sh@vger.kernel.org,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH v4 1/3] serial: sh-sci: Add OF support
Date: Wed, 6 Mar 2013 10:28:22 +0000	[thread overview]
Message-ID: <201303061028.23084.arnd@arndb.de> (raw)
In-Reply-To: <CABYn4szirgE7jy=49qCR3BuYd9jsWXJ=DrXeCqyuyGP0S2quiQ@mail.gmail.com>

On Wednesday 06 March 2013, Bastian Hecht wrote:
> 2013/3/6 Paul Mundt <lethal@linux-sh.org>:
> > No, we still need to figure out how to generate that baud rate, whether
> > it needs an internal or external clock for driving the rate, etc. The
> > frequency in and of itself doesn't provide this information, and various
> > parts use different algorithms for factoring the baud rate generator,
> > even varying across otherwise identical ports. It's unfortunately not
> > possible to infer anything about the SCBRR algorithm from port type or
> > specified baud rate.
> >
> > The algorithm IDs here are wholly arbitrary anyways, but are the
> > variations I came up with from roughly 60-70 different CPUs.

Ok, I see.

> So if we stick with the notion of the algrithm ID everything is settled now.
> 
> I will prepare a v6 that I will post as the whole patchset and an
> additional incremental patch 1/3 from v3 to v6 for Paul's repo. Then
> we can see if the SCBRR thing needs further discussion and if the rest
> of the patchset is final.

I can't think of anything better either, so let's stick to putting the
algorithm ID into the DT binding.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/3] serial: sh-sci: Add OF support
Date: Wed, 6 Mar 2013 10:28:22 +0000	[thread overview]
Message-ID: <201303061028.23084.arnd@arndb.de> (raw)
In-Reply-To: <CABYn4szirgE7jy=49qCR3BuYd9jsWXJ=DrXeCqyuyGP0S2quiQ@mail.gmail.com>

On Wednesday 06 March 2013, Bastian Hecht wrote:
> 2013/3/6 Paul Mundt <lethal@linux-sh.org>:
> > No, we still need to figure out how to generate that baud rate, whether
> > it needs an internal or external clock for driving the rate, etc. The
> > frequency in and of itself doesn't provide this information, and various
> > parts use different algorithms for factoring the baud rate generator,
> > even varying across otherwise identical ports. It's unfortunately not
> > possible to infer anything about the SCBRR algorithm from port type or
> > specified baud rate.
> >
> > The algorithm IDs here are wholly arbitrary anyways, but are the
> > variations I came up with from roughly 60-70 different CPUs.

Ok, I see.

> So if we stick with the notion of the algrithm ID everything is settled now.
> 
> I will prepare a v6 that I will post as the whole patchset and an
> additional incremental patch 1/3 from v3 to v6 for Paul's repo. Then
> we can see if the SCBRR thing needs further discussion and if the rest
> of the patchset is final.

I can't think of anything better either, so let's stick to putting the
algorithm ID into the DT binding.

	Arnd

  reply	other threads:[~2013-03-06 10:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04 15:23 [PATCH v4 1/3] serial: sh-sci: Add OF support Bastian Hecht
2013-03-04 16:20 ` Bastian Hecht
2013-03-04 16:20 ` Bastian Hecht
2013-03-04 15:23 ` [PATCH v4 2/3] ARM: mach-shmobile: r8a7740: Add DT names to clock list Bastian Hecht
2013-03-04 16:20   ` Bastian Hecht
2013-03-04 16:20   ` Bastian Hecht
2013-03-04 15:29 ` [PATCH v4 3/3] ARM: mach-shmobile: r8a7740: Setup the serial devices using DT Bastian Hecht
2013-03-04 16:20   ` Bastian Hecht
2013-03-04 16:20   ` Bastian Hecht
2013-03-04 16:22   ` Arnd Bergmann
2013-03-04 16:22     ` Arnd Bergmann
2013-03-04 16:22     ` Arnd Bergmann
2013-03-05 13:00     ` Bastian Hecht
2013-03-05 13:00       ` Bastian Hecht
2013-03-05 13:00       ` Bastian Hecht
2013-03-05 13:42       ` Sergei Shtylyov
2013-03-05 13:42         ` Sergei Shtylyov
2013-03-05 13:42         ` Sergei Shtylyov
2013-03-05 13:47         ` Bastian Hecht
2013-03-05 13:47           ` Bastian Hecht
2013-03-05 13:47           ` Bastian Hecht
2013-03-05 19:22       ` Arnd Bergmann
2013-03-05 19:22         ` Arnd Bergmann
2013-03-05 19:22         ` Arnd Bergmann
2013-03-04 16:20 ` [PATCH v4 1/3] serial: sh-sci: Add OF support Arnd Bergmann
2013-03-04 16:20   ` Arnd Bergmann
2013-03-04 16:20   ` Arnd Bergmann
2013-03-05 12:58   ` Bastian Hecht
2013-03-05 12:58     ` Bastian Hecht
2013-03-05 12:58     ` Bastian Hecht
2013-03-05 19:26     ` Arnd Bergmann
2013-03-05 19:26       ` Arnd Bergmann
2013-03-05 19:26       ` Arnd Bergmann
2013-03-06  0:50       ` Paul Mundt
2013-03-06  0:50         ` Paul Mundt
2013-03-06  0:50         ` Paul Mundt
2013-03-06 10:19         ` Bastian Hecht
2013-03-06 10:19           ` Bastian Hecht
2013-03-06 10:19           ` Bastian Hecht
2013-03-06 10:28           ` Arnd Bergmann [this message]
2013-03-06 10:28             ` Arnd Bergmann
2013-03-06 10:28             ` Arnd Bergmann

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