From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2DCFE36D510 for ; Fri, 16 Jan 2026 11:30:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.168.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768563024; cv=none; b=VwUqO+RLfH9OqMs922cbxzuliaY7yWTVYGWfmct7+DOw1NvEhjsGuQ5K7w7Iboy8Gpa743VoiWXIk9j2jtL8lpdiTUsk2DY2dDDePoyV8BIjUIUm+886DdW7TpXNrj6PlWOhQk0fVgy73wFIzUAnwokGXjHFNI1uplicnklMIYI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768563024; c=relaxed/simple; bh=TQTvbgiBG+SKBmDtt/7Qz10lccsxtBeY3EJYQbt/5ik=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=XhCeLPcbLoSBFbvZOogzdH9aVOcfNveZnai2uXdWetiOJSF89gpigxnXyisRc47nUA9vpFj9U7PPE8Y81hyUPaOFd2HLWIqQznhjihoeLGanv70LEHiEhESYLosJN+GV5asWoC/aho6TzH8KdYxlgHQYMNeXERrAgmA5Y9r2df0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com; spf=pass smtp.mailfrom=oss.qualcomm.com; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b=EKDM+ota; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b=QQfjddRa; arc=none smtp.client-ip=205.220.168.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b="EKDM+ota"; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b="QQfjddRa" Received: from pps.filterd (m0279864.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 60G8RIwQ1240858 for ; Fri, 16 Jan 2026 11:30:20 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qualcomm.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=qcppdkim1; bh= 09h4tPa/kI/gXdQi3NlmGSOnFal6CqO9SCpG9ObzGqg=; b=EKDM+otaqzpTsTFA a89rMF/q7ULUU7gUWmU7o9AqUkG+2q1cUlfYNuW+/2aovpB9/kNM8O7Ieoxaouex ihjYuB56RU2C4U19LMsDVCi+o3M1yIjJICA8GZPQy1dLNgvuETB8lar0nd+IGaA9 4DaGbfARlhv8jY0tnLXy5Mnh5npnjDq6N/Dt7K92529MoQoqBLlRg8DeSWmgU/86 flVAksWe7iSF+RdClH/xIE4bYJLySa1daCGBuwByR7FhodX/WVWytTsnBJhGThYW KfUvGNfx456A+k9ni7uXk42pngMUSxvmvsLFafUV/4YrNE/Ru8X6jGgDrNOXVR8T P+chMw== Received: from mail-qt1-f197.google.com (mail-qt1-f197.google.com [209.85.160.197]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 4bq96ssxkg-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Fri, 16 Jan 2026 11:30:20 +0000 (GMT) Received: by mail-qt1-f197.google.com with SMTP id d75a77b69052e-50144419b6cso5478621cf.2 for ; Fri, 16 Jan 2026 03:30:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oss.qualcomm.com; s=google; t=1768563019; x=1769167819; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=09h4tPa/kI/gXdQi3NlmGSOnFal6CqO9SCpG9ObzGqg=; b=QQfjddRayv+T+WaY83A5RhOt6+fbsKNjg75jFzuyxCsT7umKhkNTvQp4GJDWggW+Fz b1TAYIRsHk13DOtp1CwQpkHz51Y6IarZ9iaxmaj8VUmbJMoP9xdzh4y3RoD5UqAKjMN2 BinobVjmbKvRnP4MP5Ql8/S99novFYhGH6Fi1lIKu03vdHthSZDU7V0FheepmO4cFxxL 6BE2vBAROgz7Ehs4qBPrlujFXGztRZ/Na9GnAnJ6EKrk7LX4pJYPfngbv+UBAhPTJ+VV jUPDD51snMmxAgCaqZMUYwAO83/Vkwzk03YVn9xtZcIJN6Iy2cJVXbQs/jtcDNU76oMb j3nQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768563019; x=1769167819; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=09h4tPa/kI/gXdQi3NlmGSOnFal6CqO9SCpG9ObzGqg=; b=YeQX4ZAIWi3uALupXM2h+gi0rUA8wMz2NG4IJtgyX9iDExAs67g25HyNY2PBQGS82G HL4PYhzSclZgoRkQn0u01U5CjQEDAT0S/WVNe59JFWJhKMagsijVQUFTSY1DTuVJh2WW DU1CGcvBcKWZJmbcou34BfyItDa2e+zwNBCm7480sXSvSTot4x2ziPd5fwO5OrbSFL1q QrzCpdR/GW0UG6GhsOgRMhFOaLUz4neaYZ6OUozr9CwtY8uwuPItl+tYBq9k7tKcYtKz DDrBY2m1+3/f+atJ37wOrr4s5NRZg7D+0/MJdGt6CcM193AZgOsmtbHkk0l5fI12Pjpk /jXA== X-Forwarded-Encrypted: i=1; AJvYcCUgu/xszSeHwHDgsbxQkB4eSCqy8N24hAVLRkleYjG/pvffw75RE8+Lq6oq8Wkk2jCZkpAAU4mnHPu/uuLQ3uc=@vger.kernel.org X-Gm-Message-State: AOJu0Yx7brUNqHzUZnMdJzQajSRDVocT5s54f0uiuVIbFZLaSs2h4Nd1 okpc+RGzrYvzw6Weu/OFKgFOLKmCMfKbMW+wK6LCxe3GTuU3YbVNxkvVzQfh1b/uKRqeENLOCCS JgDcjqkFtDSshKtgqXzt44aQ7mUw8aISTIS0WmavGAcR5Huiu/GLSn7Z8i46XTrRrJ4S3oO8= X-Gm-Gg: AY/fxX4YWA58MiYAH7NEYe1S0ZqCDC7xLL+1bj4tDVABZ16j/Bum7AtqHwE1RXtVKRg YKSyF8/atXQbbbN+fV2DQ4R58WkRllj76uVlPtGqC6pEP21QEmi8FnPysUjR4e4mxlao3FxP8Fr rqp35bMTdGQ07z/9NQ13Y2EyrOFbGZYIDYxXfPbMC848+rfT9i6Xa823iYhdy8hJGFpDeAdQGwz auYbEk/Q7XZHdTkQe9nwMTl9iIjz/JplpbNt6p81E6mDN7tT/SCcqeK+IM5tTuS550vW/uIDhbj oAAfGVQT/NGsI1mCZaUy1w8Dos/FsU2HBGM9W09UWOr9sfcNhp3sKXtU+IJsRoL1telGfdephSd v8q/l+1cXsdp4hpNxqjAw/ozHJp62O0+KFQ29MnUFB8o30jajyOsdNU48ewzVKXFCQtE= X-Received: by 2002:a05:622a:1794:b0:501:4767:a6f with SMTP id d75a77b69052e-502a16043c2mr26336821cf.3.1768563017766; Fri, 16 Jan 2026 03:30:17 -0800 (PST) X-Received: by 2002:a05:622a:1794:b0:501:4767:a6f with SMTP id d75a77b69052e-502a16043c2mr26336231cf.3.1768563017270; Fri, 16 Jan 2026 03:30:17 -0800 (PST) Received: from [192.168.119.254] (078088045245.garwolin.vectranet.pl. [78.88.45.245]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-b879513ed07sm226392566b.3.2026.01.16.03.30.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 16 Jan 2026 03:30:16 -0800 (PST) Message-ID: <42a0e768-c217-44b2-81ba-1237d9f983f9@oss.qualcomm.com> Date: Fri, 16 Jan 2026 12:30:14 +0100 Precedence: bulk X-Mailing-List: linux-hardening@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 2/6] arm64: dts: qcom: sm6125-xiaomi-ginkgo: Correct reserved memory ranges To: David Heidelberg , =?UTF-8?B?QmFybmFiw6FzIEN6w6ltw6Fu?= , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Gabriel Gonzales , Kees Cook , Tony Luck , "Guilherme G. Piccoli" , Biswapriyo Nath Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org, phone-devel@vger.kernel.org, ~postmarketos/upstreaming@lists.sr.ht, linux@mainlining.org References: <20260112-xiaomi-willow-v1-0-8e4476897638@mainlining.org> <20260112-xiaomi-willow-v1-2-8e4476897638@mainlining.org> <723357fc-a785-45d6-8d49-4c00dd4f340c@ixit.cz> <0da3c96e-4f20-4bd0-836e-73d20581954f@ixit.cz> Content-Language: en-US From: Konrad Dybcio In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Proofpoint-ORIG-GUID: wA9bl5Ey5qIHCJZhgtjTjFXKin1Az2KX X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwMTE2MDA4MiBTYWx0ZWRfX8nuDLJ/NSjvu Od96K2Dz5qQU8/V8yQEnNcMpQvL5o6lMRXYu2m0bOeBZinP1oOanZua/9ZoBhb2XebQe8BSFBNG qV0WfDp5wIRgovuar+ZK386HqILhHpJeH6r6E6e3Wj4UK9PTHOdjnQYlg5XVZUjUQSQ8JNnnXDU +NWiVAM3wCUPLw4jqmALGB/bTvqZI5xl7zPZnI6rw9rBvxowBipQF9MBCTKg26Iau14+ei3wCGy a0VYxC2rgFYITq+Gz2mUe7kH9aqakHxEN26hjT9K5j/2CmvUKxIQlQaVvs6Xa02mf/L8etGk6F7 vttRzEEx3icY71YGPwpjQMioiBheH0Rf0aBq5rkhsYgh2qKKEDoeaZKAh8dm18c+T2yCJbCDJZZ O96aK1IngHl1Ty2aNNZY6Vwrz7myXIcHnayoJ+RJsu4DF6XGJRoHAxXPL55UD7fYzrK/5naLmt/ mqhcWoF8yT1v+1fy90Q== X-Proofpoint-GUID: wA9bl5Ey5qIHCJZhgtjTjFXKin1Az2KX X-Authority-Analysis: v=2.4 cv=M9tA6iws c=1 sm=1 tr=0 ts=696a214c cx=c_pps a=EVbN6Ke/fEF3bsl7X48z0g==:117 a=FpWmc02/iXfjRdCD7H54yg==:17 a=IkcTkHD0fZMA:10 a=vUbySO9Y5rIA:10 a=s4-Qcg_JpJYA:10 a=VkNPw1HP01LnGYTKEx00:22 a=OuZLqq7tAAAA:8 a=WKeohOAsuF05E7y8TmsA:9 a=3ZKOabzyN94A:10 a=QEXdDO2ut3YA:10 a=a_PwQJl-kcHnX1M80qC6:22 a=AKGiAy9iJ-JzxKVHQNES:22 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.9,FMLib:17.12.100.49 definitions=2026-01-16_03,2026-01-15_02,2025-10-01_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 clxscore=1015 malwarescore=0 bulkscore=0 impostorscore=0 lowpriorityscore=0 adultscore=0 spamscore=0 phishscore=0 suspectscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2512120000 definitions=main-2601160082 On 1/16/26 12:21 PM, David Heidelberg wrote: > On 16/01/2026 10:52, Konrad Dybcio wrote: >> On 1/14/26 10:55 PM, David Heidelberg wrote: >>> On 14/01/2026 11:28, Konrad Dybcio wrote: >>>> On 1/14/26 11:15 AM, David Heidelberg wrote: >>>>> On 12/01/2026 21:13, Barnabás Czémán wrote: >>>>>> The device was crashing on high memory load because the reserved memory >>>>>> ranges was wrongly defined. Correct the ranges for avoid the crashes. >>>>>> Change the ramoops memory range to match with the values from the recovery >>>>>> to be able to get the results from the device. >>>>>> >>>>>> Fixes: 9b1a6c925c88 ("arm64: dts: qcom: sm6125: Initial support for xiaomi-ginkgo") >>>>>> Signed-off-by: Barnabás Czémán >>>>>> --- >>>> >>>> [...] >>>> >>>>> Hello! >>>>> >>>>> I suggest one more nice to have improvement: >>>>> >>>>> you could label framebuffer cont_splash_mem since you already touching the node and testing the series. >>>>> >>>>> Then in additional commit, you can replace manually defined `reg` in chosen > framebuffer node with >>>>> >>>>> memory-region = <&cont_splash_mem>; >>>>> >>>>> For example you can look at sdm845-oneplus-common.dtsi >>>>> >>>>> Tell me what u think >>>> >>>> If you wanna do that, please call it framebuffer_mem, "cont_splash" is a >>>> Qualcomm-specific name for (roughly) flicker-free bootup >>> >>> I have feeling someone recommended me to stick with cont_splash_mem. >>> >>> I think, since we'll be doing the mdss reset anyway in sdm845 (which I used as an example), I can do the rename in our sdm845 too then without any harm? (no it's not flicker-free takeover :D ) >> >> It's not flicker-free because the OS must cooperate in that process, >> whereas we currently reset and re-initialize the entire display subsystem > > Sure. > > Previously I was thinking, that after doing proper panel driver with proper initialization sequences etc. etc., we could have device-tree property such as "linux,takeover-from-bootloader", where we could skip mdss reset, panel reset and just continue from the point what bootloader set (for devices where bootloader does the right job). I don't think there's a need for a separate property. Once MDSS is powered on, various registers could be read back and the state could be largely inferred from there. It just comes with an infinite amount of edge cases and it's not top priority for now, I don't think Konrad