From: Denis Turischev <denis@compulab.co.il>
To: Greg KH <greg@kroah.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
Subject: Re: [PATCH v3] pch_uart: reference clock on CM-iTC
Date: Sun, 13 Mar 2011 15:48:00 +0200 [thread overview]
Message-ID: <4D7CCB10.50009@compulab.co.il> (raw)
In-Reply-To: <20110311222529.GA14675@kroah.com>
Hi Greg,
There is a patch to pch_phub.c that is absent in your linux/kernel/git/gregkh/tty-2.6.git
pch_phub: add new device ML7213
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=c47dda7d179dde17697c3f839f150fecaf6770cb
>From which repository you want my patch to be based?
On 03/12/2011 12:25 AM, Greg KH wrote:
> On Thu, Mar 10, 2011 at 03:14:00PM +0200, Denis Turischev wrote:
>> Default clock source for UARTs on Topcliff is external UART_CLK.
>> On CM-iTC USB_48MHz is used instead. After VCO2PLL and DIV
>> manipulations UARTs will receive 192 MHz.
>> Clock manipulations on Topcliff are controlled in pch_phub.c
>>
>> v2: redone against the linux-next tree
>> v3: redone against linux/kernel/git/next/linux-next.git snapshot
>>
>> Signed-off-by: Denis Turischev <denis@compulab.co.il>
>> ---
>> diff -Nru linux-next-20110310.orig/drivers/misc/pch_phub.c linux-next-20110310/drivers/misc/pch_phub.c
>> --- linux-next-20110310.orig/drivers/misc/pch_phub.c 2011-03-10 08:31:30.000000000 +0200
>> +++ linux-next-20110310/drivers/misc/pch_phub.c 2011-03-10 14:42:05.110978473 +0200
>> @@ -618,6 +626,14 @@
>> CLKCFG_CAN_50MHZ,
>> CLKCFG_CANCLK_MASK);
>>
>> + /* quirk for CM-iTC board */
>> + if (strstr(dmi_get_system_info(DMI_BOARD_NAME), "CM-iTC"))
>> + pch_phub_read_modify_write_reg(chip,
>> + (unsigned int)CLKCFG_REG_OFFSET,
>> + CLKCFG_UART_48MHZ | CLKCFG_BAUDDIV |
>> + CLKCFG_PLL2VCO | CLKCFG_UARTCLKSEL,
>> + CLKCFG_UART_MASK);
>> +
>
> This is the chunk that is causing problems. I guess someone else
> modified this file in the linux-next tree, and I can't apply it in mine.
> Any ideas who did this change? Can you look at the linux-next tree and
> see what caused this merge issue?
>
> thanks,
>
> greg k-h
--
Denis
next prev parent reply other threads:[~2011-03-13 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 9:31 pch_uart: reference clock on CM-iTC Denis Turischev
2011-03-07 20:07 ` Greg KH
2011-03-08 12:22 ` [PATCH v2] " Denis Turischev
2011-03-09 23:42 ` Greg KH
2011-03-10 13:14 ` [PATCH v3] " Denis Turischev
2011-03-11 22:25 ` Greg KH
2011-03-13 13:48 ` Denis Turischev [this message]
2011-03-14 23:25 ` Greg KH
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=4D7CCB10.50009@compulab.co.il \
--to=denis@compulab.co.il \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tomoya-linux@dsn.okisemi.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