Received-SPF: pass (google.com: domain of linux-kernel+bounces-66563-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Message-ID: <d3d7b101-eb19-4169-94ce-25e6f969f035@suse.com>
Date: Thu, 15 Feb 2024 10:37:16 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Bug reporting on Raydium touchscreen
To: Vanja Pogacic <vanja@pogacic.net>, linux-pci@vger.kernel.org,
 linux-kernel@vger.kernel.org
References: <20240215085953.Horde.oa0RoVvzrHmYsnVs_gHNkTT@cloud.pogacic.net>
Content-Language: en-US
From: Oliver Neukum <oneukum@suse.com>
In-Reply-To: <20240215085953.Horde.oa0RoVvzrHmYsnVs_gHNkTT@cloud.pogacic.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 15.02.24 09:59, Vanja Pogacic wrote:
> Hello,
> I am trying to find the best way to submit a kernel bug for a raydium touchscreen driver (raydium_i2c_ts) which stops working after waking up from sleep.
> The hardware in question is a converted Chromebook (Acer Spin 512) with coreboot uefi bios.
> 
> You can find more details and logs about the issue here:
> bbs.archlinux.org/viewtopic.php
> 
> Since I observed the same behavior under Fedora, Ubuntu and Arch, I concluded it would be best to contact the upstream people :)
> 
> Any guidance will be highly appreciated.

Hi,

in your specific case I would suggest making a bug report on bugzilla.kernel.org
to collect your logs in one place. Then based on your logs, decide whether your issue is rather
input or power management and make a bug report to the appropriate list.

	HTH
		Oliver