Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Gabor Juhos <juhosg@openwrt.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH] tty: ar933x_uart: use the clk API to get the uart clock
Date: Wed, 28 Aug 2013 10:02:22 +0200	[thread overview]
Message-ID: <521DAE8E.3030007@openwrt.org> (raw)
In-Reply-To: <20130827232707.GA10719@kroah.com>

2013.08.28. 1:27 keltezéssel, Greg Kroah-Hartman írta:
> On Tue, Aug 27, 2013 at 10:14:25PM +0200, Gabor Juhos wrote:
>> The AR933x UARTs are only used on the Atheros AR933x
>> SoCs. The base clock frequency of the UART is passed
>> to the driver via platform data. The SoC support code
>> implements the generic clock API, and the clock rate
>> can be retrieved via that.
>>
>> Update the code to get the clock rate via the generic
>> clock API instead of using the platform data.
>>
>> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
>> ---
>> Note:
>>
>> Because the driver specific platform data only contains
>> the clock frequency it can be removed. In order to avoid
>> merge conflicts between different trees, it will be removed
>> by a later patch once this one is merged upstream.
> 
> I don't understand what you mean by this.

Currently the clock frequency is passed to the driver through platform data and
the platform data is initialized via platform specific setup code in
'arch/mips/ath79/dev-common.c'.

After this patch, the platform data is not used by the driver, so the
initialization will be superfluous and it can be removed along with the
'arch/mips/include/asm/mach-ath79/ar933x_uart_platform.h' header file.

However those changes would cause merge conflicts with my other patches which
are going through the MIPS tree so I kept out that part from the patch.

> Also, this patch doesn't even apply to my tty-next tree, so I can't
> accept it as-is, so please fix it up,

Sorry, it was based on 3.11-rc7. Will rebase it against the tty-next tree.

> work with the people whose patches yours is conflicting with, and figure out
> how to do this with the least amount of merge issues.

Ok.

Thanks,
Gabor
--
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

      reply	other threads:[~2013-08-28  8:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27 20:14 [PATCH] tty: ar933x_uart: use the clk API to get the uart clock Gabor Juhos
2013-08-27 23:27 ` Greg Kroah-Hartman
2013-08-28  8:02   ` Gabor Juhos [this message]

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=521DAE8E.3030007@openwrt.org \
    --to=juhosg@openwrt.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-serial@vger.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