From: Stefan Wahren <stefan.wahren@i2se.com>
To: "Ivan T. Ivanov" <iivanov@suse.de>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Phil Elwell <phil@raspberrypi.org>,
kernel test robot <lkp@intel.com>,
bcm-kernel-feedback-list@broadcom.com, linux-clk@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] clk: bcm2835: Round UART input clock up
Date: Tue, 19 Apr 2022 18:11:21 +0200 [thread overview]
Message-ID: <c57d6490-7439-d49f-369c-5356b6c4eeee@i2se.com> (raw)
In-Reply-To: <20220419150555.igh6tdxgjb7meygx@suse>
Hi Ivan,
Am 19.04.22 um 17:05 schrieb Ivan T. Ivanov:
> On 04-18 18:01, Stefan Wahren wrote:
>>>> Do you use the mainline DTS or the vendor DTS to see this issue?
>>>>
>>> For (open)SUSE we use downstream DTS.
>> This is popular and bad at the same time. We as the mainline kernel
>> developer cannot guarantee that this works as expected. A lot of issues are
>> caused by mixing vendor DTS with mainline kernel, so in general (not for
>> this specific issue) you are on your own with this approach.
>>
> Yep, I am aware of that. I am still trying to recover after recent
> gpio-ranges fiasco, also still working on fixing non-exported firmware
> clocks, which break HDMI output on some of the devices.
I guess, these firmware clock issues are only reproducible with vendor DTS?
>
>> I know this is a little bit off topic but except from overlay support, can
>> you provide a list of most missing features of the mainline kernel / DTS?
> Well, 260+ overlays for free is not insignificant benefit. Beside few
> breakages from time to time using downstream device tree works fine.
I think the better approach is to add the missing steps for overlay
support in mainline.
Best regards
>
> Regards,
> Ivan
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-04-19 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 12:51 [PATCH v2] clk: bcm2835: Round UART input clock up Ivan T. Ivanov
2022-04-14 10:56 ` Ivan T. Ivanov
2022-04-15 8:52 ` Stefan Wahren
2022-04-18 11:05 ` Ivan T. Ivanov
2022-04-18 11:22 ` Stefan Wahren
2022-04-18 11:38 ` Ivan T. Ivanov
2022-04-18 16:01 ` Stefan Wahren
2022-04-19 15:05 ` Ivan T. Ivanov
2022-04-19 16:11 ` Stefan Wahren [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=c57d6490-7439-d49f-369c-5356b6c4eeee@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=aou@eecs.berkeley.edu \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=iivanov@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=mturquette@baylibre.com \
--cc=nsaenz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=phil@raspberrypi.org \
--cc=rjui@broadcom.com \
--cc=sboyd@kernel.org \
--cc=sbranden@broadcom.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