meta-ti.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: "Kumar, Udit" <u-kumar1@ti.com>
To: Ryan Eatmon <reatmon@ti.com>, <meta-ti@lists.yoctoproject.org>
Cc: <sbellary@baylibre.com>, <sinthu.raja@mistralsolutions.com>
Subject: Re: [meta-ti] [PATCH] export ov10635 camera device tree overlay
Date: Tue, 12 Mar 2024 11:49:19 +0530	[thread overview]
Message-ID: <b73b3443-7aa5-48d0-9ec9-20f63faf5de9@ti.com> (raw)
In-Reply-To: <17BBBE23B48A82C1.17779@lists.yoctoproject.org>

Hi Ryan

On 3/11/2024 8:35 PM, Udit Kumar via lists.yoctoproject.org wrote:
> Hi Ryan
>
> On 3/11/2024 6:05 PM, Ryan Eatmon wrote:
>>
>> We typically put the file grouping of the change in the commit 
>> message. For example:
>>
>> conf: machine: am57xx: export ov10635 camera device tree overlay
>>
>>
>> On 3/11/2024 6:14 AM, Udit Kumar via lists.yoctoproject.org wrote:
>>> Adding ov10635 camera overlay in default build
>>>
>>>
>>> Signed-off-by: Udit Kumar <u-kumar1@ti.com>
>>> ---
>>>   meta-ti-bsp/conf/machine/am57xx-evm.conf | 1 +
>>>   1 file changed, 1 insertion(+)
>>>
>>> diff --git a/meta-ti-bsp/conf/machine/am57xx-evm.conf 
>>> b/meta-ti-bsp/conf/machine/am57xx-evm.conf
>>> index 43a6a833..9a06e801 100644
>>> --- a/meta-ti-bsp/conf/machine/am57xx-evm.conf
>>> +++ b/meta-ti-bsp/conf/machine/am57xx-evm.conf
>>> @@ -29,6 +29,7 @@ KERNEL_DEVICETREE = " \
>>>       am57xx-beagle-x15-revc.dtb \
>>>       am5729-beagleboneai.dtb \
>>>       am571x-idk.dtb \
>>> +    ov10635.dtbo \
>>
>> This change is not needed to get this overlay into the TI kernels.  
>> This is already included in the KERNEL_DEVICETREE_PREFIX variable and 
>> is part of the builds. The KERNEL_DEVICETREE is used to reference 
>> files that are upstreamed, which is seems on quick glance, that this 
>> overlay is not upstreamed.
>>
> Yes, this overlay is not upstreamed and present in ti kernels


are you ok to accept ti specific files , if yes I will send v2.

Thanks

Udit

>
>
>> Were you seeing a problem that this patch is seeking to resolve?
>
>
> I am not able to get this overlay as part of yocto build. So I am 
> planning to export this dtbo into build
>
>
>>
>>
>>>       am572x-idk.dtb \
>>>       am574x-idk.dtb \
>>>   "
>>>
>>>
>>>
>>>
>>>
>>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#17508): https://lists.yoctoproject.org/g/meta-ti/message/17508
> Mute This Topic: https://lists.yoctoproject.org/mt/104860956/7571657
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [u-kumar1@ti.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


      parent reply	other threads:[~2024-03-12  6:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 11:13 [PATCH] export ov10635 camera device tree overlay Udit Kumar
2024-03-11 12:30 ` [EXTERNAL] [meta-ti] " Chirag Shilwant
2024-03-11 12:35 ` Ryan Eatmon
2024-03-11 15:05   ` Kumar, Udit
     [not found]   ` <17BBBE23B48A82C1.17779@lists.yoctoproject.org>
2024-03-12  6:19     ` Kumar, Udit [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b73b3443-7aa5-48d0-9ec9-20f63faf5de9@ti.com \
    --to=u-kumar1@ti.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=reatmon@ti.com \
    --cc=sbellary@baylibre.com \
    --cc=sinthu.raja@mistralsolutions.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).