On Mon, Apr 24, 2023 at 4:50 AM Adam Ford wrote:
>
> On Mon, Apr 24, 2023 at 4:47 AM Marek Szyprowski
> wrote:
> >
> > On 24.04.2023 11:44, Chen-Yu Tsai wrote:
> > > On Mon, Apr 24, 2023 at 5:31 PM Adam Ford wrote:
> > >> On Mon, Apr 24, 2023 at 1:12 AM Chen-Yu Tsai wrote:
> > >>> On Sun, Apr
On Mon, Apr 24, 2023 at 4:47 AM Marek Szyprowski
wrote:
>
> On 24.04.2023 11:44, Chen-Yu Tsai wrote:
> > On Mon, Apr 24, 2023 at 5:31 PM Adam Ford wrote:
> >> On Mon, Apr 24, 2023 at 1:12 AM Chen-Yu Tsai wrote:
> >>> On Sun, Apr 23, 2023 at 8:13 PM Adam Ford wrote:
> The DPHY timings are
On 24.04.2023 11:44, Chen-Yu Tsai wrote:
> On Mon, Apr 24, 2023 at 5:31 PM Adam Ford wrote:
>> On Mon, Apr 24, 2023 at 1:12 AM Chen-Yu Tsai wrote:
>>> On Sun, Apr 23, 2023 at 8:13 PM Adam Ford wrote:
The DPHY timings are currently hard coded. Since the input
clock can be variable, the
On Mon, Apr 24, 2023 at 5:31 PM Adam Ford wrote:
>
> On Mon, Apr 24, 2023 at 1:12 AM Chen-Yu Tsai wrote:
> >
> > On Sun, Apr 23, 2023 at 8:13 PM Adam Ford wrote:
> > >
> > > The DPHY timings are currently hard coded. Since the input
> > > clock can be variable, the phy timings need to be
On Mon, Apr 24, 2023 at 1:12 AM Chen-Yu Tsai wrote:
>
> On Sun, Apr 23, 2023 at 8:13 PM Adam Ford wrote:
> >
> > The DPHY timings are currently hard coded. Since the input
> > clock can be variable, the phy timings need to be variable
> > too. Add an additional variable to the driver data to
On Sun, Apr 23, 2023 at 8:13 PM Adam Ford wrote:
>
> The DPHY timings are currently hard coded. Since the input
> clock can be variable, the phy timings need to be variable
> too. Add an additional variable to the driver data to enable
> this feature to prevent breaking boards that don't support
The DPHY timings are currently hard coded. Since the input
clock can be variable, the phy timings need to be variable
too. Add an additional variable to the driver data to enable
this feature to prevent breaking boards that don't support it.
The phy_mipi_dphy_get_default_config function
