From: Krzysztof Kozlowski <firstname.lastname@example.org> To: Lee Jones <email@example.com> Cc: Will McVicker <firstname.lastname@example.org>, Geert Uytterhoeven <email@example.com>, Catalin Marinas <firstname.lastname@example.org>, Will Deacon <email@example.com>, Sylwester Nawrocki <firstname.lastname@example.org>, Tomasz Figa <email@example.com>, Chanwoo Choi <firstname.lastname@example.org>, Michael Turquette <email@example.com>, Stephen Boyd <firstname.lastname@example.org>, Android Kernel Team <email@example.com>, Linux ARM <firstname.lastname@example.org>, Linux Kernel Mailing List <email@example.com>, linux-samsung-soc <firstname.lastname@example.org>, linux-clk <email@example.com> Subject: Re: [PATCH v1 1/4] clk: samsung: change COMMON_CLK_SAMSUNG default config logic Date: Thu, 23 Sep 2021 18:27:28 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <YUyMyVezyjfv1Hs7@google.com> On 23/09/2021 16:18, Lee Jones wrote: >> Thanks Lee, you described the use case. In general I like it and support >> it, except for what I wrote in the other mail. >> >> Vendor does not contribute much therefore there is no balance in >> upstreaming. Since none of other vendor's platforms are supported, I am >> looking only at what is supported. From that perspective - the change >> proposed by Will and previous guys, does not have much sense. >> >> My perspective probably would change a lot if vendor did contribute some >> of its non-edge platforms (3-5 years old)... especially that unlike few >> community guys (e.g. PostmarketOS), vendor has shit-tons of money and >> the hardware manuals. :) > > But no incentive to upstream code old (dead) platforms that they no > longer make money from. We're not talking about kind-hearted > individuals here. These are business entities. > > What is the business incentive to put hundreds of thousands of dollars > into something with no RoI? Before you mentioned business entities refrain from upstreaming recent hardware. You question upstreaming not that recent, so basically business entity will claim it has zero incentives working with upstream. Actually there are incentives for both cases - better code quality for the pieces being base for future devices, selling mainline supported hardware to other businesses, eventually less work for themselves around keeping code in sync with mainline. All these are of course difficult to measure from business perspective. > >> Instead of pushing this change, please let's give some incentive to the >> vendor for upstreaming anything. > > Again, you're being specific. We would also like/need to make the > same kinds of changes to other vendor configurations. One's which do > contribute significantly at their own cost. Yes, I am specific because we talk here about specfic Kconfig changes for one specific ARM sub-architecture. Same set of changes can be applied to other SoCs and usually have more sense there because number of upstream platforms is bigger. If you have 10 different pinctrl drivers, you might decide to narrow the defconfigs to subset of it. If you have 2-3, the extra complexity does not matter and you just enable all of them. That's also decision we made few years ago internally in Samsung. > The technical reasoning cannot be different because you do or don't > like the way the company operates. Try to detach a little from > your feelings during discussions which should be purely technical. I mentioned the less-contributing vendor arguments because you said: >> Vendors are not able to upstream all functionality right away That's the side-topic in this discussion. Technically, all supported Exynos platforms require selecting ARCH_EXYNOS and require all drivers selected by ARCH_EXYNOS. If you mention some unsupported out-of-tree platforms, which I cannot audit/see/use, it is not a valid reason to change statement above. Make them supported, available to audit and check and statement above stops being valid. Best regards, Krzysztof
next prev parent reply other threads:[~2021-09-23 16:27 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-20 19:03 [PATCH v1 0/4] arm64: Kconfig: Update ARCH_EXYNOS select configs Will McVicker 2021-09-20 19:03 ` [PATCH v1 1/4] clk: samsung: change COMMON_CLK_SAMSUNG default config logic Will McVicker 2021-09-21 7:29 ` Krzysztof Kozlowski 2021-09-21 7:50 ` Geert Uytterhoeven 2021-09-21 8:35 ` Krzysztof Kozlowski 2021-09-21 17:58 ` Will McVicker 2021-09-21 18:04 ` Krzysztof Kozlowski 2021-09-23 12:57 ` Lee Jones 2021-09-23 13:27 ` Krzysztof Kozlowski 2021-09-23 14:18 ` Lee Jones 2021-09-23 16:27 ` Krzysztof Kozlowski [this message] 2021-09-23 16:30 ` Krzysztof Kozlowski 2021-09-20 19:03 ` [PATCH v1 2/4] soc: samsung: change SOC_SAMSUNG " Will McVicker 2021-09-20 20:57 ` Will McVicker 2021-09-21 7:23 ` Krzysztof Kozlowski 2021-09-21 8:19 ` Lee Jones 2021-09-21 17:45 ` Will McVicker 2021-09-21 18:20 ` Krzysztof Kozlowski 2021-09-23 12:39 ` Lee Jones 2021-09-23 12:57 ` Krzysztof Kozlowski 2021-09-23 13:41 ` Lee Jones 2021-09-23 16:19 ` Geert Uytterhoeven 2021-09-23 18:05 ` Geert Uytterhoeven 2021-09-20 19:03 ` [PATCH v1 3/4] pinctrl: samsung: change PINCTRL_EXYNOS " Will McVicker 2021-09-21 7:27 ` Krzysztof Kozlowski 2021-09-21 8:18 ` Lee Jones 2021-09-23 21:52 ` Linus Walleij 2021-09-21 7:08 ` [PATCH v1 0/4] arm64: Kconfig: Update ARCH_EXYNOS select configs Lee Jones 2021-09-21 7:19 ` Krzysztof Kozlowski 2021-09-21 7:22 ` Krzysztof Kozlowski 2021-09-21 8:11 ` Lee Jones 2021-09-21 8:25 ` Krzysztof Kozlowski 2021-09-21 8:41 ` Lee Jones 2021-09-25 2:17 ` Saravana Kannan 2021-09-27 8:08 ` Krzysztof Kozlowski 2021-09-27 8:16 ` Geert Uytterhoeven 2021-09-27 18:07 ` Saravana Kannan 2021-09-27 19:54 ` Geert Uytterhoeven
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v1 1/4] clk: samsung: change COMMON_CLK_SAMSUNG default config logic' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).