All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] serial: ns16550: Add register shift variable
Date: Mon, 16 Jul 2018 18:47:21 +0300	[thread overview]
Message-ID: <CAHp75VdYDirzq8qKNrgwSOkyOJj12-GiCo84gRc+CjeDif90nA@mail.gmail.com> (raw)
In-Reply-To: <4881796E12491D4BB15146FE0209CE64681148D9@DE02WEMBXB.internal.synopsys.com>

On Mon, Jul 16, 2018 at 6:04 PM, Alexey Brodkin
<Alexey.Brodkin@synopsys.com> wrote:

>> > Any chance to get a reference to the commit in Linux kernel that introduces that change?
>> >
>> In fact I believe that the <reg-shift> property never existed in the
>> am33xx.dtsi file from Linux. U-Boot commit 85cf0e6299 shows that the
>> property has been added to U-Boot's am33xx.dtsi file. The commit log
>> clearly states why this happened:
>>
>> "With the commit 'c7b9686d5d48 ("ns16550: unify serial_omap")' all
>> TI platforms are broken with DM/DT boot as ns16550 driver expects
>> reg-shift from DT which is not populated for TI platforms.
>> Earlier it worked as it was hard coded to 2 in serial-omap
>> driver. So adding the reg-shift to serial nodes for dra7, am4372
>> and am33xx dtsi files. Tested this patch on am437x-sk-evm,
>> am437x-gp-evm, am335x-boneblack, dra74x-evm and dra72x-evm."
>
> Ok so this has nothing to do with changes in Linux kernel I guess.
> Why don't we go the other way around and not just submit
> a change to .dts files in Linux kernel that are missing required properties?

You may change DTSi files in the Linux kernel sources tree, but you
wouldn't be able to fix all DTB:s in the wild.
In this case Linux should have a fallback to the previous value in
case property is not found.

-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2018-07-16 15:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13 14:43 [U-Boot] [PATCH] serial: ns16550: Add register shift variable Felix Brack
2018-07-13 15:08 ` Alexander Graf
2018-07-14 10:47 ` Wolfgang Denk
2018-07-14 15:49   ` Tom Rini
2018-07-15  8:43     ` Alexey Brodkin
2018-07-15 14:02       ` Felix Brack
2018-07-16 15:04         ` Alexey Brodkin
2018-07-16 15:47           ` Andy Shevchenko [this message]
2018-07-17 13:24             ` Tom Rini
2018-07-17  6:51           ` Felix Brack
2018-07-17 13:34             ` Alexander Graf
2018-07-15 11:17     ` Felix Brack
2018-07-16 12:42       ` Wolfgang Denk
2018-07-16 12:48         ` Felix Brack
2018-07-16 12:53     ` Alexander Graf
2018-07-17 13:25       ` Tom Rini
2018-07-17 13:33         ` Alexander Graf
2018-07-17 13:34           ` Alexey Brodkin
2018-07-17 13:41             ` Tom Rini
2018-07-17 13:43               ` Alexander Graf
2018-07-18  8:26                 ` Lokesh Vutla
2018-07-17 21:23             ` Andy Shevchenko
2018-07-17 21:30               ` Adam Ford
2018-07-17 21:46                 ` Andy Shevchenko
2018-07-17 13:39           ` Tom Rini
2018-07-15 11:05   ` Felix Brack

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=CAHp75VdYDirzq8qKNrgwSOkyOJj12-GiCo84gRc+CjeDif90nA@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.