Re: [PATCH] tpm: atmel: Drop PPC64 specific MMIO setup

2024-11-06 Thread Jarkko Sakkinen
On Wed Nov 6, 2024 at 8:32 PM EET, Rob Herring wrote: > On Wed, Nov 6, 2024 at 12:19 PM Jarkko Sakkinen wrote: > > > > On Wed Nov 6, 2024 at 8:17 PM EET, Jarkko Sakkinen wrote: > > > > Whatever happened to this? Can you please apply my patch if you don't > > > > have the time for further rework. >

Re: [PATCH] tpm: atmel: Drop PPC64 specific MMIO setup

2024-11-06 Thread Rob Herring
On Wed, Nov 6, 2024 at 12:19 PM Jarkko Sakkinen wrote: > > On Wed Nov 6, 2024 at 8:17 PM EET, Jarkko Sakkinen wrote: > > > Whatever happened to this? Can you please apply my patch if you don't > > > have the time for further rework. > > > > Sorry unintentional. > > > > I applied with > > > > -stat

Re: [PATCH] tpm: atmel: Drop PPC64 specific MMIO setup

2024-11-06 Thread Jarkko Sakkinen
On Wed Nov 6, 2024 at 8:17 PM EET, Jarkko Sakkinen wrote: > > Whatever happened to this? Can you please apply my patch if you don't > > have the time for further rework. > > Sorry unintentional. > > I applied with > > -static void __iomem * atmel_get_base_addr(unsigned long *base, int > *region_si

Re: [PATCH] tpm: atmel: Drop PPC64 specific MMIO setup

2024-11-06 Thread Jarkko Sakkinen
On Wed Nov 6, 2024 at 4:50 PM EET, Rob Herring wrote: > On Thu, Jul 18, 2024 at 11:01 AM Jarkko Sakkinen > wrote: > > > > On Thu Jul 18, 2024 at 5:57 PM EEST, Rob Herring wrote: > > > On Wed, Jul 17, 2024 at 6:14 AM Jarkko Sakkinen > > > wrote: > > > > > > > > On Wed Jul 17, 2024 at 3:08 PM EES

Re: [PATCH] tpm: atmel: Drop PPC64 specific MMIO setup

2024-11-06 Thread Rob Herring
On Thu, Jul 18, 2024 at 11:01 AM Jarkko Sakkinen wrote: > > On Thu Jul 18, 2024 at 5:57 PM EEST, Rob Herring wrote: > > On Wed, Jul 17, 2024 at 6:14 AM Jarkko Sakkinen > > wrote: > > > > > > On Wed Jul 17, 2024 at 3:08 PM EEST, Jarkko Sakkinen wrote: > > > > On Tue Jul 2, 2024 at 7:10 PM EEST, R

Re: [PATCH] tpm: atmel: Drop PPC64 specific MMIO setup

2024-07-18 Thread Jarkko Sakkinen
On Thu Jul 18, 2024 at 5:57 PM EEST, Rob Herring wrote: > On Wed, Jul 17, 2024 at 6:14 AM Jarkko Sakkinen > wrote: > > > > On Wed Jul 17, 2024 at 3:08 PM EEST, Jarkko Sakkinen wrote: > > > On Tue Jul 2, 2024 at 7:10 PM EEST, Rob Herring (Arm) wrote: > > > > The PPC64 specific MMIO setup open code

Re: [PATCH] tpm: atmel: Drop PPC64 specific MMIO setup

2024-07-18 Thread Rob Herring
On Wed, Jul 17, 2024 at 6:14 AM Jarkko Sakkinen wrote: > > On Wed Jul 17, 2024 at 3:08 PM EEST, Jarkko Sakkinen wrote: > > On Tue Jul 2, 2024 at 7:10 PM EEST, Rob Herring (Arm) wrote: > > > The PPC64 specific MMIO setup open codes DT address functions rather > > > than using standard address parsi

Re: [PATCH] tpm: atmel: Drop PPC64 specific MMIO setup

2024-07-17 Thread Jarkko Sakkinen
On Wed Jul 17, 2024 at 3:08 PM EEST, Jarkko Sakkinen wrote: > On Tue Jul 2, 2024 at 7:10 PM EEST, Rob Herring (Arm) wrote: > > The PPC64 specific MMIO setup open codes DT address functions rather > > than using standard address parsing functions. The open-coded version > > fails to handle any addre

Re: [PATCH] tpm: atmel: Drop PPC64 specific MMIO setup

2024-07-17 Thread Jarkko Sakkinen
On Tue Jul 2, 2024 at 7:10 PM EEST, Rob Herring (Arm) wrote: > The PPC64 specific MMIO setup open codes DT address functions rather > than using standard address parsing functions. The open-coded version > fails to handle any address translation and is not endian safe. > > I haven't found any evide

Re: [PATCH] tpm: atmel: Drop PPC64 specific MMIO setup

2024-07-03 Thread Michael Ellerman
"Rob Herring (Arm)" writes: > The PPC64 specific MMIO setup open codes DT address functions rather > than using standard address parsing functions. The open-coded version > fails to handle any address translation and is not endian safe. > > I haven't found any evidence of what platform used this.

Re: [PATCH] tpm: atmel: Drop PPC64 specific MMIO setup

2024-07-02 Thread Jarkko Sakkinen
On Tue, 2024-07-02 at 10:10 -0600, Rob Herring (Arm) wrote: > The PPC64 specific MMIO setup open codes DT address functions rather > than using standard address parsing functions. The open-coded version > fails to handle any address translation and is not endian safe. > > I haven't found any evide