Posts
245
Following
37
Followers
270
Linux Kernel developer and maintainer
#standwithukraine 🇵🇱 🇪🇺 🇺🇦 🇨🇭
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social
krzk
repeated
monsieuricon

K. Ryabitsev 🍁

I put together a mailing list etiquette page, in case it's useful for newbie posters.

https://subspace.kernel.org/etiquette.html
5
32
34
krzk

Krzysztof Kozlowski

Reply to @marcan@social.treehouse.systems
Edited 1 year ago
@marcan @broonie @janne That's a way to solve your use case. Might not get pass upstream review, though. DTS should represent real hardware and you created there a virtual regulator. What's more, do your devices have a SDZ supply? Probably not, so also not a true hardware representation. IOW, this is a work-around for the limitations of current OS implementation, so wearing DT maintainer hat: does not looks upstreamable.
1
0
0
krzk

Krzysztof Kozlowski

Reply to @janne@social.treehouse.systems
@janne @broonie @marcan As Janne points, reset controller framework solves this problem ("Shared resets behave similarly to clocks in the kernel clock framework. They provide reference counted deassertion..."), but, now wearing DT maintainer hat, "resets" property points to a reset controller not to a GPIO. It is something else than a reset-gpio. Representing reset-gpio as a reset controller would be an overkill and a workaround for limitations of a specific OS implementation. Thus it would not make me happy as a DT maintainer...

As far as Linux kernel is concerned, I was thinking of stuffing this feature into the GPIO lib: https://lore.kernel.org/alsa-devel/84f9f1c4-0627-4986-8160-b4ab99469b81@linaro.org/
1
0
1
krzk

Krzysztof Kozlowski

What's happening in Poland around parliamentary election is beautiful! People waiting in long queues to vote, sometimes up to 1 AM. Just to vote! 73% turnout - record for Polish parliamentary elections after fall of communism. It is such a great pleasure to see the nation woken up to kick out corrupted, populist, close-minded, anti-democratic party out of their seats!

https://www.theguardian.com/world/2023/oct/15/poland-exit-polls-pis-party-wins-most-votes-but-opposition-coalition-possible
1
12
31
krzk

Krzysztof Kozlowski

Reply to @vegard@mastodon.social
Edited 1 year ago
@vegard Why should they be separate? Probably because no one using generic kernels should ever use CIP kernel? These two worlds - so CIP customers and everyone else - should never intersect?
1
0
0
krzk

Krzysztof Kozlowski

Reply to @vegard@mastodon.social
Edited 1 year ago
@vegard I understand that. I was saying that LF is not involved here. CIP and Greg are different people. One maintains generic stable kernels, other maintain non-generic-long-term stable kernels. Why non-generic kernel should be mixed up with our generic stable kernels? Really, CIP is entirely different thing, so where's the confusing part?
1
0
0
krzk

Krzysztof Kozlowski

Reply to @vegard@mastodon.social
@vegard LF does not send any message here, thus there cannot be a confusion from recipients of its message. Greg sent a message and CIP folks sent their own. What's more CIP folks never said they can support SLTS 10yo *generic* kernel... Basically the customers of CIP SLTS are not customers of stable kernels.
1
0
0
krzk

Krzysztof Kozlowski

Reply to @vegard@mastodon.social
@vegard Do you mean that it is surprising that two people working in the same organization have different point of view on some things?
Also, Linux Foundation gathers many different projects under its umbrella. Some stakeholders want (and pay for) CIP, others don't.
1
0
1
krzk
repeated
josh@josh.tel

Robin Riley (fka Josh)

Edited 1 year ago

I'm proud to call Bradley Kuhn a friend and am celebrating him joining the growing community of out-and-proud FOSS leaders.

But it is a tragedy when someone is forced out.

I've watched as Eben Moglen and SFLC have abused the legal system and attacked SFC, wasting the scarce resources of one of FOSS's most important charitable nonprofits, and am devastated to learn about the personal abuse Bradley has endured.

FOSS friends: please take the time to read this. https://ebb.org/bkuhn/blog/2023/10/11/moglen-sflc.html

2
14
1
krzk

Krzysztof Kozlowski

Reply to @rmader@floss.social
@rmader @mort @cassidy @agx @cas I do not understand that statement, therefore I cannot answer whether I agree or I disagree. I wrote what the DT is for (and what it is not for). To repeat - there is no DT bindings patch in that thread, which I could analyze and respond to.
0
0
0
krzk

Krzysztof Kozlowski

Edited 1 year ago
Keep an eye on this talk for Linux Plumbers Conference 2023 - @abelvesa will be talking about how devices attached to discoverable buses on DT-based platforms need some special kind of powering up solution.
https://lpc.events/event/17/contributions/1507/
I am looking forward to it.
0
2
4
krzk

Krzysztof Kozlowski

Reply to @mort@fosstodon.org
@mort @rmader @agx @cassidy @cas I really have no clue to what you refer (and pasting some links to some long discussions won't help me because none of us has time to read hundreds of pages of possible discussions). For example the cut-off region (inaccessible because of physical layer covering it) for touchscreen got my review and I think it was accepted, so to what do you refer here? Please point me to specific bindings patch where DT maintainers rejected some particular idea. Otherwise I have no clue to what to respond to.
1
0
0
krzk

Krzysztof Kozlowski

Reply to @rmader@floss.social
@rmader @mort @cassidy @agx @cas I do not see any bindings patch there. No comments from DT maintainers either.
1
0
1
krzk

Krzysztof Kozlowski

Reply to @rmader@floss.social
@rmader @agx @mort @cassidy @cas DT is not for software properties. Camera orientation is a hardware property. I don't know from where you get the impression that properties useful to user-space are no allowed. The user of bindings can be in user-space, firmware, bootloader etc.
2
0
1
krzk
repeated
corbet

Jonathan Corbet

So they made a movie about my dad ...

https://fullcirclefilm.co/

...and about a crazy kid named Trevor Kennison and how both recovered their lives after a devastating injury. I've seen it, it's definitely worth a watch. The site lists a lot of upcoming screenings (all just in North America, alas).
0
6
15
krzk

Krzysztof Kozlowski

Reply to @MishaalRahman@androiddev.social
@MishaalRahman News were dropped half a year ago. Nothing new was said this week. :/
1
0
1
krzk

Krzysztof Kozlowski

What a pleasant surprise - I am going to Plumbers! My talk about useful tool-set for fresh Linux kernel maintainers was accepted for this years Linux Plumbers Conference:
https://lpc.events/event/17/contributions/1498/
The cool part is that I will speak very early - on the second slot of the first day.
0
1
11
krzk

Krzysztof Kozlowski

Reply to @gregkh
@gregkh @corbet @sjvn I guess we should start making full, regular press releases, so journalists will not wake up surprised half a year later after the decision is made public.
1
0
4
krzk

Krzysztof Kozlowski

Reply to @kernellogger@fosstodon.org
@kernellogger yeah, it's not the first time news talk about stuff already known in the community...
0
0
1
krzk

Krzysztof Kozlowski

Edited 2 years ago
For a year I have been keeping a branch on top of linux-next with all the cleanups and fixes for Qualcomm SoCs Devicetree sources. Goal is to pass DT schema validation someday (just like Samsung does). I update and rebase the branch frequently. I also add new patches to fix existing warnings. Unfortunately, the branch actually never gets smaller: I always have around 120-200 patches on top of linux-next. Always. Now, after rebasing on next-20230913 it is ~150 patches. Still 150 patches just cannot get applied...

If anyone tells you "Linux kernel development goes too fast", he is wrong. It's too slow. For one year I was able to create fixes much faster than people were applying then.

Branch is here if anyone wants to avoid duplicating work/effort:
https://github.com/krzk/linux/tree/pending/dt-bindings-qcom-new-and-fixes-for-warnings-linux-next
0
0
3
Show older
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: