lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250222075347.GC1158377@rocinante>
Date: Sat, 22 Feb 2025 16:53:47 +0900
From: Krzysztof WilczyƄski <kw@...ux.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Mrinmay Sarkar <quic_msarkar@...cinc.com>,
	manivannan.sadhasivam@...aro.org, quic_shazhuss@...cinc.com,
	quic_ramkri@...cinc.com, quic_nayiluri@...cinc.com,
	quic_krichai@...cinc.com, quic_vbadigan@...cinc.com,
	quic_nitegupt@...cinc.com,
	Kishon Vijay Abraham I <kishon@...nel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Slark Xiao <slark_xiao@....com>, Qiang Yu <quic_qianyu@...cinc.com>,
	Mank Wang <mank.wang@...prisma.us>,
	Johan Hovold <johan+linaro@...nel.org>,
	Jeff Johnson <quic_jjohnson@...cinc.com>,
	Fabio Porcedda <fabio.porcedda@...il.com>, mhi@...ts.linux.dev,
	linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org
Subject: Re: [PATCH v1 0/2] pci_generic: Add supoprt for SA8775P target

Hello,

> > > This patch series add separate MHI host configuration to enable
> > > only IP_SW channel for SA8775P target.
> > > 
> > > And also update the proper device id for SA8775P endpoint.
> > 
> > Applied to epf-mhi, thank you!
> 
> I see "[2/2] PCI: epf-mhi: Update device id for SA8775P" on
> pci/epf-mhi, but I don't see patch [1/2].  Where did that go?
> They seem related, so I would think we'd want to merge them together.

I asked Mani whether he would prefer for me to take the entire series via
the PCI tree, but he said that the first patch should go via the MHI tree.

So, I assume Mani will take it, then.  Mani, thoughts?

> Also, in [2/2], I guess the .deviceid change is known not to break
> anything that's already in the field?

Mrinmay, are you expecting any issues with this change?

Per the c670e29f5bfe ("PCI: epf-mhi: Add support for SA8775P SoC"):

  Add support for Qualcomm Snapdragon SA8775P SoC to the EPF driver.
  SA8775P is currently reusing the PID 0x0306 (the default one hardcoded
  in the config space header) as the unique PID is not yet allocated.

I think, we should be fine.  But would be best to confirm that.

	Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ