linux-kernel - Re: [PATCH v2] clk: bcm2835: Round UART input clock up

Open Source and information security mailing list archives

Date:   Tue, 19 Apr 2022 18:11:21 +0200
From:   Stefan Wahren <stefan.wahren@...e.com>
To:     "Ivan T. Ivanov" <iivanov@...e.de>
Cc:     Michael Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...nel.org>,
        Nicolas Saenz Julienne <nsaenz@...nel.org>,
        Florian Fainelli <f.fainelli@...il.com>,
        Ray Jui <rjui@...adcom.com>,
        Scott Branden <sbranden@...adcom.com>,
        Paul Walmsley <paul.walmsley@...ive.com>,
        Palmer Dabbelt <palmer@...belt.com>,
        Albert Ou <aou@...s.berkeley.edu>,
        Phil Elwell <phil@...pberrypi.org>,
        kernel test robot <lkp@...el.com>,
        bcm-kernel-feedback-list@...adcom.com, linux-clk@...r.kernel.org,
        linux-rpi-kernel@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] clk: bcm2835: Round UART input clock up

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@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives