Any pending patches on me for Samsung SoC? Closing applying cycle

Any pending patches on me for Samsung SoC? Closing applying cycle

[Krzysztof Kozlowski]

Hey,

I went through my inbox and cleared my queue because I am approaching
end of applying cycle. I think I dealt with everything and pending
things are:

1. Exynos7870 SoC: waits for bindings,

2. Exynos990 watchdog: waits for bindings, replied some days ago,

3. GS101 pinctrl fixes: waits for review but I will apply soon:
https://lore.kernel.org/all/20250301-pinctrl-fltcon-suspend-v2-0-a7eef9bb443b@linaro.org/

4. ACPM firmware debug interface: I replied now, need more discussion
about interface

5. arm64: dts: exynos: update all samsung,mode constants: will wait one
cycle

Did I miss anything? Is there something still pending on me?

Best regards,
Krzysztof

Re: Any pending patches on me for Samsung SoC? Closing applying cycle

[Ivaylo Ivanov]

On 3/5/25 21:45, Krzysztof Kozlowski wrote:
> Hey,
>
> I went through my inbox and cleared my queue because I am approaching
> end of applying cycle. I think I dealt with everything and pending
> things are:
>
> 1. Exynos7870 SoC: waits for bindings,
>
> 2. Exynos990 watchdog: waits for bindings, replied some days ago,
>
> 3. GS101 pinctrl fixes: waits for review but I will apply soon:
> https://lore.kernel.org/all/20250301-pinctrl-fltcon-suspend-v2-0-a7eef9bb443b@linaro.org/
>
> 4. ACPM firmware debug interface: I replied now, need more discussion
> about interface
>
> 5. arm64: dts: exynos: update all samsung,mode constants: will wait one
> cycle
>
> Did I miss anything? Is there something still pending on me?

Hey Krzysztof,

Thanks for your work! I just noticed that there's an inaccuracy in [1]
where instead of setting only BIT(2), all bits in the register are getting
flipped except BIT(2), and it forces clock request state. Is there any
room left for me to send out a bugfix tomorrow?

Otherwise all other important patches of mine have been applied,
except 2200 usb phy and device tree series, which I think should be
sorted out soon for after the merge window.

[1]: soc: samsung: usi: add a routine for unconfiguring the ip
https://lore.kernel.org/r/20250204172803.3425496-3-ivo.ivanov.ivanov1@gmail.com

Best regards,
Ivaylo

>
> Best regards,
> Krzysztof
>

Re: Any pending patches on me for Samsung SoC? Closing applying cycle

[Krzysztof Kozlowski]

On 05/03/2025 22:07, Ivaylo Ivanov wrote:
>>
>> 5. arm64: dts: exynos: update all samsung,mode constants: will wait one
>> cycle
>>
>> Did I miss anything? Is there something still pending on me?
> 
> Hey Krzysztof,
> 
> Thanks for your work! I just noticed that there's an inaccuracy in [1]
> where instead of setting only BIT(2), all bits in the register are getting
> flipped except BIT(2), and it forces clock request state. Is there any
> room left for me to send out a bugfix tomorrow?


Yes, no problem, bugfixes can keep going. I am closing my tree (usually
around rc5 or rc6) for new features and non-bugfix patches.

Best regards,
Krzysztof

Re: Any pending patches on me for Samsung SoC? Closing applying cycle

[Kaustabh Chakraborty]

On 2025-03-05 19:45, Krzysztof Kozlowski wrote:
> Hey,
> 
> I went through my inbox and cleared my queue because I am approaching
> end of applying cycle. I think I dealt with everything and pending
> things are:
> 
> 1. Exynos7870 SoC: waits for bindings,

Is this possible to be merged? [1]
It's over a month old at this point, seemingly left untouched.

This one's also a build dependency for [2], as mentioned in its cover
letter.

[1] https://lore.kernel.org/all/20250204-exynos7870-bootmode-v1-1-0f17b3033c2d@disroot.org/
[2] https://lore.kernel.org/all/174100756283.1496281.12555971793250210333.robh@kernel.org/

Re: Any pending patches on me for Samsung SoC? Closing applying cycle

[Krzysztof Kozlowski]

On 06/03/2025 15:03, Kaustabh Chakraborty wrote:
> On 2025-03-05 19:45, Krzysztof Kozlowski wrote:
>> Hey,
>>
>> I went through my inbox and cleared my queue because I am approaching
>> end of applying cycle. I think I dealt with everything and pending
>> things are:
>>
>> 1. Exynos7870 SoC: waits for bindings,
> 
> Is this possible to be merged? [1]
> It's over a month old at this point, seemingly left untouched.

I don't have it in my inbox for some reason. Regardless, you want it to
be a binding, so is it going to be used also by U-Boot?

> 
> This one's also a build dependency for [2], as mentioned in its cover
> letter.
> 
> [1] https://lore.kernel.org/all/20250204-exynos7870-bootmode-v1-1-0f17b3033c2d@disroot.org/
> [2] https://lore.kernel.org/all/174100756283.1496281.12555971793250210333.robh@kernel.org/

Then it should not have been sent separately. Patchset should be split
by subsystem, so this belongs to soc with the rest.

Best regards,
Krzysztof

Re: Any pending patches on me for Samsung SoC? Closing applying cycle

[Kaustabh Chakraborty]

On 2025-03-06 18:07, Krzysztof Kozlowski wrote:
> On 06/03/2025 15:03, Kaustabh Chakraborty wrote:
>> On 2025-03-05 19:45, Krzysztof Kozlowski wrote:
>>> Hey,
>>>
>>> I went through my inbox and cleared my queue because I am approaching
>>> end of applying cycle. I think I dealt with everything and pending
>>> things are:
>>>
>>> 1. Exynos7870 SoC: waits for bindings,
>> 
>> Is this possible to be merged? [1]
>> It's over a month old at this point, seemingly left untouched.
> 
> I don't have it in my inbox for some reason. Regardless, you want it to
> be a binding, so is it going to be used also by U-Boot?

Don't have any plans with u-boot at the moment, though I'll likely consider
it later. The macros are used with syscon-reboot-mode which helps switching
modes from userland.

> 
>> 
>> This one's also a build dependency for [2], as mentioned in its cover
>> letter.
>> 
>> [1] https://lore.kernel.org/all/20250204-exynos7870-bootmode-v1-1-0f17b3033c2d@disroot.org/
>> [2] https://lore.kernel.org/all/174100756283.1496281.12555971793250210333.robh@kernel.org/
> 
> Then it should not have been sent separately. Patchset should be split
> by subsystem, so this belongs to soc with the rest.

Hmm, getmaintainer didn't report it as part of the soc subsystem, although
the file path does have 'soc' in it. And thus I decided to kept it
separate.

> 
> Best regards,
> Krzysztof

Re: Any pending patches on me for Samsung SoC? Closing applying cycle

[Krzysztof Kozlowski]

On 06/03/2025 19:37, Kaustabh Chakraborty wrote:
> On 2025-03-06 18:07, Krzysztof Kozlowski wrote:
>> On 06/03/2025 15:03, Kaustabh Chakraborty wrote:
>>> On 2025-03-05 19:45, Krzysztof Kozlowski wrote:
>>>> Hey,
>>>>
>>>> I went through my inbox and cleared my queue because I am approaching
>>>> end of applying cycle. I think I dealt with everything and pending
>>>> things are:
>>>>
>>>> 1. Exynos7870 SoC: waits for bindings,
>>>
>>> Is this possible to be merged? [1]
>>> It's over a month old at this point, seemingly left untouched.
>>
>> I don't have it in my inbox for some reason. Regardless, you want it to
>> be a binding, so is it going to be used also by U-Boot?
> 
> Don't have any plans with u-boot at the moment, though I'll likely consider
> it later. The macros are used with syscon-reboot-mode which helps switching
> modes from userland.

Exynos Auto added first binding for that, but I am not sure if we need
to keep going. Binding describes the interface, so for whom do you
describe it here? I can imagine downstream bootloader, but that is I
don't believe it is worth adding bindings for downstream.

If you it is not for downstream then it has to be for some other
upstream project. Which one?


> 
>>
>>>
>>> This one's also a build dependency for [2], as mentioned in its cover
>>> letter.
>>>
>>> [1] https://lore.kernel.org/all/20250204-exynos7870-bootmode-v1-1-0f17b3033c2d@disroot.org/
>>> [2] https://lore.kernel.org/all/174100756283.1496281.12555971793250210333.robh@kernel.org/
>>
>> Then it should not have been sent separately. Patchset should be split
>> by subsystem, so this belongs to soc with the rest.
> 
> Hmm, getmaintainer didn't report it as part of the soc subsystem, although
> the file path does have 'soc' in it. And thus I decided to kept it
> separate.
Yes, that's a missing path.

Best regards,
Krzysztof